Migration Scenarios and Use Cases

Migrate during Scheduled Downtime

If your application does not require constant uptime, such as in the case of an internal application, you can have the migration occur during scheduled downtime. Migrating during downtime is the easiest way to configure and complete the migration process.

When you start the migration process, Relational Migrator takes a snapshot of the data on the legacy application and migrates the data from that point in time. During the migration process, your legacy application can remain online to support incoming reads, but cannot support incoming writes. The length of the migration process depends on several factors, such as the amount of data being migrated and your connection speed.

After the migration completes, take your legacy application offline and launch your new application.

Migrate without Downtime

If your application must remain online to support reads and writes during the migration process, you can use Change Data Capture (CDC) to migrate data without downtime. This process is called a continuous sync migration.

When you start a continuous sync migration, Relational Migrator takes a snapshot of the data on the legacy application and tracks database updates in near real time. During the migration process, your source and destination databases remain in sync.

After the continuous sync migration completes, you can transfer users to the new application and shut down the legacy application.

To learn more about migration jobs, see Migration Jobs.

Unsupported Migration Scenarios

Relational Migrator currently does not support migrating an operational data store. Depending on your workload, migrating a data store could cause CDC to run indefinitely without completing, which is not recommended with Relational Migrator.

Relational Migrator will support more migration scenarios and use cases in future releases.