# Project (classic) recovery

#### GitHub **projects (classic)** are older project types that were used to create customized workflows (like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists) before projects v2 were introduced.

***

## General information

{% hint style="danger" %} <mark style="color:red;">**Support for backing up projects (classic) has been removed.**</mark> It is now available only for restoring previously backed-up **projects (classic)** — when restored, **projects (classic)** are automatically converted into **projects v2**.
{% endhint %}

According to the official **GitHub** page, **projects (classic)** are being **discontinued**.

You can only create a new **project (classic)** for an organization, repository, or user that already has at least one **project (classic)**. If you are unable to create a **project (classic)**, create a **project v2** instead.

When repositories containing **projects (classic)** are restored to an organization that does not support this feature, **direct restoration in the original format is not possible**. Instead, the system converts the restoration from **projects (classic)** to **projects v2**.

Key considerations include:

1. The conversion retains elements such as the project name, issue cards, and pull request cards.
2. Certain metadata, such as columns or notes, cannot be restored due to **GitHub** **API** limitations.
3. The system flags these conversions in the restoration summary for transparency.

<figure><img src="/files/tz8dUKoAKmzhSw6TBwS1" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Data that cannot be converted **remains in the backup copy**. Future updates to the **GitHub** **API** may enable improved restoration capabilities, allowing additional metadata to be recovered.
{% endhint %}

***

## Useful links and items

{% embed url="<https://docs.github.com/en/enterprise-server@3.15/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://helpcenter.xopero.com/xopero-one-en/backup-and-recovery/devops/github/recovery/project-classic-recovery.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.