Migration behavior
Last updated: 11/3/2026The migration status of each asset is indicated by the following icons:
- Green checked checkbox: Migrated successfully.
- Blue information box: Migrated successfully with additional information. Hover over the icon to display the details.
- Amber exclamation triangle: Migrated successfully, but part of the asset failed to migrate, such as a trigger or a space description. Hover over the icon to display the message.
- Red exclamation circle: Migration failed. Hover over the icon to display the error message.
The following behavior applies to the migrated assets:
- Migration order: Environments are migrated first, followed by spaces and then engines. In an automatic migration, tasks and then plans are migrated last. A space or engine fails to migrate if the parent environment or space does not exist in the target tenant.
- Default environment: The default environment of the source tenant is not migrated.
- Space owner: The space owner is not migrated. The owner of the personal access token registered for the target tenant becomes the owner of the migrated space.
- Remote engines: Remote engines are migrated unpaired, with a new pre-authorized key. After the migration, pair each remote engine manually using the new key. Run profile types and the ESB compatibility version are migrated. Custom run profiles are not migrated.
- Remote engine clusters: The cluster and the remote engines inside the cluster are migrated. The remote engines are migrated unpaired and must be paired manually after the migration.
- Dynamic engines: Dynamic engines are created in the target tenant but are not assigned to the environment. After the migration, deploy each dynamic engine, then assign the dynamic engine to the environment.
- Existing environments, spaces, and engines: If an environment, space, or engine with the same name already exists in the target tenant, the existing asset is not modified. The migration status displays the information icon.
- Existing tasks and plans: If a task or plan with the same name already exists in the target space, the existing asset is overwritten with the source values. An existing artifact with the same version is reused and is not overwritten.