Versions Compared

Old Version 9

changes.mady.by.user Ruth Stento

Saved on

compared with

New Version 10

changes.mady.by.user Ruth Stento

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

SnapLogic currently offers two control planes:

Organizations outside of the US might want to migrate from the Global to the EMEA control plane for any of the following reasons:

  • Better performance: Lower latency because of proximity.

  • Data sovereignty: Data stays in the region where it was created and is not subject to foreign laws.

Migration of environments from the Global control plane to the EMEA control plane requires careful planning and execution. If your organization would like to migrate, contact your Customer Success Manager (CSM) to discuss feasibility and your timeline.

Child pages (Children Display)
allChildrentrue

Before you begin

  • Make sure that your CSM is aware of the project.

  • Engage all of your internal stakeholders to understand how downstream processes and applications use data processed by the SnapLogic Platform. All systems that call public APIs and tasks will need to change the URI from the US to the EMEA Control plane.

  • Most environments (Orgs) contain assets that were used only for development or are no longer operational. If you can identify these before or during your inventory and clean them up, it greatly simplifies the migration process.

Migration Process

The following table describes the main steps required to migrate an environment from the US Control plane to the EMEA Control plane. The description column includes links to resources and more information.

Step

Responsible Party

Description

  1. Identify the requirements for new environments and a timeline.

Customer

Inventory environments (Orgs), user accounts, projects, and assets. Decide who will perform each migration task and how, and create a timeline. Refer to Preliminary Inventory for checklists.

  1. Create the new environments on the EMEA Control plane.

SnapLogic

Create the environment and enable feature entitlements.

  1. Migrate the foundational assets: user accounts, groups, and projects.

Customer, optionally contact SnapLogic Professional Services for help.

Refer to Migrate User Accounts and Groups and Migrate Project Spaces and Projects.

  1. Configure the new environmentenvironments.

Customer

Refer to Configure the New Environment.

  1. Migrate integration assets: endpoint accounts, pipelines, files, tasks, APIs from APIM, AutoSync data pipelines.

Customer, optionally contact SnapLogic Professional Services for help.

Unless an environment uses Enhanced Account Encryption and Groundplexes, you must migrate your own endpoint accounts. Similarly there is no automated way to migrate Ultra tasks or APIM APIs. Refer to Migrate Integration Assets.

  1. Configure the data plane.

Customer: for Groundplexes

SnapLogic: for Cloudplexes and AutoSync Snaplexes

Refer to Configure the Data Plane.

  1. Acceptance testing.

Customer

Refer to Acceptance Testing.