Migration plan

Eight weeks, signed exit criteria, zero close-week drama

Migrations into a finance system are won or lost on exit criteria. This is the same plan we use with every customer — week by week, with owners and the signed evidence required to move on.

Default plan

8 weeks

From signed MSA to active mode

Cutover rollback

≤ 60 s

One command, audited

Shadow window

≥ 2 weeks

Variance vs incumbent < 0.25%

Audit-ready

W7

Walk-through with your auditor

Week-by-week plan

WeekTitle
W0Mutual NDA, data room access, MSA + DPA
W1Read-only connect to ad platforms & ERP
W2Shadow pacing & alerts
W3Cutover plan + rollback test
W4Cutover · monitoring mode
W5–6Active mode & payouts
W7Audit trail handover
W8Exit criteria signed

By source system

Spreadsheets + email

Effort
Low (4–6 weeks)
Risks
Discovery of un-tracked accounts; reconciliation surprises in month 1
Assets we bring
We auto-discover platform accounts and pre-fill budgets from history.

In-house ledger

Effort
Medium (6–8 weeks)
Risks
Schema mismatch; custom rules; SSO + RBAC mapping
Assets we bring
Schema mapping templates; CSV/Parquet importers; SSO handover playbook.

Competitor SaaS

Effort
Medium (6–10 weeks)
Risks
Contract overlap; data export limits; auditor sign-off
Assets we bring
We co-sign a contract-overlap credit; data export adapters for the top 4 competitors.

Our commitments during migration

  • No close-week cutovers; cutover never lands in the customer’s fiscal close window.
  • Shadow mode for at least two full weeks before any state-changing action.
  • Customer auditor invited to W7 walk-through at our expense.
  • If exit criteria slip, the contract clock pauses until they are signed.