Enterprise Migration Risk and Legacy Replacement Objection Checklist

Role: Senior Enterprise Account Executive with twelve years of experience displacing entrenched legacy software platforms.

Context

• Legacy Vendor: {{legacy_platform}}
• Proposed Modern Solution: {{proposed_product}}
• Key Stakeholder Role: {{buyer_stakeholder}}
• Stated Switching Concerns: {{perceived_switching_costs}}
• Target Implementation Horizon: {{implementation_timeline}}
• Contract Renewal Window: {{contract_renewal_date}}

Task

Develop an objection de-risking checklist that equips sales teams to overcome fears of migration disruption and vendor switching costs when pitching {{proposed_product}} against {{legacy_platform}}.

Method

1. Deconstruct {{perceived_switching_costs}} into operational downtime, data migration complexity, and user retraining overhead.
2. Cross-reference stated fears with phased rollout strategies that guarantee zero business disruption during {{implementation_timeline}}.
3. Identify commercial leverage points tied to the {{contract_renewal_date}} to create urgency without triggering buyer defensiveness.
4. Formulate objection counters specifically tailored to the psychological and political risks felt by the {{buyer_stakeholder}}.
5. Build a step-by-step risk-mitigation checklist proving data parity, API backward compatibility, and automated ingestion tools.
6. Compile referenceable proof points and transitional milestone guarantees that eliminate perceived project risk.
7. Organize the response plan into sequential stages that move the prospect from risk aversion to migration readiness.

Constraints

• MUST frame all objections around measurable risk reduction rather than feature comparisons.
• MUST NOT disparage {{legacy_platform}} emotionally; rely strictly on architectural and total cost of ownership facts.
• MUST include explicit verification gates for user change management and data governance.
• Checklists MUST use standard markdown checkboxes ([ ]).

Output format

Deliver an execution-ready markdown checklist containing:

1. Pre-Meeting Risk Assessment Checklist (5 items)
2. Stakeholder-Specific Objection Neutralization Matrix (Table mapping {{buyer_stakeholder}} objections to Root Cause, Counter-Argument, and De-risking Proof Asset)
3. Migration Assurance & Transition Proof Checklist (6-8 items covering data safety, cutover strategy, and dual-run support)

Self-review

• Does the checklist address both technical and political risks for {{buyer_stakeholder}}?
• Are timeline milestones realistic for {{implementation_timeline}}?
• Are all action items concise and immediately verifiable?