Migrate environments between control planes

SnapLogic offers the following control planes:

Currently, you can migrate from the US control plane to EMEA. Organizations choose to migrate between control planes for several reasons, including:

  • Better performance: Lower latency because of proximity.
  • Data residency requirements: Data remains in a specific geographic region.

Migration of environments (Orgs) between control planes requires careful planning and execution. If your organization would like to migrate, contact your Customer Success Manager (CSM) to discuss feasibility and a timeline. This page answers basic questions about the migration process.

Who performs the migration?

From SnapLogic:

  • A Customer Success Manager (CSM)
  • An engineer from Professional Services (PS)
  • A Project Manager (PM)

From your organization:

  • An Environment admin
  • An Integration developer
  • A QA resource

The SnapLogic team members use a migration tool and get the target environment set up. Your Environment admin is responsible for configuring the target environment to match the source environment. The Integration developer and QA resource are responsible for testing at prescribed stages and for final acceptance. For production systems, your organization is responsible for changing the URLs for systems and applications that call public APIs and tasks (unless you have your own custom URLs).

When the CSM and PS complete the migration, they provide a report that shows what was migrated and lists the remaining steps.

How much downtime does migration require?

We aim for zero downtime with a parallel approach:

  • Start with a development environment, if applicable.
  • Validate functionality in the development environment before migrating a production environment.
  • Validate functionality in the production environment before cut-over.

SnapLogic retains the source environment for 45 to 60 days for reference and fallback when necessary.

How long does migration take?

We estimate up to three person days per environment for the SnapLogic migration team members to run the migration tool, depending on complexity. This doesn't account for the time required for planning, coordination, and validation. The time required from your organization also depends on the following factors:
  • The number of environments your organization uses for development and in production.
  • The number of operational assets, such as user accounts, Snap accounts, pipelines, and tasks.
  • The type of tasks, scheduled tasks are the easiest to migrate.
  • Use of Secrets Management and the Git Integration.
Important: We don't currently support migrating environments that are actively using APIM or Enhanced Encryption. Environments that have these entitlements but aren't yet using them can still be migrated.

Where can I find more details?