Skip to content

Latest commit

 

History

History
53 lines (41 loc) · 3.6 KB

migrating-from-projects-classic.md

File metadata and controls

53 lines (41 loc) · 3.6 KB
title intro versions redirect_from type topics allowTitleToDifferFromFilename
Migrating from {% data variables.product.prodname_projects_v1 %}
You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.
feature
projects-v2-migration
/issues/trying-out-the-new-projects-experience/migrating-your-project
tutorial
Projects
true

Note

  • If the project you are migrating contains more than {% data variables.projects.item_limit %} 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 {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
  • 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 AUTOTITLE.
  • Automation will not be migrated.
  • Triage, archive, and activity will not be migrated.
  • After migration, the new migrated project and old project will not be kept in sync.
  • {% data reusables.projects.migration-permissions-warning %}

About project migration

You can migrate your {% data variables.projects.projects_v1_boards %} to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see AUTOTITLE.

Migrating an organization {% data variables.projects.projects_v1_board %}

{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}

  1. In the left sidebar, click Projects (classic). {% data reusables.projects.migrate-project-steps %}

Migrating a user {% data variables.projects.projects_v1_board %}

  1. In the upper-right corner of {% data variables.product.prodname_dotcom %}, select your profile photo, then click Your projects.

    Screenshot showing the profile photo menu. The "Your projects" link is highlighted with an orange outline.

  2. On the top of your profile page, in the main navigation, click {% octicon "table" aria-hidden="true" %} Projects. Screenshot showing the tabs on a user profile. The 'Projects' tab is highlighted with an orange outline.

  3. Above the list of projects, click Projects (classic). {% data reusables.projects.migrate-project-steps %}

Migrating a repository {% data variables.projects.projects_v1_board %}

Note

{% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository {% data variables.projects.projects_v1_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.

{% data reusables.repositories.navigate-to-repo %}

  1. Under your repository name, click {% octicon "table" aria-hidden="true" %} Projects.
  2. In the left sidebar, click Projects (classic). {% data reusables.projects.migrate-project-steps %}