---
schema_version: "1"
id: de7efe48ff91b4af069a8b6bdd770c2970bbf49760ed8833bbaa322ddb36c790
title: Lifecycle Center Migration Errors
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_troubleshoot_migration.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_troubleshoot_migration.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 680b13f0410ad91199fca65e67630352e6eef9afe36409b2241d1a9370638ce0
description: Here are some tips if you encounter issues while migrating from DevOps Center (Managed Package) to Lifecycle Center.
products:
  - Salesforce Platform
release: "264"
---
# Lifecycle Center Migration Errors

Here are some tips if you encounter issues while migrating from DevOps Center (Managed Package) to Lifecycle Center.

## 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**.