Lifecycle Center Migration Errors

Issue: Duplicate work item IDs after migration

Problem: A work item ID from the managed package already exists in the Lifecycle Center.

Resolution: The migration process automatically assigns the next available work item number to the migrated item. No action is required.

Issue: Branch naming conflicts

Problem: A branch naming conflict occurs when a branch already exists in the source control repository.

Resolution: If Lifecycle Center can't move a work item to In Progress due to this conflict, create a work item in Lifecycle Center.

Issue: DUPLICATE_VALUE error

Problem: The migration fails with a DUPLICATE_VALUE error, even though SOQL queries and the UI show zero records in SourceCodeRepositoryBranch.

Cause: The migration inserts records from sf_devops__Branch__c into SourceCodeRepositoryBranch, where the Name field must be unique. If two sf_devops__Branch__c records share the same sf_devops__Name__c value, the second insert fails and the migration stops.

Resolution:

• Query sf_devops__Branch__c to find records that share a sf_devops__Name__c value.
• Rename the obsolete branch record, which has no associated work items or commits.
• Clear all previously migrated SourceCodeRepositoryBranch records from the Lifecycle Center.
• Rerun the migration.

Issue: The Activate Pipeline button is disabled after migration

Problem: After you migrate a pipeline from DevOps Center (Managed Package), Activate Pipeline is disabled. If you try to activate the pipeline from a list view, you see the error Cannot activate pipeline: Pipeline stages must be bundled for stage: stage name.

Cause: The migration copies pipeline stage settings as they are in the managed package. Lifecycle Center requires every pipeline stage to be bundled before you can activate a pipeline, but a migrated stage can arrive with IsBundled set to false.

Resolution:

• Query the DevopsPipelineStage records for the migrated pipeline and check the IsBundled value for each stage.
• Set IsBundled to true on every stage where it's false.
• Return to the pipeline and click Activate Pipeline.