There's a particular phone call I keep having with Australian e-commerce founders. They're on Shopify, the store does between $400k and $4M annually, and someone — usually a consultant, sometimes a board member — has suggested they should be looking at "replatforming." The phone call is them trying to figure out if it's a real strategic move or a vanity exercise.

My honest answer for most of them is: don't do it yet. The Shopify ceiling that triggers a genuine replatform conversation tends to live above $5M revenue, and even then the decision is more nuanced than the consultants imply. If your problem is that the storefront feels slow, the theme looks dated, or the checkout could convert better — that's a custom theme project, not a replatform. The cost difference is roughly an order of magnitude.

But for the businesses where replatforming is the right move, the timeline and cost assumptions floating around are mostly imported from the US enterprise market and don't translate cleanly to Australian businesses. This is the honest version.

The case for replatforming an AU Shopify store

Real reasons to leave Shopify, in rough order of how often I see them:

The product catalogue has outgrown Shopify's data model. Shopify allows three product options (size, colour, material). If your business needs four or more — common for furniture, made-to-order, configurable products — you're either hacking around it with apps that slow the checkout or you're hitting a structural wall.
You need B2B and B2C in the same store. Shopify Plus has B2B but it's tier-locked at $2,500 USD/month and the implementation isn't always what mid-market Australian wholesalers need.
Your subscription business depends on app sprawl. Recharge, Bold, or one of the others handles subscriptions, but every interaction with the customer is mediated by the app, which means margins, customer data, and feature roadmap aren't yours.
The headless ambition is real and the SEO opportunity is significant. Moving the frontend to a custom Next.js build while keeping Shopify as the backend (the Hydrogen approach or a fully custom storefront) opens up performance and brand differentiation that the standard theme architecture can't match.

If none of those apply, the conversation should be about optimising the existing Shopify store. Custom theme, better app hygiene, Shopify Functions for checkout customisation. Most $1M to $4M Australian stores have more upside in optimisation than replatforming.

The timeline (what Shopify's own data says vs what AU agencies actually deliver)

Shopify's own replatforming guide cites a 16 to 24 week timeline for mid-size retailers. That's reasonable as an enterprise benchmark but it's worth understanding what's in those 16 to 24 weeks before you sign anything that says "eight weeks."

The Shopify-published breakdown:

Discovery and audit: 2 to 4 weeks
Design and architecture: 3 to 6 weeks
Development: 4 to 10 weeks
Testing and QA: 2 to 4 weeks
Pre-launch: 1 to 2 weeks
Go-live and monitoring: 1 to 2 weeks

For an Australian mid-market store, my real-world experience is that the discovery phase is usually shorter (1 to 2 weeks because the founder is closer to the operational detail than at a US enterprise) but the development phase is often longer (5 to 12 weeks) because the AU agency market has a smaller pool of senior Shopify-headless developers and the schedules stretch.

The honest range for a Melbourne or Sydney-based replatform of a $1M to $5M store: 14 to 22 weeks from kick-off to go-live, plus another 4 to 6 weeks of post-launch monitoring and stabilisation.

If an Australian agency is quoting eight weeks for a replatform of a real store, ask what's being cut. The usual answer is QA, accessibility audit, or the SEO migration plan — none of which are the corners you want cut on a project that's going to determine 12 to 36 months of revenue.

The cost (the Australian version)

Shopify's enterprise guide cites $150k to $300k USD for a mid-size replatform. Convert that to AUD and adjust for the Australian agency market and the realistic range for an Australian store is roughly:

| Component | Low | High | |-----------|-----|------| | Design and frontend development | $40,000 | $180,000 | | Backend / Shopify configuration | $8,000 | $40,000 | | Data migration | $5,000 | $25,000 | | Integration rebuilds (ERP, 3PL, ESP, etc.) | $10,000 | $60,000 | | SEO migration plan and execution | $5,000 | $20,000 | | Project management and QA | $10,000 | $40,000 | | Total | $78,000 | $365,000 |

Plus the ongoing Shopify Plus licence at $2,500 USD/month (roughly $3,800 AUD/month) if that's the destination, or the hosting and headless storefront cost if you're going custom-front, Shopify-back.

The cost bands hide enormous variation. A $1M store moving from a basic Shopify theme to a custom Shopify Plus build might land at $80k. A $4M store moving to a headless Next.js storefront with five integrations to rebuild might land at $250k. The proposal you're holding should be specific about what's in scope, not gestured at vaguely.

The SEO assumptions to challenge

Here's where most replatforming projects get hurt. Three assumptions get baked in early and they need pushing on.

Assumption 1: "Shopify-to-Shopify migrations don't lose SEO"

False. Even Shopify-to-Shopify migrations lose traffic in the short term. Shopify's own data, repeated in their migration documentation, says a typical migration sees normalisation at 4 to 6 weeks with a 1:1 redirect plan, and a 10 to 20 percent organic traffic dip in the first 6 to 12 weeks even when execution is good. That dip on a $2M store is $20k to $40k in lost revenue, and the dip is bigger if the migration is sloppy.

The assumption to challenge: that the redirect plan is "obviously" being done. Ask to see the spreadsheet. If the answer is "we'll generate it during development," that's a red flag.

Assumption 2: "The URL structure will improve, which will improve SEO"

The pitch goes: the existing store's URLs aren't great, so we'll make them cleaner, and Google will reward us. Maybe. But every URL change is a 301 redirect to maintain, and every 301 redirect is a small concession of link equity. Moz's longstanding research suggests a clean 301 preserves 90 to 99 percent of link equity, but the cumulative effect across a few hundred URLs is real.

Default to keeping the existing URL structure unless there's a specific reason to change it. "Aesthetically cleaner" is not a reason.

Assumption 3: "The new site will rank better because it's faster"

Performance helps. It's not magic. A site that goes from 65 to 95 on Lighthouse won't suddenly outrank competitors with stronger backlink profiles and better content. Page speed is a tiebreaker between sites that are otherwise comparable, not a replacement for the actual ranking factors.

The honest version: the speed improvement is a real long-term advantage but it won't show up in rankings within the 4 to 8 week recovery window. Don't promise the founder a ranking lift that you can't deliver on the timeline they're imagining.

The integration risks (this is where the budget actually goes)

The line that surprises Australian founders is integration rebuild costs. A typical Australian e-commerce store of size has more integrations than the founder realises:

Accounting (Xero, MYOB)
ERP or inventory (Cin7, Unleashed, DEAR)
3PL fulfilment (StarShipIT, Shippit, ShipStation)
Email service provider (Klaviyo, Mailchimp, Campaign Monitor)
Customer support (Gorgias, Zendesk)
Reviews (Junip, Yotpo)
Subscriptions (Recharge, Bold)
Loyalty (Smile.io, LoyaltyLion)
B2B portal (Sparklayer, custom)

Every integration that exists today needs a plan. Either it carries across (because the app supports the new destination), it gets rebuilt natively, or it gets replaced with something equivalent. The discovery audit should produce a list of every integration with its destination plan. If the proposal doesn't reference this, the budget is going to grow mid-build.

What "ready to migrate" actually looks like

The signals that an Australian Shopify store is genuinely ready for replatforming, not just feeling restless:

Revenue above $1.5M annually with growth trajectory
A specific feature requirement that Shopify cannot meet, documented
Internal capability or budget for ongoing development post-launch (a custom storefront needs ongoing engineering, not just an agency on retainer)
Acceptance of a 4 to 6 week SEO recovery window
A signed-off integration plan covering every connected system
Senior executive sponsorship beyond the marketing or e-commerce manager

If two or more of these are missing, the project is probably premature. Spend the budget on optimising the existing Shopify store first.

The five mid-build risks nobody mentions in the proposal

Even with a properly scoped replatform, five specific risks tend to emerge during the build that should have been costed in but rarely are.

Tax configuration for AU customers. Shopify handles GST through tax overrides, and the configuration that worked on the old store may not survive a fresh setup cleanly. For B2B stores, GST exemptions for ABN-registered customers require either a Shopify Plus B2B configuration or a third-party app. Both add cost and configuration time.

Customer account migration. Shopify lets you import customer records, but password hashes don't transfer — customers will need to reset their passwords on first login. The communications around this need to be planned. An email campaign explaining the change goes out a week before launch, on launch day, and a week after launch. Skip this and a percentage of returning customers think their account has been deleted.

Subscription continuity. If the existing store runs subscriptions via Recharge, Bold, or similar, migrating active subscriptions to the new store is a data migration project on its own. Payment tokens often need to be re-tokenised, which means customers re-confirm payment details. Drop-off during this is typically 5 to 15 percent of the subscriber base.

Inventory sync during the cutover window. Between the moment the new store goes live and the moment all integrations are confirmed working, inventory levels can drift. A 24 to 48 hour freeze on inventory-affecting operations during cutover is standard but disrupts operations. The plan needs to be agreed in advance.

The marketing dependency reset. Existing campaigns — Google Ads with destination URLs pointing at old pages, email flows referencing old product URLs, social media posts with old links — all need updating. The marketing team's workload during cutover week is usually higher than the e-commerce team's. Brief them early.

These risks are all manageable. They become problems when nobody plans for them and they surface in the launch week as crises.

The honest bottom line

For most Australian e-commerce founders, the right answer to "should we replatform?" is "not yet, and probably not the way you're imagining." The honest version of the conversation includes the timeline (14 to 22 weeks, not 8), the cost ($80k to $365k depending on scope), the SEO dip (10 to 20 percent for 6 to 12 weeks), and the integration rebuild cost (often the single biggest line item).

For the businesses where replatforming is the right call, the framing matters: this is a 12 to 18 month investment, not a quick refresh, and the ROI shows up in conversion rate, brand differentiation, and ceiling lift — not in immediate ranking gains.

Before you commit to a 14-week replatform, get a hard number on what your current Shopify storefront is doing. Drop the URL into our audit and you'll see the mobile performance, the rendered SEO, the accessibility gaps, and the dollar-impact framing of every second your store currently takes to load. Whatever the replatform proposal says it'll fix, this is the baseline it needs to beat.

Shopify Replatform AU: Real Timeline, Cost, SEO 2026