Migrate accounts

Organizations with multiple Orgs can migrate accounts from one Org to another. There are a few ways to migrate accounts:

From the Project Options menu:
  • Export and Import: Export the accounts to a ZIP file and import it into the target Org.
  • Direct Migration: Migrate accounts directly from one Org to another.
From the Assets Table:
  • Copy Accounts: Select the accounts to migrate and click the toolbar's Copy button.

Both Project options allow you to migrate all accounts. To migrate individual accounts, select them in the Assets table and copy them. Before migrating accounts, the Orgs should both be configured as trusted Orgs.

Encryption for migrated accounts

Different organizations (Orgs) owned by the same company may use various account types encryption. Because of security risks, SnapLogic does not support migrating accounts from Orgs with Enhanced Encryption to those using standard encryption. In these cases, you must manually re-create the accounts in the target Org.

Considerations when migrating accounts

When you migrate accounts from one Org to another, consider the following:

  • Re-encryption of accounts
    • Standard Encryption to Standard or Enhanced Encryption
      • Accounts migrated from an Org with standard encryption to another Org (destination) are automatically re-encrypted with the destination Org's keys.
      • The source Org must recognize the destination Org as a trusted entity. Org admins can configure trust settings in Organizational Settings.
    • Enhanced Encryption to Enhanced Encryption
      • When migrating accounts between Orgs with Enhanced Encryption, the source Org’s private keys must be added to the destination Org’s JCC keystores.
      • The source private keys should have a different alias name than the destination key alias. We recommend to append the Org name to the source key alias.
  • Handling sensitive fields
    • If your Org is configured for Enhanced Account Encryption, the SnapLogic Create Snap and Update Snap allow you to create/update accounts with sensitive fields provided in plain text. The Snaps will automatically encrypt accounts.
    • If a field is marked with a 'key' in the property, it indicates that the field is already encrypted. When providing plain text values, ensure the 'key' field in the sensitive property object is deleted to allow encryption.