# A displacement plan includes the current vendor's contract end date and the cost of switching

Template, Competitive displacement, read 10 Nov 2026

**The short answer.** Thirteen steps over about eighty days. The template starts with the incumbent's contract date, a list of what the buyer must replicate, a migration plan and a comparison the champion can show to the economic buyer, so a switch is argued on fact.

## When to use it

Use when the buyer already uses a rival product, has a contract end date or a reason to leave, and must migrate users or data.

## The plan, step by step

Day 0 to day 80

| Day | Step | Owner | Side | Done when |
| --- | --- | --- | --- | --- |
| 0 | Find out why the buyer is considering a switch | Seller: account executive | seller | The reason is stated by the buyer and recorded on the plan. |
| 2 | Get the incumbent's contract end date | Buyer: procurement contact | buyer | The date and notice period are on the plan. |
| 5 | List what must be replicated | Buyer: current administrator | buyer | A list of required features and integrations is attached. |
| 8 | Map the current users and data | Buyer: current administrator | buyer | Counts and data types are recorded. |
| 10 | Confirm the comparison criteria | Buyer: champion | buyer | Written criteria, each with a pass test, are on the plan. |
| 18 | Run a side-by-side evaluation | Both: solutions engineer and evaluator | both | Each criterion has a result recorded. |
| 25 | Plan the migration | Seller: services lead | seller | Steps, owners, downtime and fallback are on the plan. |
| 32 | Present the case to the economic buyer | Buyer: champion | buyer | The economic buyer has seen the comparison and stated a decision date. |
| 36 | Complete security review | Buyer: IT or security lead | buyer | Findings are closed or accepted. |
| 48 | Agree contract and start date | Both: legal contacts and procurement | both | The start date is set after the incumbent's notice period. |
| 55 | Obtain signature | Buyer: economic buyer | buyer | The signed contract is on record. |
| 65 | Run the migration | Both: services lead and administrator | both | Users and data are moved and checked against the counts. |
| 80 | Switch off the incumbent | Buyer: current administrator | buyer | The old tool is closed and its notice is given before its end date. |

## Where plans like this stall

- Missing the incumbent's notice period, which delays the switch by a full term.
- Comparing on features without a pass test.
- Planning the migration after signature, when the buyer's staff are already stretched.

## Running it in a tool

The [MAP Tool Matrix](/tools/) shows which tools keep the plan where the buyer already is, send nudges and sync to the CRM; [the tool ranking](/platforms/) weighs the plan at 30 of 100.

## Sources

- MEDDICC, MEDDPICC methodology: decision process and paper process: https://meddicc.com/meddpicc-sales-methodology-and-process (read 10 Nov 2026)
- Rocketlane help center: project plan: https://help.rocketlane.com/support/solutions/articles/67000699280-project-plan (read 10 Nov 2026)
- GUIDEcx: Salesforce integration and project templates: https://www.guidecx.com/products/integrations/salesforce/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://themutualactionplan.com/templates/competitive-displacement/
