Only show these results:

Migration Guide for Data Centers

This guide details the process of changing your region for data residency purposes. Each data center region is isolated and separate from others. When you’ve configured Nylas to store data in one region, your application uses that region’s Nylas URLs for API requests. Data isn't shared between regions. To migrate your organization’s data region, follow the steps below.

For setting up a new organization and configuring your region for the first time, see the Data Residency guide to get started.

Migrating an Existing Organization

If your organization has set up your data residency for one of our existing regions, follow the steps below to migrate to another region.

Step 1: Create a New Nylas Organization

To migrate your current organization to a new region, create a new application for the new region. Use the links below for your specific region’s Nylas Dashboard.

Location Dashboard URL API URL
United States (Oregon) https://dashboard.nylas.com https://api.nylas.com
Canada (Central) https://canada-dashboard.nylas.com https://canada.api.nylas.com
Europe (Republic of Ireland) https://ireland-dashboard.nylas.com https://ireland.api.nylas.com

Step 2: Set Up Authentication and Begin Migration

Set up your new application's Client ID and Client Secret authentication information. Check your new application’s configuration, then begin migrating the new application into your organization.

Step 3: Transfer Billing Information

Contact your Nylas Customer Success Manager with your application’s information. We'll connect the new application’s billing profile to your current account. The billing department also manages the added data residency region of your new application. Using additional data centers has no additional platform fee.

Step 4: Re-authenticate Users and Accounts

Users and accounts in your new application’s data residency require re-authentication. These need new <ACCESS_TOKEN> values for your new application.

Step 5: Delete Duplicate Accounts

Revoke credentials for user account information from the former application as you migrate the accounts to the new application. Also, update the billing state for these accounts in the former application to cancelled. See the Managing Transitioning Accounts section for more.

Managing Transitioning Accounts

Unique identification values are different between applications in different data regions. Any ACCOUNT_ID or object ID values in the former region aren’t the same as those in the new region’s application.

Delete Accounts

With two applications connected to your accounts, deactivate access to the former region’s application and stop billing.

Use the Revoke Access Tokens endpoint to deactivate access tokens for accounts. To stop billing, contact Nylas with your applications’ ID numbers.

Account Migration Approach

The two methods below are effective for your data center migration.

Same-Month or Immediate

When completed with setting up a new application, migrate all user accounts. Finish the migration within the month and contact Nylas Billing for charge adjustments.

New Accounts First

After setting up a new application, you can choose to start only new users in the new region. For existing users, migrate accounts and credentials in a targeted approach. Move information from the former to the new application at your discretion.

This strategy helps you avoid additional work for setting up new users. However, accounts connected in both applications count toward your active connection total.

Billing

Your organization uses more than one application when migrating data regions. Account data remains in isolated regions, so you must contact the Nylas team to ensure your existing billing profile is linked to your new application. Contact Nylas Billing for solutions when transitioning data residency.

ID Values

Migrated users are new connections in Nylas. In this situation, all data requires resyncing and creates new ID values for every object. Merge existing data through unique IDs for calendar and email objects between regions. Duplicate data may involve alternative solution methods.

For emails, use the RFC-based messageid in the header of the email. For calendars using Nylas API v2.1 or higher, use the ical_uid field in an event object.

Webhooks

Update your webhook configuration for the new data residency options.

What's Next