Nylas App migration API
Before you begin, you should already have: - Linked your v2 and v3 Nylas organizations. If you're not sure if your organizations are linked and you have a contract with us, [contact Nylas Support](/docs/support/#contact-nylas-support). - Created v3 applications to serve as the destinations for your v2 settings and connected account information. - [Set up equivalent provider auth apps as needed](/docs/v2/upgrade-to-v3/upgrade/auth/), especially if your users are authenticating with Microsoft. - [Set up v3 notification infrastructure](/docs/v2/upgrade-to-v3/upgrade/webhooks/). You'll use this to keep track of object that update while you're migrating your applications. You make Migration API requests using the v3 API route, using an API key from the destination v3 application. For each application to be migrated: 1. [Link apps](#post-/v3/migration-tools/link-v2v3-apps) 2. [Import app settings](#post-/v3/migration-tools/import-v2-app) 3. [Migrate a test user](#post-/v3/migration-tools/grants/-account_id-/clone) and/or [Start a batch migration](#post-/v3/migration-tools/snapshot-batch-clone) Make sure you use the correct region! In Nylas v3, you mange applications for both the U.S. and E.U. regions using the same Dashboard. If you're migrating a v2 application to a v3 one, make sure you create the v3 application in the correct region.