Finalize a migration

For continuous migrations, you can initiate the cut-over process after it's time to move reads and writes to the destination.

Cut-over means that the destination cluster is disconnected from the source and is now being used as your application write instance.

Go to Migration jobs in the Google Cloud console.

Go to the Migration jobs
Click the migration job that represents the migration that you want to finalize. The Migration job details page appears.
Use the Data Validation Tool to track the replication delay by checking row counts.

Wait for the replication delay to trend down significantly, ideally on the order of minutes or seconds. The replication delay is available for review on the Migration jobs page.
After the replication delay is at a minimum, initiate the cut over. To avoid data loss, make sure to:
1. Stop all writes, running scripts, and client connections to the source database. The downtime period begins here.
2. Wait until the replication delay is at zero, which means that the migration job has processed all outstanding changes.
3. Stop the migration job.
You can finalize a migration even if the replication delay isn't at zero. This can reduce the database downtime, but may affect the accuracy of the data in the destination.
The migration job stops reading from the source.
The destination instance can now be used as your application write instance.
The application can now be connected to the destination AlloyDB for PostgreSQL instance and the migration job can be deleted safely.