Move the starting state. Then close the gap while production stays open.
Omni Loader pins the change position before the initial load, copies tables in parallel, and keeps committed changes in a durable stream until the target catches up.
Establish the CDC handoff before the first table slice moves.
Use bounded workers and range slicing to seed large targets.
Replay every concurrent change before moving the application.
One coordinated path
Initial load and CDC share the same migration boundary.
The pipeline records where continuous capture begins, copies the selected tables, and applies every committed change that arrived during the copy.
Cut over with evidence
Know the remaining lag before you move traffic.
Separate capture and apply lag make the cutover decision observable. Let the target reach the durable frontier, validate it, then switch the application against a checkpoint you can name.
Keep exploring
See the connected parts of the platform.
Turn cutover into a measured handoff.
Bring the source, target, table sizes, and outage budget. We will map the load, CDC handoff, validation, and cutover sequence.