Migration scope and limitations

The SnapLogic CSM and PS team members use a proprietary migration tool, which:

  • Produces an audit checklist of existing settings, and assets.
  • Checks the target environment against the source environment for discrepancies.
  • Migrates most assets automatically.

The migration tool can't migrate:

  • Some assets, such as APIM APIs, Proxies, or Services
  • Status, history, and logs
  • Configuration settings

The following sections provide more detail.

Assets migrated by the tool

Foundational assets

  • Users and Groups: Complete user list with permissions and group memberships
  • Snap Pack subscriptions: All subscribed Snap Packs and versions
  • Snaplexes: Cloudplexes (automatic), Groundplexes (configuration only)

Integration assets

  • Project Spaces and Projects: Complete folder structure with ACLs
  • Pipelines: All pipeline versions and configurations
  • Accounts: Credential configurations — those with standard encryption are re-encrypted automatically
  • Files: All file assets including schemas and documentation
  • Tasks: Scheduled, triggered, and ultra tasks (all disabled in the target environment)
Important: After the migration of user accounts and integration assets is complete, you must track any changes in the source environment. These must be synchronized with the target environment to prevent drift.

Not migrated

The migration tool can't migrate the following:

  • Pipeline execution history and metrics
  • Audit logs and compliance records
  • Runtime state and active executions
  • APIM APIs, Proxies, Services, Subscriptions, and Developer Portals

We recommend exporting execution history and logs up to the switchover date if you need to retain them.

Manual steps and configuration

The migration script generates a report listing all assets that the CSM will share with you. You should validate it and confirm the features and subscriptions from the source environment.

The migration tool doesn't migrate the following. Your team is responsible for reproducing these in the target environment:

  • SSO credentials and certificates (configuration is migrated, but credentials require manual setup)
  • CI/CD integration settings and tokens
  • Secrets manager configurations and customer secrets
  • Enhanced account encryption keys
  • SAML, IP whitelist, CORS, and session configurations
  • Pattern settings
  • Custom notification configurations