CASE 54 · REVERB · 2024
Off Magento, onto something the team can actually maintain.
A speciality e-commerce site ran on Magento 2 for seven years, accumulating 140 third-party modules and a deployment process nobody trusted. We migrated to a headless commerce architecture on AWS with Next.js on the front and commercetools handling catalog + checkout.
E-commerce
MIGRATION
2024
RESULTS
What changed, by the numbers.
PAGE LOAD (p75)
−61%
CONVERSION RATE
+18%
DEPLOY FREQUENCY
14×
INFRASTRUCTURE COST
−43%
HOW IT WENT
The Magento install was a museum of half-finished decisions: a custom theme, three layers of module overrides, a checkout flow that had been "almost rewritten" twice. Deploys took 90 minutes and broke roughly weekly. The team had stopped shipping non-emergency changes.
The new stack is conventional headless commerce: Next.js on Vercel’s edge model (CloudFront + Lambda@Edge for personalisation), commercetools for the catalog and checkout state machine, Stripe for payments, Aurora Postgres for order history. EventBridge wires the events that need to flow into the back office.
Page load dropped 61% at the 75th percentile — the front end is now static-by-default. Conversion rate went up 18% in the 90 days following launch. The team ships changes 14 times a week now instead of when-they-have-to.
RELATED · SAME DOMAIN
Other engagements in this space.
READY WHEN YOU ARE
Let's get your AWS bill (and architecture) in order.
The discovery call is free. You walk away with at least one concrete idea — even if we never work together.