The riskiest part of replatforming is rarely the new platform. It is the knowledge buried in the old one - the rules, workarounds and integrations the business depends on without ever writing them down.

Where operational knowledge hides

Before anything moves, it helps to know where to look:

  • Pricing and account rules added over years of customisation.

  • Integration mappings and scheduled jobs that keep ERP, stock and orders in step.

  • Manual workarounds that teams run without thinking about them.

  • URLs, redirects and content that search engines and customers rely on.

Discover before you decide

Start by understanding customer journeys, operational systems, data, risks and the real reasons for change. Only then select an architecture and platform, based on fit, ownership, cost and maintainability rather than on a feature list.

Migration risk lives in the detail

Data integrity: map, cleanse, migrate and reconcile customers, products, orders, accounts and content. Integration cutover: plan how ERP, payments, fulfilment and other connected services move without losing operational control. URL and search continuity: preserve important URLs, redirects, metadata and indexable content. Operational readiness: use staged cutover, acceptance criteria, rollback planning and clear ownership for launch decisions.

Migrate in controlled stages

Moving data and capability in stages, with reconciliation at each one and a rollback plan throughout, turns one large risk into several small, visible ones.

Keep the context after launch

The knowledge gathered during a migration is valuable long after cutover. A team that retains it can optimise experience and operations after launch instead of rediscovering how the platform works. More on ecommerce replatforming.

Big-bang and phased replatforming

Big-bang cutover

Everything moves at once, so data, integration and search problems surface together at the worst possible moment.

Phased migration

Capability moves in controlled stages with reconciliation and rollback planning, so issues are found and fixed while they are small.

What to take away

  • Document the rules and workarounds before choosing the new platform.

  • Treat data, integrations, URLs and launch readiness as separate risks.

  • Migrate in stages you can reconcile and roll back.

  • Keep the people who gathered the knowledge involved after launch.