Parallel Running: Operating Two CRMs During Transition
You are weeks from cutover and the big-bang plan looks simple on a slide. Overnight switches are how teams discover that pipeline, associations, and forecasts only match in theory. Parallel running keeps the old CRM live while the new one shadows, so you prove the dual CRM path before licence spend doubles permanently.
We design the parallel-run window, reconciliation cadence, and cutover gate that make the switch safe.
Sound Familiar?
These are the exact pressures our clients faced weeks before a dual CRM cutover:
- The board wants a Friday-to-Monday CRM cutover, and nobody can explain what happens if Monday's pipeline numbers are wrong
- Sales is already dual-entering deals into both CRMs, burning 60–90 minutes a day with no reconciliation to prove they match
- Dual CRM licences are running open-ended because cutover keeps slipping, and finance is asking when the double spend stops
- Nobody owns the cutover gate: no drift threshold, no consecutive clean reconciliation days, no written go/no-go
- Read-only shadow and dual-write are treated as the same thing, so conflicts pile up and nobody knows which system is authoritative
Salesforce raised Enterprise and Unlimited list prices by an average of 6% on 1 August 2025, and renewals without uplift caps keep compounding. Licence renewals and end-of-contract windows are exactly when teams feel pressured into a big-bang cutover. That pressure is when parallel running matters most.
What Parallel Running Actually Does
Old CRM stays live → new CRM shadows → reconcile daily → cut over only when the gate passes.
Old CRM Stays Live
Sales keeps working in the source system. It remains the fallback until the gate says otherwise
New CRM Shadows
Read-only feed mirrors deals, contacts, and companies so mapping and reports can be tested safely
Reconcile on Cadence
Daily counts, field samples, and association checks. Drift alerts before anyone trusts the new system
Gate, Then Cut Over
Pass written go/no-go criteria, flip ownership, keep source read-only, cancel seats on schedule
Everything You Need for a Safe Dual CRM Cutover
Parallel Run Window Design
A fixed dual CRM calendar (typically four to eight weeks for mid-market) with freeze windows, owners, and a hard end date so licence overlap does not become permanent.
Read-Only Shadow Mode
Old CRM stays live for the business. New CRM shadows via one-way sync so you validate mapping and reports without risking write conflicts.
Controlled Dual-Write
When shadow proves clean, critical objects switch to dual-write with stable keys and clear ownership rules so both systems stay aligned.
Reconciliation Cadence
Daily (or faster) count, field, and association checks with drift alerts. Cutover only after consecutive clean cycles, not after a hopeful weekend.
Cutover Decision Gate
Binary go/no-go criteria: forecast parity, association integrity, workflow smoke tests, and a signed decision before seats switch permanently.
Dual-Licence Cost Control
Seat overlap priced in Rand, capped by the parallel window, with a planned read-only hold on the source CRM after cutover instead of an open cheque.
Platforms We've Run Parallel Cutover On
From Open-Ended Dual Licences to a Six-Week Parallel Run
How a 45-seat professional services firm avoided a Friday cutover, proved the new CRM in shadow, and stopped dual spend on schedule.
The Big-Bang Plan
- Board slide said Friday lock, Monday go-live, cancel old seats Tuesday
- Twelve power users already dual-entering deals for ~90 minutes a day
- Dual CRM licences already open for two months with no end date
- No shadow mode, no reconciliation cadence, no written cutover gate
- Finance forecasting four months of overlap if cutover slipped again
The Parallel Run
- Three-week read-only shadow with daily reconciliation, then dual-write on deals and contacts
- Eleven mapping defects caught before any seat cancellation
- Cutover gate passed after three consecutive clean reconciliation days
- Old CRM moved to read-only for 60 days, then seats cancelled on schedule
- Dual entry stopped once shadow parity held; sales worked one system again
Big-Bang Cutover vs Parallel Running
How It Works
From first conversation to gated cutover in a designed parallel-run window.
Cutover Risk Review
Seat counts, deal cycle length, which objects must stay live, and whether you are weeks from a big-bang switch you should not make.
Parallel Run Scope Call
30-minute call to choose shadow vs dual-write, set the window length, and define the reconciliation and go/no-go gates.
Shadow, Reconcile, Dual-Write
We stand up the dual path, run daily reconciliation, surface mapping defects, and only then open dual-write on critical objects.
Gate, Cut Over, Cap Licences
Pass the written gate, flip ownership to the new CRM, keep the old one read-only for the hold period, then cancel seats on schedule.
Frequently Asked Questions
What is parallel running in a CRM migration?
Parallel running (also called dual CRM or dual running) means the old CRM stays available while the new one is proven against live work. Industry playbooks typically run both systems for two to four weeks at minimum, and four to eight weeks for mid-market switches, with reconciliation before you cancel seats. It is a cutover risk strategy, not a permanent operating model.
Should we dual-write or run a read-only shadow first?
Start with read-only shadow: the old CRM remains authoritative while the new system receives a one-way feed for validation. Dual-write comes later, only for objects that need both sides writable, and only after reconciliation drift stays near zero. Jumping straight to dual-write without a shadow window is how conflicts and "which system is right?" meetings start.
How long should we run two CRMs, and what does dual licensing cost?
Well-planned mid-market switches typically dual-run for four to eight weeks, then move the source to read-only for 60 to 90 days before cancelling. At roughly R18.50 to the dollar, a 50-seat Salesforce-class overlap near $8,250 per month is about R153,000 per month in licence overlap alone. Every unstructured extra month is pure waste.
What is the cutover decision gate?
A written go/no-go checklist: record and association parity within agreed thresholds, forecast and board-report variance within tolerance for consecutive reconciliation cycles, workflow smoke tests passed, and dual-entry stopped. Research puts meaningful data loss or corruption near 40% of CRM migrations when teams skip that discipline. Import completion is not the gate. Proven parity is.
How long does a structured parallel-running engagement take?
Design and setup usually take one to two weeks, then the parallel window itself runs four to eight weeks depending on deal cycle and object complexity. Simple contact-and-deal environments land toward the shorter end. Heavy custom objects and many integrations need the full window, still with a hard licence end date.
How much does a parallel-running cutover strategy cost?
Focused parallel-run design, shadow sync, reconciliation, and cutover gating for mid-market CRMs typically lands between R35,000 and R85,000. Against R153,000-plus per month in dual licences and the R1.9 million to R4.4 million range often cited for mid-market failed CRM rescues (about $105,000 to $240,000 at R18.50), most clients recover the fee inside one or two dual-run months avoided.
Stop Betting the Pipeline on a Big-Bang Switch
If you are weeks from cutover and dual CRM spend is already running without a gate, you are paying for risk instead of buying proof.
Tell us which CRM you are leaving, which you are joining, how many seats overlap, and when the board expects go-live. We will show you a parallel-running window, shadow vs dual-write path, and the cutover gate that protects the switch.