Resolve, reconcile, approve, or roll back a migration

Open the import log and select the job. Queued and Processing are still active; Completed is clean; Completed with errors and Failed require correction and cannot be approved.

Review row outcomes. Success created or updated the intended record; Skipped means the record was already imported safely or no duplicate mutation was needed; Failed and Conflict require review.

Correct failed or conflicting source rows and import the corrected file into the same migration project. Successfully imported source records are protected from replay, and corrected records can resolve earlier errors.

Import every dataset selected at the beginning of the project. A missing planned dataset blocks approval even if every uploaded job completed successfully.

Select Reconcile and approve only after all files finish. Reconciliation requires every source row to equal the sum of imported, skipped, failed, and conflicting outcomes, with zero failures and conflicts.

For Setmore appointments, resolve any missing report dates, periods longer than the supported range, gaps, overlaps, or incomplete coverage of the declared history.

Perform business reconciliation outside the row counts: compare appointments by date and status, sample client identities, sales/tax/payment totals, package liabilities, and inventory quantities and value.

Record controlled exclusions and concierge transformations. Unsupported data cannot be counted as migrated merely because the supported files reconcile.

Complete the final delta after freezing the old system, test booking, reminders, forms, payments, receipts, terminals, and public links, then obtain business sign-off.

Approve the migration using recent account verification. Approval records the approver, time, planned datasets, coverage, and row reconciliation and closes automatic rollback.

Before approval, Roll back migration can remove records created by a clean migration in dependency-safe reverse order. Rollback stops if those records are now used by other data.

If the migration updated existing records, has already been approved, or rollback stops to protect newer work, contact migration support for a controlled restore instead of deleting or overwriting records manually.