When a replatform is the wrong answer

Dear reader,

I turn down more replatform projects than I take on, and I think that's the honest way to work. A migration is one of the biggest, riskiest things you can do to a store, and quite often it solves a problem you don't actually have.

The urge is usually a symptom

When someone tells me they need to move platforms, the real driver is usually one of these:

• The store feels slow, so it feels old
• One workflow is painful and everyone's sick of it
• A competitor relaunched and now yours looks tired
• An agency said a rebuild is the only way forward

None of those, on their own, require leaving your platform.

Try the cheaper cure first

Before you commit to months of work and real migration risk, ask what a focused fortnight could fix.

1. Measure the actual pain — is it speed, admin friction, or design?
2. Fix the top three — the specific pages or flows that hurt
3. Re-check the numbers — did conversion or workload actually improve?
4. Then decide — replatform only if the ceiling is genuinely reached

Most stores are running at 60% of what their current platform can do. Moving house won't fix a room you haven't tidied.

When it is right

Sometimes migration is the correct call — your platform can't support your tax model, your catalogue has outgrown it, or the maintenance cost is genuinely higher than a rebuild. That's real, and I'll say so plainly.

The point isn't to avoid replatforming forever. It's to make sure you're spending six figures on a cure, not on a fresh coat of paint. If you want help telling the difference, book advisory time and we'll pressure-test it together before you spend a penny.