The replatform decision, made with evidence
Most replatform conversations start from a mood, not a constraint. Before scoping a migration, name the specific thing the current platform cannot do, because in a growing number of cases, it already can.
AUTHOR
Director at Lucent Commerce. 13 posts, newest first.
Most replatform conversations start from a mood, not a constraint. Before scoping a migration, name the specific thing the current platform cannot do, because in a growing number of cases, it already can.
Put performance in the redesign as a constraint, not as a workstream. A speed project bolted onto a rebuild gets cut, and a speed project run just before one gets thrown away.
A CDP does not fix your customer data. It gives the mess a new address, and charges you per profile for the privilege.
Your 3PL already runs a warehouse management system. Buying a second one rarely fixes the problem you have, which is almost always that nobody agreed who owns the stock number.
Agree how much failure is acceptable before it happens, measure the business event rather than the HTTP status, and name what changes when the budget is spent.
Freezing your own repository is the easy half. The changes that break peak come from counterparties whose release calendar you have never asked for.
Shopify already resizes, converts and caches your images. Most slow stores are slow because the theme asks for the wrong size, not because the CDN is missing.
Every speed project is the same three decisions applied to every file the page asks for. Most of them start with the wrong one.
The connector is the easy part. What decides whether this works is which system owns each object, and what happens the week one of them is wrong.
How to rehearse a migration cutover: run the full sequence on real data, time every step, and practice the rollback before launch night.
Peak does not break integrations. It removes the slack that was hiding a design fault, and the failure it produces tells you exactly which one.
The catalog is the easy part. The budget goes on URLs, integrations and the extensions that have no Shopify equivalent.
NEXT STEP
A senior Shopify engineer reviews your storefront, theme performance and checkout, then sends a prioritized list of fixes.