Migrate Scheduler data from v2 to v3
🚀 Support for Scheduler migration is coming soon.
This page explains how Scheduler migration works and how to migrate your v2 Scheduler Pages to v3 Configurations.
How Scheduler migration works
Nylas Scheduler v3 introduces Configurations as replacements for v2 Pages. A Configuration is a collection of event settings and preferences which is stored in the Scheduler database and loaded as a Scheduling Page in the Scheduler UI. For a comparison between the schemas for Pages and Configurations, see the Scheduler v3 diff view.
Scheduler v3 includes an internal migration tool that automatically converts v2 Pages to Configurations. Nylas migrates each Page individually, based on the related application ID and the app-specific slug.
When a guest visits a Scheduling Page, Nylas checks to see if its slug exists for the app in v3. If the slug exists in v2, but not in v3, Nylas automatically starts migrating the Page. After Nylas completes the migration, Scheduler v3 creates a corresponding Configuration, and displays the Scheduling Page in the Scheduler Editor.
Migrating a Page can take several seconds. Guests might experience a delay in loading the Scheduling Page the first time they visit it.
Handling in-flight bookings
In-flight bookings are bookings that are currently in progress and can be rescheduled or canceled.
When you migrate your v2 connected accounts to v3 grants, Nylas gives a 30-day grace period before the migrated connected accounts expire. This allows v2 Pages to stay active, and organizers and guests can reschedule or cancel bookings during the grace period.
⚠️ After you migrate your connected accounts to grants, organizers no longer have access to the v2 Scheduler Editor. Be sure to plan accordingly.
The connected accounts automatically expire after the 30-day grace period, even if there are in-flight bookings beyond that 30-day period. The booked events remain active, but Nylas doesn't support rescheduling or cancelling them.