Migrate accounts
Organizations with multiple environments can migrate accounts from one environment to another:
- 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.
- 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 environments should both be configured as trusted environments.
Encryption for migrated accounts
Different environments owned by the same organization can use different account encryption. Because of security risks, SnapLogic doesn't support migrating accounts from environments with Enhanced Encryption to those using standard encryption. In these cases, you must manually re-create the accounts in the target environment.
When you migrate accounts from one environment to another, consider the following:
- Re-encryption of accounts
- Standard Encryption to Standard or Enhanced Encryption
- Accounts migrated from an environment with standard encryption to another (destination) are automatically re-encrypted with the destination environment's keys.
- The source environment must recognize the destination environment as a trusted entity. Environment admins can configure trust settings in Admin Manager.
- Enhanced Encryption to Enhanced Encryption
- When migrating accounts between environments with Enhanced Encryption, the source environment private keys must be added to the destination environment's JCC keystores.
- The source private keys should have a different alias name than the destination key alias. We recommend appending the environment name to the source key alias.
- Standard Encryption to Standard or Enhanced Encryption
- Handling sensitive fields
- If your environment 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 that the 'key' field in the sensitive property object is deleted to allow encryption.