Content Migration

Transitioning to a new CMS & Launching On a Net-New Domain

For years our content team had been struggling with WordPress. It was the usual story: too many plugins, an outdated interface, not enough control over permissions, templates breaking, you name it. They wanted to produce and publish at speed, and we wanted to produce new custom features that would drive HVI product actions. No one was happy. 

We audited the current state of affairs, shortlisted open source CMS tools in the market, reconciled them with our technical requirements, did a self-serve demo to recreate the editorial workflow 1:1, and pulled together our technical requirements for templates, features, CTAs, and our design system. Wagtail CMS was our final answer. 

With an upcoming soft launch of the Credenza brand in April 2026, we had a tight timeline and limited engineering resources. Once again, our full stack engineer came through with an MVP setup that would allow us to begin transitioning content to Wagtail, using SvelteKit as our headless front end code framework. The backend work was grueling and involved numerous migration scripts, database level and wildcard redirects, and meticulous attention to editorial QA and detail in order to account for every last piece of content (not to mention a programatic redesign of all IntelyCare-branded embedded images). 

But we launched! Delivered in-scope & on time! 

This was a huge cross functional success from both a front end/editorial perspective but also on the back end. Our content drives a significant part of our organic inbound traffic, and helps with Google's understanding of our brand authority. Without this work we would not be in an incredible position of growth with Credenza.