Skip to main content

Data center migration

Zuora

Data center migration

  1. Last updated
  2. Save as PDF

Data center migration involves moving your data from one region to another to reduce latency and improve performance. To meet the growing need for hosting system data, you can transfer it to secure multi-tenancy and allocate resources.

Data center migration includes the following benefits:

  • Compliance with domestic regulations and guidelines
  • Time zone partitioned migration windows can facilitate maintenance convenience.
  • Cross-border data transfer for geographical proximity

Consult your internal legal policy before migrating data centers.

Data centers for migration

Zuora supports the following regions as data centers for migrating tenants:

  • North America to Europe
  • Europe to North America

Zuora executes migration in the following two phases,

  1. Migrates API sandbox tenants and their entities.
  2. Migrates production tenants. 

For pricing details, contact your Zuora account team.

Fill out-migration intake form

The tenant migration process involves a complete re-host of your tenants from one region to another. 

The migration intake form includes the following prerequisites for data transfer:

  • Intended region for migrating tenants
  • Tenant and entity IDs within the migration scope
  • Subscribed products or features
  • The preferred time frame for executing the migration

Migrate tenants

Complete the following steps to start tenant migration:

  1. Complete your Zuora product setup.
  2. Request a data center migration from your Zuora account team.
    Note: After your request is initiated, our migration team will contact you.
  3. Review the migration checklist.

System impacts on migration

This section lists system impacts for your consideration before and after the migration.

Prerequisites

  • Onboard all the new tenants to your Zuora site before the migration process. Adding new tenants on or after the migration window could lead to missing out on the initial data.
  • Connect with the data center migration team to decide the best window for migration. The system will experience a feature freeze and downtime of two minutes or less during migration. 

Considerations

  • Migration is a one-time process per subscription. If a customer subscribes to Billing and Revenue, the migration will be considered two separate migrations.
  • Zuora does not support split migrations. The product team will work with you to customize the migration timeline if there is a legal or specific business requirement.
  • The standard migration package involves one migration per order. To reverse the migration, contact Zuora Global Support.
  • Multi-entity tenants cannot distribute data residency across two regions.

Post-migration changes

After the migration, you will observe the following changes:

  • URL change
  • REST and UI endpoint change
  • New central sandbox tenant with a new ID
  • Disabled tenants in the former data center region 
  • Notifications auto-scheduled in UTC time zone (EU) or PT time zone (NA). For more information, see Standard Events.

Migration updates for EU production environment

The following section highlights the seamless transfer of features from sandbox to production in the EU region, focusing on improvements and limited disruption.

S.No

Description

Sandbox

Production

1

Access links for UI/backend

Sandbox endpoints to be updated:

Production endpoints to be updated:

2

Notifications /Callouts

Notifications are triggered based on UTC timezone (compared to PT in the US tenant)

In the US, tenant notifications follow the PT timezone, whereas UTC is the standard in general

3

Workflows

Data migration excludes workflow run and log data.

Data migration excludes workflow run and log data.

4

Tenants IDs

No impact

No impact

5

IP Settings

Use IP addresses from the EU sandbox

Use IP addresses from the EU production

6

Downtime

The downtime is under 3 minutes

The downtime is under 3 minutes

7

Feature Freeze window

Feature freeze is allowed for a 2-hour window

Feature freeze is allowed for a 2-hour window

8

History/ Audit Trail

The migration process won’t include telemetry and login history. (can be accessed from the audit trail via DQ.)

Audit Trail will undergo a full migration.

9

User Access

The process will continue as usual after migration, with the only difference being the location of the OAuth token in the EU instead of the US. The process will have no impact on the end user.

The user access process remains the same after migration, except that OAuth tokens are now generated in the EU. Tokens generated in the US region will become invalid, but end users won’t be affected.

10

Test User Account

Set up a pre-migration test user account to verify migrated data.

Set up a pre-migration test user account to verify migrated data.

Post-migration support

The migration team will perform service testing and validation once the migration is complete and tenants are operational in the new region.