The Situation
A leading health data platform had released a next-generation version of one of its core data products. The new product was a significant improvement: better data coverage, more efficient pipelines, and new capabilities that unlocked use cases customers had been asking for. But roughly 60% of the customer base was still running on the legacy version.
This created a dual problem. For customers, staying on the legacy product meant missing out on meaningful enhancements that could drive better outcomes. For the company, maintaining the legacy data pipeline was expensive: higher storage costs, greater compute consumption, and engineering resources tied up supporting an older architecture. Every month without migration eroded margins and increased the risk that customers would churn at renewal rather than adopt the change.
What We Built
Rather than treating this as a technical migration with a deadline, CS leadership designed a comprehensive, customer-first migration strategy that addressed messaging, delivery, feedback, and executive engagement simultaneously:
- External messaging plan: A unified communication strategy that led with value, not urgency. Every touchpoint framed the migration around what customers would gain (new capabilities, better data quality, faster performance) rather than what was being deprecated.
- Structured content delivery: Migration guides, product walkthroughs, and comparison documentation built and sequenced so customers had the right information at the right time. Support and CS teams were trained on the new product so they could guide customers through the transition confidently.
- Client-to-product feedback loops: Structured channels for customers to surface migration concerns, feature gaps, and friction points directly to the product team. This ensured that real customer input shaped the migration experience and that blockers were resolved quickly.
- Strategic executive involvement: For the largest and most complex accounts, senior leadership engaged directly to reinforce the strategic rationale, address concerns, and ensure these high-value customers felt supported throughout the transition.
- Phased rollout with risk tiering: Customers were segmented by complexity, revenue, and risk profile. Lower-complexity accounts migrated first to build operational confidence, then higher-stakes accounts with the playbook already proven.
The Execution
| Phase | Timeline | What Happened |
|---|---|---|
| Planning | Weeks 1 to 4 | Customer segmentation, risk tiering, messaging development, internal team training, and migration tooling setup. |
| Wave 1 | Weeks 5 to 10 | Lower-complexity accounts migrated first. Feedback loops activated. Playbook refined based on early learnings. |
| Wave 2 | Weeks 11 to 18 | Mid-tier and complex accounts. Executive engagement for strategic accounts. Product team resolving blocker issues in real time. |
| Wave 3 | Weeks 19 to 24 | Remaining high-complexity accounts. Final stragglers with bespoke migration plans. Legacy pipeline decommissioning began. |
The Results
- Zero incremental churn across the entire migrated customer base. Not a single customer left because of the migration.
- Increased renewal revenue as customers on the new product adopted expanded capabilities and upgraded their contracts.
- Improved margins from decommissioning the legacy data pipeline, reducing storage and compute costs.
- Stronger customer relationships as the migration became a trust-building exercise rather than a disruption.
- Reusable playbook that became the template for future product transitions across the organization.
Why It Worked
Product migrations fail when they are treated as technical projects with a deadline and a blast email. This one succeeded because it was designed as a customer success initiative from the start:
- Value-led messaging gave customers a reason to move, not just a mandate
- Feedback loops ensured the product team was solving real blockers, not assumed ones
- Risk tiering let the team build confidence before tackling the hardest accounts
- Executive involvement on key accounts signaled that this mattered at the highest level
The Perennial Connection
Product migrations, platform transitions, and packaging changes are among the highest-risk moments in a customer relationship. Most companies underinvest in the post-sales infrastructure needed to execute them well, and pay for it in churn, delayed timelines, and damaged trust.
Perennial's Build Sprint is designed for exactly this kind of challenge: a compressed, operator-led engagement that builds the migration playbook, communication framework, risk segmentation, and execution plan your team needs to protect revenue and deliver customer value through the transition.