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:

...

1. From the left navigation tree, select the source Project or shared folder.

2. In the Assets table, select one or more Assets to migrate.

3. In the toolbar, click Copy ( ). The Copy Project dialog opens.

4. Select the target Org and target Project or folder:

   Image RemovedImage Added

5. Click Continue. The Select Assets dialog opens:

   Image RemovedImage Added

6. Expand the tree to select individual Assets:

   Image Removed

   Click CopyImage Added

7. Click Copy.

Best Practice on Asset Migration at the Org-level

When a task is migrated to another Org, the Snaplex references are fixed 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 labels, as one might assume.

For example:

When migrating the task testtask from the dev to prod Orgs, a task from the dev Org with the runtime_path_id of /dev/rt/cloud/testtask is replaced with the runtime_path_id of /prod/rt/cloud/testtask, even if the two Snaplexes have different 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/cloud/testtask and /prod/rt/cloud/testtask does not work.