Software Replatforming Research Note

Software Replatforming Research Note

Replatforming is the controlled movement of customers, data, traffic, operations, and organizational attention from an old platform to a new one. A successful technical cutover can still be a failed company transition if customers, revenue, support, compliance, or operating knowledge are lost.

LivePerson's 2016 annual report attributed an 8 percent decrease in business revenue partly to rapid customer migration, delayed expansion, and cancellations. The 2018 annual report said migration to LiveEngage was completed in 2017, the legacy offering reached end of life in the second quarter, and renewed selling contributed to later growth.

Stripe's engineering account of online migrations at scale supplies a complementary technical pattern: dual write, move reads, move writes, then remove old data. Stripe used incremental rollout and production comparison to preserve service while changing the data model.

The two cases operate at different grains. LivePerson covers a company and customer platform transition. Stripe covers a high-availability data migration. Together they support explicit gates for data parity, customer readiness, revenue exposure, operational support, irreversible action, and legacy retirement.

The old platform should not be removed merely because the new system exists. The new system needs an authoritative source of truth, tested workflows, migrated customers, observable behavior, recovery paths, and an approved exception strategy.

The transition also needs a final date. Endless dual operation compounds cost and lets the old system veto architecture, staffing, and product decisions indefinitely.