CRM migrations have a reputation for costing a sales team a quarter. Forecasts stop being reliable, reps keep deals in spreadsheets “until the new system settles”, and leadership loses sight of the pipeline exactly when it needs it most. Most of that damage is not caused by the new platform. It comes from the sequence: migrate everything, switch everyone over on one date, and hope reporting catches up.

A different sequence keeps the pipeline visible the whole way through. It takes more planning up front and much less firefighting later.

Protect the pipeline first

Start by deciding what must not break. For most sales organizations the list is short:

  • Open opportunities with their stage, value, close date and owner.
  • The weekly forecast and pipeline review.
  • Activity history on accounts with open deals.
  • Commission and quota reporting, if it depends on CRM data.

Everything else, from old closed deals to archived campaigns, can follow later. Writing this list down early stops the migration from being planned around data volumes instead of business continuity.

Agree on the pipeline model before moving data

A migration is often the first time anyone compares how stages are used in practice. If teams use the old stages differently, moving them unchanged carries the confusion into the new platform. Changing them without a mapping makes historical comparison impossible.

Settle this first. Define the target stages with clear exit criteria, map each old stage to a new one, and decide what happens to deals that fit nowhere. Get sales leadership to sign off. This is also the moment to agree on the handful of fields the forecast depends on and make them mandatory in the new system.

A sequence that keeps sales working

  1. Build reporting outside both systems. Before cutover, set up pipeline reporting in a shared data layer or BI tool that reads from the old CRM. The forecast then no longer depends on which system is live.
  2. Migrate reference data early. Accounts, contacts, products and users move first, are checked by their owners, and stay in sync during the transition.
  3. Rehearse in full. Load a complete copy of the open opportunities into a test environment and compare totals by stage, owner and close month against the old system. Repeat until the numbers reconcile.
  4. Point reporting at both systems. Extend the shared reporting so it reads from the new CRM too, and confirm that the same pipeline gives the same figures from either source.
  5. Cut over by team, not by date. Where the platforms allow it, move one sales team or region at a time. The shared reporting combines migrated teams with those still on the old system, so leadership keeps seeing one pipeline.
  6. Freeze the old system team by team. As each team moves, make its records in the old CRM read-only. Two editable copies of the same deal is how pipelines get double-counted.
  7. Migrate history last. Closed deals and old activities move once the open pipeline is stable. They matter for analysis, not for this quarter’s forecast.

Timing the cutover

Avoid the last weeks of a quarter or a fiscal year. Reps are closing deals and leadership is forecasting, so nobody has time to learn new screens or check migrated records. The weeks just after a quarter starts are usually calmer, and the new quarter’s forecast is still forming.

Plan a hypercare period after each team’s cutover. Someone should be available to answer questions the same day, and a short daily check should confirm that pipeline totals still match what the team expects.

Failure patterns

  • Big-bang cutover with no fallback. When something goes wrong, the whole sales team is affected at once.
  • Reporting rebuilt after go-live. The new dashboards arrive weeks late, and leadership runs the business from exported spreadsheets in the meantime.
  • No reconciliation. Data is moved but nobody proves the totals match, so trust erodes with the first discrepancy.
  • Orphaned owners. Deals still assigned to people who have left the company disappear from everyone’s view after migration.
  • Training on features instead of workflows. Reps learn the new menus but not how to run their weekly pipeline review in the new tool.

What to measure during the transition

Keep the checks simple and visible to sales leadership: open pipeline value by stage in both systems, the number of opportunities without an owner or close date, and how many deals were updated in the past week per rep. A sudden drop in updates is usually the earliest sign that people have gone back to spreadsheets.