From monolith to composable: a migration story
How we moved a ten-year-old platform to a composable architecture without a big-bang relaunch.
Marcus Lindqvist
Big-bang relaunches are risky: months of work, one launch day and a long list of surprises. For a financial services client we took a different route.
Strangle, don't replace
We put a modern Nuxt front end in front of the existing platform and migrated one section at a time. Each route was either served by the new stack or proxied to the old one. Visitors never noticed the seams.
Content first
We migrated content into Sanity with scripts that ran nightly, so editors could keep working in the old system until each section switched over.
The outcome
Over six months, the old platform shrank until it could be switched off. Page speed doubled, hosting costs fell by 40%, and the team never had to freeze content.
Keep reading
TechnologyGuidesHeadless CMS without the headache
Structured content gives teams superpowers, but only if editors can actually use it. Our playbook for headless projects that editors love.
Marcus Lindqvist
TechnologyGuidesCore Web Vitals in practice: a field guide
LCP, INP and CLS explained without jargon, plus the fixes that moved the needle most on our recent projects.
Marcus Lindqvist
DesignTechnologyDesign tokens that scale across brands
How a three-tier token architecture let one client run five brands from a single component library.
Elena Vos