In this article
Overview
At the Project level, the export and migrate operations allow you to include Assets by type, but not to select individual Assets. Use the copy operation in Manager to migrate individually-selected Assets from one Org to another. Additional steps might be required when migrating:
Accounts, if the Orgs have different encryption levels. Learn more.
Pipelines that have child Pipelines or reference Accounts. Learn more.
Prerequisites
To use the copy operation to migrate individual Assets, you need the following permissions:
Read permission on the Project containing the Assets.
Write permission on the target Project.
Migrating Selected Assets
To migrate selected Assets in Manager:
From the left navigation tree, select the source Project or shared folder.
In the Assets table, select one or more Assets to migrate.
In the toolbar, click Copy ( ). The Copy Project dialog opens.
Select the target Org and target Project or folder:
Click Continue. The Select Assets dialog opens:
Expand the tree to select individual Assets:
Click Copy.
Best Practice on Asset Migration at the Org-level
When a task is migrated to another Org, the Snaplex references are set by the runtime_path_id
property and not by the Snaplex name. Accordingly, you should make sure that the values for the Location and Environment fields in the Snaplex dialogs match - not the Name field, as might be assumed.
Task Migration Example
Source Org in migration operation.
Org: dev
Task name: batch
Snaplex Information:
Name: dev1
Location: Cloud
Environment: west
When migrating the task batch from the dev to prod Orgs, a task from the dev Org with the runtime_path_id
of /dev/rt/cloud/west/batch
is replaced with the runtime_path_id
of /prod/rt/cloud/testtask
, even if the two Snaplexes have different name labels, such as devplex and prodplex.
However, the task with the associated Snaplexes that are both labeled mainplex in each Org, with runtime_path_ids
of /dev/rt/batch/testtask
and /prod/rt/otlp/testtask
does not work.