Most of the Voicify "Competitor A or Competitor B" battlecard library assumes a net-new evaluation — buyer has no incumbent voice-AI in production, the rep is competing for a clean buy decision, and the artifacts that fire are the discovery brief, the demo script, the pilot scorecard. The migration battlecard is the artifact that fires when none of that is true — the buyer has been running Competitor A (horizontal voice-AI platform) or Competitor B (dental-pure AI receptionist) in production for 12-24 months and is weighing the cost of switching to Voicify against the cost of staying put. The deal economics are different. The risk catalog is different. The cutover plan is the deliverable, not the demo. This battlecard covers the six topics that decide whether the buyer switches: switching cost math, data migration scope by PMS, contract overlap, staff retraining, clinical-safety bridge, and the 90-day post-cutover validation scorecard.
TL;DR
Displacement is not evaluation. When the buyer already runs Competitor A or B in production, the rep is not selling capability — the rep is selling a switch that beats the sunk cost. A-slot migration cost lands $4-9k one-time with 6-9 month payback; B-slot migration lands $2-5k with similar payback. The dual-running overlap window is 30-45 days for single practice, 60-90 for DSO. The rep deploys six artifacts in sequence: switching-cost calculator, PMS data migration scope, contract overlap and dual-running plan, staff retraining map, clinical-safety bridge, and the 90-day validation scorecard. Three failure modes — change-management fatigue, clinical-safety fear, contract-tail friction — kill more migration deals than pricing does.
When to Deploy the Migration Battlecard (Not the Net-New Battlecard)
The trigger is simple but rigid. The migration battlecard fires the moment the discovery brief tags an incumbent in the A-slot or B-slot field — not "shortlisted" or "evaluating," but "running in production today." The brief's incumbent-in-production flag is a hard switch in the trigger map: it overrides the default comparison-matrix artifact for the discovery stage and routes the rep to the migration sequence. The reason is that the buyer's decision math is fundamentally different. A net-new buyer asks "which platform is better." A migration buyer asks "is the upgrade worth the switching cost and the staff disruption and the contract overlap." The artifacts that answer the second question are not the same as the artifacts that answer the first, and a rep who deploys the comparison matrix to a migration buyer signals — accurately — that the rep has not understood the actual decision the buyer is facing.
One caveat. If the buyer is on a free trial of Competitor A or B that has not yet converted to paid contract, the deal is technically a net-new evaluation, not a migration. The rep should still note the trial in CRM and use a hybrid approach — the comparison matrix as the lead artifact, the switching-cost calculator as a defensive insert if the buyer raises the data they have already loaded into the trial. Once the trial converts to paid contract or the buyer crosses 90 days of live production use, the deal becomes a true migration and the full battlecard fires.
The Switching-Cost Calculator: Real Numbers by Slot
The migration battlecard's first artifact is the switching-cost calculator. The buyer's CFO will ask for it before the buyer's office manager does, so the rep presents it without being asked. The structure is a four-line one-time cost stack plus the 12-month total-cost-of-staying number from the pricing battlecard, with the payback period calculated as a function of the per-month savings delta.
| One-Time Switching Cost | A-slot incumbent (horizontal voice-AI) | B-slot incumbent (dental-pure receptionist) |
|---|---|---|
| PMS reintegration setup | $1,500 - $3,500 | $800 - $1,800 |
| Call-flow rebuild (custom prompts + triage) | $1,200 - $2,800 | $400 - $1,200 |
| Staff retraining (8-12 hours, 3-5 staff) | $800 - $1,600 | $800 - $1,600 |
| Dual-running overlap (30-45 days at 50% list) | $500 - $1,200 | $300 - $700 |
| One-time total | $4,000 - $9,100 | $2,300 - $5,300 |
| Typical payback period from monthly delta | 6 - 9 months | 5 - 7 months |
The A-slot migration is higher cost because the PMS integration depth of the horizontal incumbent is typically less mature — the rebuild on Voicify is a true upgrade, not a lateral move, and the rebuild captures features the incumbent never delivered (PMS write-back, schedule-gap detection, recall-list integration). The B-slot migration is lower cost because the incumbent's PMS integration was already shallow and the call-flow customization was modest — the rebuild is mostly a one-for-one mapping. The payback window in both cases assumes the pricing delta the rep showed in the procurement conversation; if the buyer's CFO discounts that delta, the payback window stretches and the rep escalates pricing through the AE-to-RevOps path the trigger map defines for that signal.
Data Migration Scope by Practice Management System
The second artifact is the PMS-specific data migration scope. The buyer's office manager — not the CFO — runs this conversation, and they want a checklist, not a sales pitch. The migration scope spans four PMS environments: Dentrix, Eaglesoft, Open Dental, and Curve Dental. Each has a different export surface and a different reintegration path.
| PMS | Exported from incumbent | Reintegrated to Voicify | Time |
|---|---|---|---|
| Dentrix | Appointment templates, recall codes, provider IDs | Voicify Dentrix bridge + write-back validation | 3-5 days |
| Eaglesoft | Appointment types, op-codes, fee schedule mappings | Voicify Eaglesoft bridge + scheduler test | 4-6 days |
| Open Dental | Definitions table, appointment views, provider list | Voicify Open Dental connector + 3-day shadow run | 2-4 days |
| Curve Dental | Cloud API export, appointment + recall config | Voicify Curve OAuth + production cutover same-day | 1-2 days |
The migration scope is the artifact the office manager forwards to their IT support or DSO operations team. The rep does not need to be technical to deliver it — the rep needs to deliver it accurately, with the right PMS-specific time estimate and the named Voicify integration engineer who owns the cutover. The single most common rep mistake is to promise a one-day migration on Dentrix or Eaglesoft. The honest answer is 3-6 days including shadow-run validation, and the office manager will trust the rep more for the honest answer than for the aspirational one.
Contract Overlap and the Dual-Running Window
The buyer's incumbent contract has a tail. The contract started 12 or 18 months ago and there are 4-10 months remaining before natural termination. The buyer's CFO does not want to pay the tail and the new vendor simultaneously, and the rep's job is to make the dual-running window painless on cash flow without inventing a discount that the rep cannot deliver.
The structure that works in 80% of migration deals: Voicify at 50% list during the dual-running overlap window (30-45 days single-location, 60-90 days multi-location DSO), full list starting the day the incumbent contract terminates. The 50% is not a free month and not a permanent discount — it is a one-time accommodation that reflects the genuine fact that the buyer is paying two vendors for a defined window during which both vendors are actively running. The rep presents this without being asked, because the buyer's CFO will ask within the next two meetings and an unprompted offer reads as good faith. The dual-running window is also the period during which the migration battlecard's clinical-safety bridge runs — the two purposes overlap by design.
One edge case. If the incumbent contract has more than 10 months remaining, the contract-tail math may break the deal even with the 50%-overlap structure. The rep then escalates to RevOps for a deeper accommodation — typically a one-time contract-buyout credit calculated as a percentage of the remaining tail. This is not standard authority and the rep does not promise it in the first meeting. The escalation is the trigger-map's pricing-pushed-beyond-AE-ceiling signal and the rep follows the escalation protocol.
The Staff Retraining Map and Clinical-Safety Bridge
The buyer's office manager is the gatekeeper of staff retraining and the buyer's clinical lead — owning DDS or hygienist — is the gatekeeper of clinical-safety bridge. Both worry about the same thing from different angles: the front-desk team just learned the incumbent system, and putting them through another training cycle while keeping after-hours emergency triage reliable is the single largest perceived risk in the deal.
The staff retraining map is a side-by-side workflow document. Column 1 is the incumbent's workflow for the most common front-desk task — handling an after-hours emergency call, booking a new patient, processing a recall confirmation, escalating to a clinical decision. Column 2 is Voicify's equivalent workflow, mapped step-for-step. The named Voicify onboarding lead — not the AE — runs the training in-office across 2-3 sessions during the dual-running window. The artifact is the document; the value is the named human who delivers it. Practices buy on the named human.
The clinical-safety bridge is the dual-running window's clinical insurance policy. During the overlap, both systems run on the same incoming-call volume and the clinical lead reviews the differential — calls Voicify routed differently from the incumbent, calls Voicify escalated that the incumbent did not, calls the incumbent escalated that Voicify did not. The review is daily for the first 7 days, then 3-times-a-week through end-of-overlap. If the differential is clean, the clinical lead signs off on cutover. If the differential is concerning, the clinical lead pauses cutover and the rep extends the overlap rather than pushing the cutover date. Pushing a clinical lead past their comfort line on safety is a lost deal even after signature — the buyer cancels in week 60 and the rep loses the renewal and the reference.
The 90-Day Post-Cutover Validation Scorecard
The migration battlecard's final artifact is the 90-day validation scorecard the rep hands to the customer success team at the moment of cutover. The scorecard is a small set of measurable outcomes that the CSM reviews with the buyer at day 30, day 60, and day 90. It is the migration's analog to the net-new pilot scorecard — same idea, different trigger, different success bar. The bar is that Voicify has to do better than the incumbent did, not just as well, because the buyer is paying for an upgrade and not a swap. The five lines on the scorecard are: after-hours coverage uptime (Voicify ≥ incumbent's last 90-day average), incoming-call-to-booked-appointment conversion (Voicify ≥ incumbent + 4 percentage points), clinical mis-triage incident count (Voicify ≤ incumbent over 90 days), staff satisfaction (front-desk lead's blind rating ≥ 4/5), and PMS write-back error rate (Voicify ≤ 1% of routed calls). If four of five hit at day 90, the migration is a confirmed success and the CSM moves the account into the B-slot defense rotation for installed-base protection.
Failure Modes: What Kills Migration Deals Where the Math Works
Three failure modes recur. Change-management fatigue from the front-desk team is the most common and the hardest to surface — the office manager is the one who says "we just trained them on the incumbent, I cannot put them through it again," and the rep cannot fix it with a slide. The fix is the named onboarding lead and the side-by-side workflow map, deployed early enough that the office manager sees the retraining is bounded and supported, not a months-long project.
Clinical-safety fear from the clinical lead is the second. The cure is the dual-running clinical-safety bridge with daily-then-tri-weekly differential review, and the rep's willingness to extend the overlap if the differential is unclean. Reps who try to compress this lose the deal in week 6 of cutover. Contract-tail friction from the CFO is the third — the buyer assumes the 4-10 months of incumbent contract are a no-go and the rep has to show, with the switching-cost calculator and the 50%-overlap structure, that the 12-month total-cost picture still favors the switch even with the tail. Migration battlecard deals are won and lost on whether the rep deploys these three counters proactively in the right sequence. The battlecard tells them what to deploy and when. The rest is delivery.