Switching CRMs without losing pipeline visibility
How to cut over to HubSpot without a blackout week, a broken forecast or reps working out of their inboxes.
The short answer: To switch CRMs without losing pipeline visibility, rehearse the migration twice, cut over away from quarter end, freeze edits in the old CRM for an announced window, reconcile open pipeline by stage and owner before switching, keep a rollback plan, and leave the old system read-only for reference afterwards.
The question sales leaders ask most about a CRM switch is simple: how long will we be flying blind? In a badly run move, the answer can be weeks. Data is half-moved, reps don’t know which system to update, and the forecast becomes a guess. In a well-run move, the answer is: not at all.
Why pipeline visibility gets lost
- No freeze point. Reps keep updating the old CRM while data is moving, so HubSpot is out of date on day one.
- No clear source of truth. For a while nobody knows which system holds the real numbers, so people update both, or neither.
- Nobody checks the totals. The data loads, but nobody confirms that open pipeline in HubSpot matches the old system.
- Reps can’t find their deals. Views, stages and dashboards weren’t set up to match how they work.
How a controlled cutover works
Rehearse it first
The real cutover should be the third run of the migration, not the first. Two full rehearsals in a test portal, each reconciled, mean the process and its timing are known in advance.
Pick the right moment
Never switch in the last weeks of a quarter, during a pricing change or in the middle of a major campaign.
Announce a freeze
At an agreed time, the old CRM is frozen for edits. Reps know when, and what to do with anything urgent. The freeze should be measured in hours, not days.
Migrate the final changes and reconcile
After the final load, compare both systems on the numbers leadership cares about:
- Open pipeline value by stage and by owner
- Number of open deals by pipeline
- Deals expected to close this quarter
If they don’t match within the agreed tolerance, the old CRM stays the system of record while the issue is fixed.
Switch the source of truth
Once reconciliation is signed off, HubSpot becomes the system of record. Forms, chat and other lead sources point at HubSpot. Reps start working there that day.
Keep the old system read-only
The old CRM stays available, read-only, for an agreed period so anyone can look up history. It isn’t updated. Then it’s archived and the subscription ends in line with your contract.
Make day one familiar
Before go-live, have each rep’s views, tasks and dashboards ready, and train them in their own pipeline. See how to get your sales team to use HubSpot.
What leadership should see
A one-page reconciliation showing pipeline value, deal counts and owners in both systems side by side, signed by your sales process owner and the migration lead. Without it, you don’t know the forecast survived. That report is part of every Airtight go-live. For the full schedule, see how long a move to HubSpot takes.