The situation
The client is a Fortune 500 insurer whose customers and partners rely on more than 30 websites and over 120,000 digital assets to get quotes, find agents, follow claims and manage their policies. Any disruption to those sites carries a direct cost in revenue and reputation.
The content platform behind those sites was monolithic and hosted on premises. It cost more each year to license and maintain, and the web team spent time patching it that it would rather have spent on customers. After evaluating several platforms, the insurer chose Magnolia, deployed as Magnolia DX Cloud on AWS, and selected TBSCG to carry out the migration.
What we did
We began with discovery that mapped user needs, content types and editorial workflows, then worked with the insurer's technical teams on the target architecture and a migration plan built around waves. Each wave grouped a set of sites into one release and moved it through two parallel workstreams: one building templates, components, integrations and automated content migration, and one covering information architecture, content, author training and acceptance testing.
The work covered 17 traditional websites and 17 headless content repositories, an API framework connecting Magnolia to the insurer's policy administration and CRM systems, and audience-based personalisation.
The numbers
- 34 sites moved onto Magnolia, 17 traditional and 17 headless.
- 9 waves, each faster than the one before.
- 12 months from the first wave to the full platform.
- 3 months to the first sites going live.
- Zero downtime for customers and staff throughout.
What changed for the client
The insurer now runs its sites on Magnolia DX Cloud on AWS rather than on an on-premises platform it had to patch, so the web team spends its time on customers instead of infrastructure. One source of content now feeds many sites in different formats, and the integrations with policy administration and CRM let the team build journeys that carry a customer from a product page to their own policy information.
The most durable change is ownership. The insurer's team learned the platform by delivering on it, co-led the early waves and took over the cadence at wave five, so the platform is theirs to run and extend. Magnolia has published its own case study of the work.
We would be glad to talk through how a migration like this would run on your platform.
Our senior consultants can take you through the wave approach, what it would mean for your sites and integrations, and how your team would take ownership along the way.