|
| 1 | +--- |
| 2 | +title: Migrating your project to Projects (beta) |
| 3 | +intro: 'You can migrate your projects from the old projects experience to Projects (beta).' |
| 4 | +allowTitleToDifferFromFilename: true |
| 5 | +miniTocMaxHeadingLevel: 2 |
| 6 | +versions: |
| 7 | + fpt: '*' |
| 8 | + ghec: '*' |
| 9 | +topics: |
| 10 | + - Projects |
| 11 | + - Organizations |
| 12 | +--- |
| 13 | + |
| 14 | +{% note %} |
| 15 | + |
| 16 | +**Notes:** |
| 17 | + |
| 18 | +- Projects (beta) is currently in public beta and subject to change. |
| 19 | +- If the project you are migrating contains more than 1200 items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of 10,000 items is reached, additional items will not be migrated. |
| 20 | +- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#showing-and-hiding-fields)." |
| 21 | +- Automation will not be migrated. |
| 22 | +- Triage, archive, and activity will not be migrated. |
| 23 | +- After migration, the new migrated project and old project will not be kept in sync. |
| 24 | + |
| 25 | +{% endnote %} |
| 26 | + |
| 27 | +## About project migration |
| 28 | + |
| 29 | +You can migrate your project boards to the all new projects (beta) experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)." |
| 30 | + |
| 31 | +## Migrating an organization project board |
| 32 | + |
| 33 | +{% data reusables.projects.enable-migration %} |
| 34 | +{% data reusables.profile.access_org %} |
| 35 | +{% data reusables.user-settings.access_org %} |
| 36 | +{% data reusables.organizations.organization-wide-project %} |
| 37 | +1. On the left, click **Projects (classic)**. |
| 38 | +  |
| 39 | +{% data reusables.projects.migrate-project-steps %} |
| 40 | + |
| 41 | +## Migrating a user project board |
| 42 | + |
| 43 | +{% data reusables.projects.enable-migration %} |
| 44 | +{% data reusables.profile.access_profile %} |
| 45 | +1. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**. |
| 46 | + |
| 47 | +1. Above the list of projects, click **Projects (classic)**. |
| 48 | +  |
| 49 | +{% data reusables.projects.migrate-project-steps %} |
| 50 | + |
| 51 | +## Migrating a repository project board |
| 52 | + |
| 53 | +{% note %} |
| 54 | + |
| 55 | +**Note:** Projects (beta) does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository. |
| 56 | + |
| 57 | +{% endnote %} |
| 58 | + |
| 59 | +{% data reusables.projects.enable-migration %} |
| 60 | +{% data reusables.repositories.navigate-to-repo %} |
| 61 | +1. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**. |
| 62 | + |
| 63 | +1. Click **Projects (classic)**. |
| 64 | +  |
| 65 | +{% data reusables.projects.migrate-project-steps %} |
0 commit comments