On-Premises to MCE Migration Through Project Duplication

Project Duplication operates at the metadata level. It migrates project metadata and selected configuration objects according to the configured duplication settings. This supports consolidation scenarios in which one or more on-premises projects are migrated into a shared MCE environment while maintaining tenant isolation.

Note: The following workflow removes the need for source-side tenant preparation, SystemObjects.csv handling, tenant suffix processing, and manual SQL updates for tenant assignment.

1.Migration Process

1. Prepare the target MCE environment and enable Tenant Partitioning.
2. Create a new tenant as the target and record its tenant ID.
3. Configure Storage Service and verify access to the migration storage location.

2.Duplicate the Projects

For each source project:

Note: API-only workflow: Project duplication for this migration is available using the REST API.

For each source project, call POST /api/projectDuplications and configure the following optional fields in the request:

• isMergeMD: Triggers the metadata merge logic.
• dstTenantID: Specifies the target tenant ID and overrides the tenant information in the source metadata.
• globalObjectList: Identifies objects that must remain global and be assigned GUID_NULL.

1. Run the REST API request from the on-premises source environment to the MCE target.
2. Set isMergeMD to trigger the merge logic and set dstTenantID to the intended target tenant.
3. Configure globalObjectList for system and global configuration objects that must remain global.
4. Preserve the required project locales and migration settings.
5. Review and resolve dependency or conflict errors reported by the duplication operation.

Tenant and global-object behavior

• Project-owned objects are migrated to the specified dstTenantID.
• If an object with the same ID exists in the destination but belongs to a different tenant, the system generates a new ID and appends the tenant name as a suffix to resolve the conflict.
• Objects listed in globalObjectList, together with their dependencies, are identified as global and assigned GUID_NULL.
• Property sets, links and other system objects are migrated as global objects by default.

When consolidating multiple metadata repositories, repeat the process for each source project and assign each project to the appropriate target tenant.

3.Verify the Migration (Optional)

• Confirm that each project is created and accessible in MCE.
• Confirm that project-level objects are assigned to the correct tenant.
• Confirm that system and global objects remain global.
• Validate configuration dependencies and cross-tenant references.
• Review ACLs, users, user groups, subscriptions, and ownership assignments.
• Confirm that key administrator objects and runtime behavior remain valid.
• Rebuild the configuration search index if object visibility is stale.

Project Duplication Scope

Project Duplication migrates metadata and selected configuration objects. It does not copy filesystem or web-tier artifacts.