CRM Exit by Move Big Rocks
The buyer-facing journey is Shadow, Reconcile, and Cut over. Delivery still requires eight controlled stages. Each stage produces evidence and has an exit condition; completing an activity is not the same as proving readiness.
01
Inventory source products, data, relationships, files, workflows, integrations, permissions, reports, users, costs, contract dates, stakeholders, and operating constraints.
Exit condition: The known scope, exclusions, evidence sources, owners, and unresolved questions are recorded.
02
Build the sourced business case for staying as-is, right-sizing, another SaaS platform, Managed MBR, self-hosted MBR, and bespoke ownership.
Exit condition: The recommendation, confidence, sensitivities, missing evidence, and human decisions are explicit. A migration proceeds only if the evidence supports further proof.
03
Obtain and verify supported bulk exports and incremental access. Record API, retention, package, file, history, and permission limitations before treating the source as covered.
Exit condition: Extracted counts and checksums are reproducible, unsupported scope is documented, and credentials remain outside public website flows.
04
Version the disposition of objects, fields, relationships, owners, permissions, workflows, reports, integrations, and files as direct map, configurable map, rebuild, retain, replace, archive, retire, or unsupported.
Exit condition: Every in-scope capability has an owner, disposition, acceptance rule, and exception path.
05
Run the selected destination beside the authoritative CRM. Load history, apply supported incremental changes, and suppress or redirect external side effects.
Exit condition: The destination processes current in-scope data predictably, synchronization behavior is measured, and failures are visible and recoverable.
06
Compare counts, identity, required content, relationships, files, ownership, permissions, and selected workflow outcomes. Assign exceptions by severity and owner, then retest corrections.
Exit condition: Agreed thresholds pass, material exceptions have an accepted disposition, and the evidence can be reviewed independently.
07
Approve the runbook, freeze writes as planned, apply the final delta, repeat acceptance checks, switch controlled entry points, and verify integrations and user access.
Exit condition: The customer authorizes go-live against recorded evidence. Rollback remains available for the agreed window.
08
Monitor the production system, resolve or roll back material issues, archive the source according to policy, test operational procedures, and transfer administration and support ownership.
Exit condition: Stabilization gates pass, responsibilities and runbooks are accepted, data export remains available, and source retirement is an explicit customer decision.
09
CRM Exit can recommend readiness; it cannot replace the customer's go/no-go authority. Agents may prepare evidence and identify gaps, but they do not approve assumptions, migration scope, cutover, rollback expiry, or source retirement.
Make the next decision