Migration and cutover

After mapping sign-off, the migration is a controlled load. The agent shows you the target and a transformed sample, waits for your approval, loads in batches with checkpoints, and reconciles source and target. The same saved tools run the sandbox load, the production load and the delta load at cutover, so every load applies exactly the agreed mapping.

1. Approve the load

Ask the agent to load the target. It shows the target system, the credential it will use and a transformed sample, then pauses for your approval before any write.

!

Every write to a client system pauses for your approval. Load a sandbox or test company first, then repeat the same tools against production with the production credential after sign-off.

2. Load in batches

After approval, the load starts with the smallest useful batch. The agent checks the result, then continues in batches while preserving checkpoints and rejected records. It stops on an unsafe partial failure and resumes only from a verified boundary. You can watch progress on the Runs page and abort a run in progress.

Each batch is a run, recorded with its input, each step’s result and the records it wrote. That record is the audit trail of the migration.

3. Reconcile

After the load, the agent compares source and target: record counts, important totals such as open balances by period, rejected records, duplicates, and a sample of transformed fields. It reports in plain language and calls out only the discrepancies that need action.

Ask for a reconciliation artifact when the client needs a signed document. It covers the agreed scope, the final mapping, validation results, remaining risks and the cutover plan, and exports to PDF or Word.

4. Cutover

The migration tools are saved and repeatable. A typical cutover is:

1. A full load into the sandbox and client sign-off on the reconciliation.
2. A full load into production at the cutover date.
3. A delta load of records changed since the full load, using the same tools with a date filter.
4. Reconciliation of production, exported as the handover document.

Plan the cutover as project tasks with owners and a timeline, so the client sees the freeze window, the load sequence and the go or no-go decision in one place. Ask the agent to draft them from the migration scope.

After go-live

Clients who keep the legacy system running, or whose other applications still feed it, need ongoing syncs. See Post go-live. For the closing documents and the audit trail, see Handover.