DevOps Center Managed Package Migration (Developer Preview)

What Moves to Next-Generation DevOps Center

Migration moves specific data from DevOps Center (Managed Package) to the next-generation DevOps Center.

• Active projects selected for migration.
• Pipeline configurations, including stages and environments.
• Eligible work items, such as new and closed work items.
• Branches and configurations associated with migrated projects.

Migration copies data from DevOps Center (Managed Package) to the next-generation DevOps Center without affecting your original data. Run the migration multiple times to move new projects, work items, and pipelines. Migration adds new data but doesn't update previously migrated items, automatically skipping them to prevent duplicates.

Limitations

Certain DevOps Center (Managed Package) data doesn't migrate and requires manual updates post-migration.

• Open work items. Open work items refer to work items that are in In Progress, In Review, Ready to Promote, Approved, or Promoted status. The next-generation DevOps Center creates placeholders for open work items with the Migration Pending status. A placeholder contains the work item ID, title, and status. Complete the work in DevOps Center (Managed Package). To continue working on these work items in the next-generation DevOps Center, create corresponding work items there.
• Rerunning the migration doesn't update placeholders if the status of the managed package work item changes.
• Pipeline environment and source control credentials don't migrate and you must reauthorize them in the next-generation DevOps Center.

Considerations for Migration

• Migrate during a low-activity period to minimize disruption for your team.
• Promote, mark as Never, or close open work items in your pipeline.
• Use a new source control repository for the next-generation DevOps Center when possible. Reusing an existing repository with pre-existing branches can cause naming conflicts that prevent work items from moving to In Progress status.
• Inform your team that open work items appear as placeholders after migration.
• Tell your team members to create work items in the next-generation DevOps Center, and commit changes to them to continue their work.
• Don't turn off the next-generation DevOps Center while the migration is ongoing.
• After you migrate a project, avoid working on the same project in both DevOps Center (Managed Package) and the next-generation DevOps Center. Use the managed package only to finish open work items that existed before migration. Working in both places can create branch and data conflicts.
• Don't create work items in DevOps Center (Managed Package) after migration to avoid data inconsistencies.

Warning If you continue using DevOps Center (Managed Package) during a phased migration, plan how your team tracks new work. Run migration again to move new work items and related data into the next-generation DevOps Center.