--- schema_version: "1" id: 3633ff740e64cfd39274a98c87246bbb4972a1d46a83070e43162c28f879ef72 title: DevOps Center Managed Package Migration (Developer Preview) collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_managed_package_migration.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_managed_package_migration.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 1b3c0ff4fdd32bbc16de98b046e4b158dae65c07a6dc0b1284cf6246893aa514 description: Move your DevOps Center (Managed Package) projects into Lifecycle Center. Migration includes your projects, pipelines, environments, and eligible work items so your team can continue to release changes in the new experience. products: - Salesforce Platform release: "264" --- # DevOps Center Managed Package Migration (Developer Preview) Move your DevOps Center (Managed Package) projects into Lifecycle Center. Migration includes your projects, pipelines, environments, and eligible work items so your team can continue to release changes in the new experience. ### Required Editions
Available in: Lightning Experience in Professional (API access required), Enterprise, Performance, Unlimited, and Developer Editions
Not available in: Government Cloud Plus. Contact your Salesforce account executive for more details.
Not available in: EU Operating Zone. EU Operating zone is a special paid offering that provides an enhanced level of data residency commitment. Lifecycle Center is supported in orgs in the EU that aren't part of EU OZ, per standard product terms and conditions.
![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/images/icon_note.png) Note The feature is in developer preview and is subject to the Beta Services Terms at [Agreements - Salesforce.com](https://www.salesforce.com/company/legal/) or a written Unified Pilot Agreement, if executed by Customer. Its use is at the Customer's sole discretion. ## What Moves to Lifecycle Center Migration moves specific data from DevOps Center (Managed Package) to Lifecycle 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 Lifecycle 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. Lifecycle 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 Lifecycle 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 Lifecycle 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 Lifecycle 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 Lifecycle Center, and commit changes to them to continue their work. - Don't turn off Lifecycle Center while the migration is ongoing. - After you migrate a project, avoid working on the same project in both DevOps Center (Managed Package) and Lifecycle 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/images/icon_warning.png) 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 Lifecycle Center. - **[Migrate to Lifecycle Center (Developer Preview)](https://help.salesforce.com/s/articleView?id=platform.devops_center_migrate_managed_package.htm&release=264.0.0&type=5)** Move selected DevOps Center (Managed Package) projects to Lifecycle Center. #### See Also - [Lifecycle Center](https://help.salesforce.com/s/articleView?id=platform.next_generation_devops_center.htm&release=264.0.0&type=5 "Lifecycle Center (formerly next-generation DevOps Center) brings modern DevOps best practices to your team with an AI-powered, click-based user interface (UI). Built on the principles of DevOps Center (Managed Package), Lifecycle Center serves as a central development hub where your team can collaborate—with built-in governance that keeps coding agents and users safe and compliant.")