Skip to main content
Talk to an expert
ServiceReplatform · Current delivery model

Most enterprise replatforms fail in the week before go-live.
The last four we ran didn't.

A replatform is code, data, integrations and merchandising moving in step. We staff the work from day one, rehearse go-live against production until it's routine, and deliver on the date we agreed at kickoff.
Contents · 7 sections
  1. 01Go-live is rehearsed, not guessed.
  2. 02Most of the effort is data, not code.
  3. 03Integrations move on their own timelines.
  4. 04How long it actually takes.
  5. 05Selected replatform case studies.
  6. 06Platform decisions, made properly.
  7. 07Common questions.
01 · Go-live

Go-live is rehearsed, not guessed.

We don't pause trading. The week before go-live should be quiet because the work is already done, not because the site has been taken offline.
Go-live is rehearsed four times against real production data. Traffic shifts in 5-10% steps over 48-72 hours behind a feature flag, and rollback is tested at every step. If the rollback fails its rehearsal, we don't ship.
The last four replatforms we ran went live with zero customer-visible downtime. Huws Gray, the most recent, moved on a Tuesday afternoon across 45,000 SKUs and eleven years of trade-account data. Proof is at §05.
4×
Go-live rehearsals
Minimum, per project
Flagged
Launch traffic
Shifted in controlled steps
0h
Downtime
Last go-live, Huws Gray
5-10%
Traffic-shift step
Behind a feature flag
02 · Data

Most of the effort is data, not code.

Customers, orders, products and content all carry years of edge cases the new platform has to honour from the first hour of trading.
The data audit runs in week one: every entity, every owner, every contradiction between systems. Migration runs in parallel against production for weeks before go-live, and validation is row-level. We don't sign off a migration on aggregate counts.
Projects that deliver on time staff the data problem from month one. The ones that slip leave it until month seven.
03 · Integrations

Integrations move on their own timelines.

A typical replatform touches between eight and twenty-four systems, ERP, OMS, WMS, PIM, payments, tax, search, marketing. Each has its own owner and its own appetite for change. Treating them as one go-live event is how projects overrun.
We map every integration in week one, agree the order of move, and stage them across the eight to twelve weeks around go-live. The new platform sits in production for weeks before the last system migrates across. The pattern is deliberately dull.
04 · Timeline

How long it actually takes.

Five to nine months from kickoff to go-live, scoped by the engineer who will run it rather than by sales. The shape of the work is consistent across projects; only the duration varies. Your ecommerce and trading teams sit alongside ours from week one.
4-6 wks
Discovery & audit
8-12 wks
Design & data model
10-14 wks
Build & integrate
6-8 wks
Go-live rehearsal
12 wks
Go-live + 90 days
Kickoff────────── typical 5-9 months ──────────Go-live + 90 days
We won't take a 12-week replatform brief, and we'll say so early if the date you've been given isn't real. The first 90 days after go-live matter as much as the build. Performance, conversion and trading rhythm all need watching while the new platform settles.
05 · Proof
06 · Platform

Platform decisions, made on the merits.

We choose the platform based on your requirements, not ours. We're certified across the major enterprise stacks and have no incentive to push one over another.
Not every platform fits every business, and we'll say so when it doesn't. Brief us without choosing a platform first.
Replatformed in production
Adaptive Commerce° (by WithPraxis.ai) · Adobe Commerce (Magento) · Shopify Plus · Salesforce ·
commercetools · BigCommerce · Centra · Hyvä Commerce · Akeneo PIM · Salsify · Informatica ·
Adobe Experience Cloud · Contentful · Algolia · Constructor.io · Mirakl Marketplace
Adobe credential
Adobe Solutions Partner Gold, Specialised in Commerce & AI. Multiple certified architects on staff.
07 · Questions we get asked

Common questions.

When should we consider replatforming?

Usually when the current stack is blocking the operational change you want to make: ERP integration is brittle, the catalogue cannot model how you sell, releases take weeks, or support cost is rising faster than revenue. Replatforming is a commercial decision before it is a technical one.

How long does an Adobe Commerce or Magento replatform take?

Most B2B and operational replatforms iWeb runs land between four and nine months end to end. The variable is integration scope (ERP, PIM, OMS, accounts, pricing), not the front end. iWeb scopes those flows before committing to a date.

Can you replatform without pausing trading?

Yes. iWeb runs replatforms with the existing site live and trading throughout, then switches traffic at a planned launch window. Order, account and stock data is reconciled in parallel for several weeks before launch so the switch itself carries less risk.

How do you de-risk the data migration?

Customer, order, catalogue and pricing data is migrated into a staging environment early, reconciled against the live system on a recurring schedule, and signed off by the client team before launch. Edge cases (legacy accounts, custom price lists, partial orders) are named and handled, not skipped.

What does iWeb decide first when scoping a replatform?

The integration boundary with the ERP and PIM. That decision sets the realistic budget, timeline and platform shortlist. Hero copy and theme choices come much later.

Who usually commissions a replatform inside the business?

A head of ecommerce or digital director sponsors the work, with IT, operations and finance signing off the integration boundary and the support model. The decision is rarely owned by marketing alone, because the ERP, PIM and order flow all sit in scope.

What most commonly causes a replatform to overrun?

Integration scope discovered late. Pricing edge cases, account-only catalogues, partial orders and reconciliation between ERP, PIM and storefront are where time is lost. iWeb scopes those flows before a date is committed.

Which platforms does iWeb usually replatform to?

Adobe Commerce and Magento Open Source are where iWeb has the deepest direct project evidence. The replatform pattern itself is platform-agnostic and can target other commerce platforms where the architecture, connectors and operational fit support it.

What happens after a replatform launches?

A hypercare period covers the first weeks of trading, with senior engineers on the rota and the integration runbook live. Support then settles into the normal cadence. The handover is planned during the build, not after launch.

Do you have replatform case studies we can read?

Yes. The work archive lists the replatforms iWeb has shipped that are public. Where a project cannot be named, iWeb can walk through the operational shape under NDA. The team will not claim a project it did not deliver.

Next step

Replatform on the date agreed at kickoff. Without pausing trading.

Send the brief. You'll get a written response from a senior expert, scope, risks and a timeline we'd stand behind, not a pitch deck.
Talk to an expertor read how we run go-live →