Migrate projects to another org

If you have access to more than one environment (Org) in SnapLogic, you can migrate projects from one to another. Migration effectively creates a copy, the original project remains unchanged. In the dialog to select assets:
  • If the target project doesn't exist, all Asset types that exist in the source project are selected by default. Migration creates a project with the same name as the source.
  • The first time that you migrate assets from a project, all asset types are selected by default. In subsequent migrations, the target tasks, accounts, and files are customized to the target Org, and therefore you must select the target Asset types.
  • If the target project exists, the task and account Asset types are not selected by default; rather, the assumption is that the tasks, accounts, and files are already customized for the target Org). If you select task or account, a warning dialog appears describing the risk associated with migrating these types of assets.
    Note:

    If the source project references files in a /shared directory, copies of those files are also migrated if they do not already exist in the relative /shared folder in the Org to which you are migrating Assets.

  1. In SnapLogic Manager, click the dropdown next to the source project.
  2. Click Migrate to open the Migrate project dialog.

    Migrate project context menu

  3. Select the target Org and target project space from the selectors:
    Migrate Project dialog
  4. Click Choose asset types to migrate.
    The dialog opens:

  5. Select the assets to migrate and click Migrate. A notification indicates that the migration has started. When migration completes, Manager displays a second notification.