Articles in this section

Move accounts between regional domains

Celigo operates independent data center domains in the United States, Canada, Europe, and Australia. When you sign up, your account is provisioned in the domain you select, and all of your account data stays in that region. Moving an account to a different domain means creating a new account and rebuilding your integrations there — Celigo cannot transfer them for you. This article explains when a move is justified and how to complete one.

Read this if you signed up in the wrong domain, or if a data residency requirement means your account needs to be in a different region than the one it is in today.

Prerequisites

Account owner or admin access to the account.

Region Sign-in URL
United States integrator.io
Europe eu.integrator.io

When to move an account

Move an account when both of the following are true:

  • You signed up in the wrong domain, or a data residency requirement applies to your organization.
  • Your organization, your users, and the applications you connect to are located in the region you want to move to.

Moving your Celigo account changes where Celigo processes and stores your integration data. It does not change where the applications you connect to store their data. If your applications process data in a different region, cross-border data transfers still occur after the move. Confirm the data location of every application you connect to before you decide.

Tip

Instead of moving, you can keep a licensed account in more than one domain. This may increase your license fees.

For the compliance considerations that most often drive these requests, see Data residency and cross-border transfers.

What transfers and what does not

You are responsible for rebuilding your account in the new domain. Only integrations exported in an integration ZIP file move across domains, and connection credentials are not included in that file.

The following do not transfer and must be recreated in the new account:

  • Connections and their credentials
  • Users and pending invitations
  • Single sign-on (SSO) and multi-factor authentication (MFA) configuration
  • API tokens and iClients
  • On-premise agents
  • Celigo Storage files
  • Data retention policy settings and environments
  • Audit logs, error records, and flow execution history

Move your account to another domain

  1. Tell your CSM which domain you want to move to. They confirm licensing and timing for the move.
  2. Sign up for a new account at the destination domain URL. You become a free trial user for 30 days, with access to all Celigo platform features and unlimited flows and endpoints. Throughout this article, your existing account is the current account and the account you create is the new account.
  3. Plan how you will transfer, test, and validate every integration in the new account within the 30-day trial period. This window is the binding constraint on the whole move.
  4. Transfer your integrations. Use the section that matches your current account.
  5. Turn off flows in the current account before you turn them on in the new account. If both accounts run flows against the same applications at the same time, you will process the same records twice.
  6. Tell your CSM when your integrations are tested and ready. Celigo provisions licensing for the new account, and de-provisions licensing for the current account after a transition period. The new account becomes your paid account, and the current account becomes a free account.

Note

Integration apps are not included in the free trial plan. If you have managed flows that use integration apps, follow the integration app steps in the following section.

Transfer custom flows

Follow these steps if your current account contains only custom flows that you built yourself.

  1. In the current account, create a snapshot of each integration as a backup.
  2. Download a ZIP file of your integrations. See Download an integration and install it in your account.
  3. Upload and install the ZIP file in the new account.
  4. Reauthorize every connection in the new account. Connection settings are not stored in the integration ZIP file, so you must configure connections for each application connector again.
  5. Test each flow in the new account before you turn off the corresponding flow in the current account.

Transfer managed flows that use integration apps

Follow these steps if your current account includes managed flows that use integration apps.

  1. Record all of your integration apps' settings, using screenshots or written notes.
  2. Ask Celigo to provision new integration app licenses in the new account.
  3. Recreate each setting in the newly installed integration apps.
  4. Run and test each new flow.

Contact your CSM or Celigo Support if you need help.

If your current account has no integrations or flows, no transfer is required — sign up in the new domain and build there.

Data residency and cross-border transfers

Your Celigo account data is created and stored only in the region of the domain you signed up in. Where the applications you connect to store their data is outside Celigo's control, so a Celigo account in a given region does not by itself eliminate cross-border data transfers.

Celigo will provide a Data Processing Addendum (DPA) on request at compliance@celigo.com.

GDPR

Celigo is a United States-based company, so processing data in the Europe (Germany) data center may still require your organization to complete a transparency report and meet other cross-border data transfer obligations. As the GDPR data controller, your organization is responsible for these requirements. Celigo is not legally required to provide transparency reports for individual customers and does not typically do so. Celigo complies with its own GDPR obligations and provides an EU, UK, or Swiss GDPR DPA on request at compliance@celigo.com.