Ecommerce Replatforming: When It Is Worth It, and When It Is Not

Ecommerce replatforming is worth it when the platform itself is what holds the business back: it is losing support, every change needs a developer, or the work you need next would mean rebuilding anyway. It is not worth it when the real problem is a slow theme, one failing integration or a dated design, because those can be fixed where you are for a fraction of the cost. At #10 we move stores onto Shopify and Shopify Plus, and the first thing we do is work out which of those two situations a store is actually in.

That check matters more than the platform comparison most teams start with. The useful question isn’t which is the right ecommerce platform in general, but whether yours is still the right one for the business you run now. An ecommerce platform migration is expensive, it takes months, and for a while it puts search rankings and customer data at risk. Done for the wrong reason, it buys a new set of problems and keeps the old ones, because the old ones were never about the platform.

This guide is the business case: the signs you have outgrown a platform, what staying really costs, what moving costs, and when to fix in place instead. Already decided to look at a move? Our companion piece, replatforming: a decision framework for ecommerce teams, covers how to run the decision with your team.

Signs you have outgrown your ecommerce platform

Most ecommerce businesses don’t outgrow a platform in one moment. The cost shows up as friction that slowly gets treated as normal. These are the signals we look for, and what usually sits behind each one.

What you notice	What it often means	Usually points to
Support for your version is ending	Security patches stop and the upgrade path is a rebuild	Replatform
A promo or landing page needs a developer	The store’s logic lives in custom code	Replatform, if it’s everywhere
Extensions break after every update	The stack has grown past what anyone can test	Clean up first, then decide
Hosting, patches and upgrades eat the budget	You’re paying to stand still	Run the numbers below
The site is slow	Images, scripts and theme code	Fix in place
One integration keeps failing	A mapping or connector problem	Fix in place
The design looks dated	A theme problem	Fix in place
Organic traffic is falling	Technical SEO, content or old redirects	Fix in place first

The signals at the top of the table are about control: whether your team can change the store without a developer, and whether your current ecommerce platform will still be supported in two years. The ones at the bottom are about one part of the store, and a problem that specific usually has a specific fix.

End of support deserves a separate mention, because it changes the question from “should we move” to “when, and where to”. When Adobe ended support for Magento 1 in June 2020, stores still on that legacy platform had two options: move to Magento 2, which in practice meant rebuilding the store, or move somewhere else. Staying put stopped being a real option for an ecommerce site that handles payments and customer data. If your platform version has a published end-of-life date, put that date at the top of the business case.

What staying on your current platform actually costs

The cost of staying is easy to underestimate because it’s already in the budget and nobody thinks of it as a decision. When we put together a business case, we add up five things.

Platform and hosting. License fees where there are any, hosting, a CDN, paid extensions and their renewals. On a self-hosted platform this also includes the servers and whoever looks after them.

Keeping it running. Security patches, version upgrades, extension conflicts after an update and the testing that goes with all of it. This is developer time that produces nothing a customer will notice, and it tends to grow as a legacy system ages.

Workarounds. The hours your team spends doing by hand what the platform can’t do: re-keying orders, correcting prices after an import, building a promotion as a series of manual steps. These hours rarely show up in a platform budget, which is exactly why they’re worth counting.

Forced spend that’s coming. A major version upgrade, a payment processor change, a new compliance requirement. If you know it’s coming, it belongs in the cost of staying, in the year it lands.

What you can’t do. A wholesale channel, subscriptions, a second region, a faster checkout. This is the hardest part to put a number on, so we keep it out of the arithmetic and list it separately. If a business case only works because of guessed future revenue, it isn’t a strong case.

We ran a Magento store for a premium California olive oil and wine brand for six years before it moved. Most of the cost of staying sat in the second category: security patches, extension installs and the conflicts between them, wine-shipping compliance integrations, plus caching and server upkeep. None of that work was wasted. Very little of it moved the business forward, though. That’s the cost a platform comparison never shows.

What moving to a new ecommerce platform costs

Replatforming is a lot like moving house. The move itself is a known cost you can get quotes for. The rest is the week you lose to packing, the things that don’t survive the trip, and the months before the new place feels like home.

The known part is the replatforming project: discovery, a theme, data migration for products and customers with their orders, a redirect for every old URL, replacing extensions with apps or built-in features, reconnecting integrations, then testing and the cutover. Our own replatforming process onto Shopify starts at $15,000 for a smaller store and usually takes 8 to 14 weeks. Larger stores with integrations, wholesale pricing or custom checkout rules take longer and cost more. Our Shopify migration service page explains what’s included, and our replatform check gives a ballpark by store size. Shopify’s plan fees and app subscriptions are separate from the project, and you should get real numbers for both.

Then there are the costs that don’t show up in a proposal:

• Your team’s time. Someone on your side reviews test data, places test orders, rewrites how-to notes and learns the new system. Put it in the migration plan instead of hoping it fits around normal work.
• Some search movement. Rankings often wobble for a few weeks after a move, even with a complete redirect map. A move without one can lose far more. We cover where traffic and data go missing in what gets lost in a Shopify migration.
• The things that don’t move. Customer passwords can’t be carried from one platform to another, so customers set a new one the first time they sign in. Saved cards move between payment processors, not in a spreadsheet, so that step is planned with the processors. Some custom features are better retired than rebuilt.

The other half of the cost of moving is what the store costs to run after launch: platform fees and apps, plus the developer time it takes to keep it healthy. If that running cost is meaningfully lower than what you pay today, or it buys things you can’t do today, the one-time cost has something to pay back against. If it isn’t, the project has to be justified some other way.

Why running costs drop on a SaaS platform

Much of the running-cost difference comes from who does the upkeep. On a self-hosted platform such as Magento Open Source or WooCommerce, you are responsible for the servers, the security patches and the version upgrades, so you pay for them in hosting bills and developer hours. On a SaaS ecommerce platform like Shopify, the provider runs the servers and ships the updates, and you pay a monthly plan fee instead.

That moves a good part of the cost from unpredictable developer time into a predictable subscription. It doesn’t remove developers from the picture. Custom theme work and integrations still need someone, as does the occasional conflict between two apps, and each app adds its own monthly fee, so the app list deserves the same scrutiny the extension list gets today.

For the olive oil and wine brand, the change showed up in what the developer time went to. After the move, security patches and server upkeep stopped being part of our work for them. The time went into new things instead: a wholesale portal, the registers in the ranch shops and three small apps for gaps in the platform.

A quick way to compare staying and moving

The estimator below puts both sides next to each other, month by month, for up to five years. It works from your own figures, so start by replacing the examples. It counts costs only, not hoped-for revenue, which keeps it honest.

How we read the result: if moving pays back within about two years, it deserves a proper discovery. Between two and four years, the move needs a second reason, such as an end-of-support date or a sales channel you can’t run today. Past that, fix what’s broken where you are and revisit the numbers when something changes.

An ecommerce replatforming checklist for the business case

Before anyone compares platforms, gather the numbers the case depends on. Most of them are already sitting in invoices and time logs. This is the checklist we work through with a client before we give an opinion either way:

• Your platform version and its support dates. Look up the published end-of-life date for the exact version you run, not just the platform.
• A year of platform invoices. Hosting and licenses, extension renewals, and any agency or freelancer retainers.
• Developer hours, split two ways. Upkeep (patches, upgrades, fixing what broke) versus new work. The ratio tells you more than the total.
• Workaround hours by task. Ask the people doing them. Order re-keying, price fixes and manual promotions add up quickly.
• Forced spend on the horizon. Anything you already know you’ll have to pay for in the next three years if you stay.
• The systems connected to your current system. ERP or inventory, fulfillment, tax, email, subscriptions, reviews. Each one is a connection to rebuild or keep.
• Your search baseline. Organic share of revenue and your top landing pages, so search risk has a number next to it.
• What you can’t do today. Listed separately, with no revenue figure attached.

When to fix in place instead of replatforming

Some teams that consider replatforming don’t need to yet. The problem they describe is real, but it’s narrower than the platform, and a move would carry it to the new store along with everything else.

Fix in place when:

• Speed is the complaint. Slow stores are usually slow because of heavy images, old scripts or theme code, and those can be fixed on the platform you have. Our instant site audit is a quick first look, and site speed work usually takes one to three weeks, not months.
• A single integration keeps failing. Trace the records that don’t match before blaming the platform. A broken connector is a repair job.
• The design is tired. A new theme or a redesign on the current platform costs less than a move, as long as the platform has a future.
• Organic traffic is slipping. A move adds risk to a search problem. Fix the technical SEO first, so you don’t carry the issue, and the uncertainty about its cause, into a new platform.
• The existing platform has a supported future and your team can make everyday changes without filing a ticket.

We did exactly this for the olive oil and wine brand. When we first audited their Magento store in 2014, it had real issues: redirect debt, crawl errors and SEO penalty risk. We fixed those in place, and two years later rebuilt the storefront to a new design on the same platform. A move would have been premature then, because Magento was supported and the problems were specific. Four years after the redesign, the situation was different.

When ecommerce replatforming is worth it

A move earns its cost when one of these is true, and the case is much stronger when two of them are:

1. The platform is losing support, or the next version is a rebuild anyway. You’ll pay for a project either way, so the only question is which platform the ecommerce replatforming project lands on.
2. The running cost is clearly lower after the move, enough to pay back the project within two or three years on your own numbers.
3. The business needs things the platform does badly: wholesale accounts beside retail, subscriptions, shops with their own registers, more regions. If each of those means custom code where you are, that code is a cost you’ll keep paying.
4. Your team can’t change the store without a developer, and it’s slowing the work that makes money, like promotions and launches.

For the olive oil and wine brand, the first reason decided it. Magento 1 was reaching end of life in 2020 and the path to Magento 2 was effectively a rebuild, so they moved to Shopify Plus instead. We built the new store while the old one kept selling. Products and customers came across with their order history, saved card profiles moved to a new payment processor, the blog and product reviews came along, and email was rewired to the new store’s discount codes. It launched in under eight months. Since then the store has added things that would each have been custom work on the old platform: a wholesale portal, registers in the ranch shops, plus subscriptions and a membership club, all tied to the inventory system. The full story is in the case study, and the platform-specific steps are in our guide to Magento to Shopify migration.

From Tom: I didn’t see that move coming. Our main client wanted to go to Shopify Plus when Magento 1 ran out, so we went with them, and the rest of our Magento work dried up around the same time. So we’ve been through a platform ending from the inside, including the part where the decision wasn’t ours to make.

The second and third reasons are the ones to be careful with. They’re real, but they’re also where optimistic spreadsheets live. Use your own run-rate numbers, leave the revenue upside out of the payback, and if the case still holds, it’s a good case.

Questions ecommerce teams ask

How do we know it’s time to replatform our ecommerce store?

When the platform itself is the constraint: support is ending, the next upgrade is a rebuild, or most everyday changes need a developer. If the problem is speed, design, one integration or falling traffic, fix it where you are first. Our replatform check tells you what your store runs on and what a move to Shopify would involve for a store your size.

How much does ecommerce replatforming cost?

For our work, an ecommerce migration to Shopify starts at $15,000 for a smaller store and goes up with catalog size, integrations, wholesale or subscription logic and custom checkout rules. Shopify’s plan fees and apps are separate, and so is your team’s time. Ecommerce migration services vary a lot in what they include, so compare the scope, not just the price. The real comparison is that one-time cost against the difference in running costs, which the estimator above helps with.

Will we lose our search rankings if we replatform?

Some movement after any ecommerce website migration is normal. We cut the risk with a redirect for every old URL, page titles and descriptions carried over, structured data rebuilt and Search Console watched for weeks after launch. Nobody can promise rankings, but we can promise a redirect map with no missing pages.

Can we replatform without taking the store down?

Yes. Migrating your ecommerce store doesn’t require downtime. The new ecommerce site is built and tested on staging while the old one keeps selling, and the domain switch itself takes minutes, scheduled for your slowest hours. That’s how the olive oil and wine brand moved off Magento.

Which platforms do you migrate stores from?

Magento, WooCommerce, BigCommerce, Lightspeed, enterprise ecommerce platforms such as Salesforce Commerce Cloud, and custom ecommerce builds, always onto Shopify or Shopify Plus. We build on one ecommerce platform, on purpose. The migration process is the same whatever you leave; only the export changes. See our guides to WooCommerce to Shopify migration and Magento to Shopify migration.

Start with what your store runs on

You don’t need a finished business case to talk to us. Run the replatform check to see what your store runs on and a ballpark for a move, then put your own figures in the estimator above. If the numbers point to a move, or you can’t tell, talk to #10. We’ll tell you plainly whether we’d move it or fix it where it is.