Headless CMS migration scales content operations for Visier

The project

Visier, a globally recognized leader in people analytics software, was scaling fast: new products, new markets, and a marketing team that needed to publish faster to keep up. Its monolithic content management system had other ideas. Publishing a single landing page took up to five business days and coordination across six separate teams, and even minor content updates required senior engineering resources.

The challenges

• Publication bottlenecks. Product managers, writers, designers, developers, QA, and digital experience specialists all touched every page, and each handoff introduced delay.
• A rigid architecture. The CMS tightly coupled content to presentation, locking content types to fixed page templates with no reuse across channels, while the database-driven system dragged page load speeds down along with SEO.
• Scale the system couldn’t meet. With 100 page templates, 1,500 unique web pages, and more than 25,000 digital assets, the monolith couldn’t support the volume and velocity the business required.
• A live migration. The move had to complete within 12 months without disrupting ongoing operations or the product launches happening in parallel.

The solution

Winmill migrated Visier to Contentful, a headless CMS that decouples content from presentation. The composable architecture lets teams build modular content components and deploy them across channels through APIs, giving marketing the self-service publishing the business needed. The migration ran on a bimodal strategy: one track supported existing operations while the other built out the new Contentful infrastructure, so the two proceeded in parallel without disruption.

The results

• Days to minutes. Time to production dropped from up to five business days to about five minutes.
• Everything moved, nothing broke. All 100 templates, 1,500 pages, and 25,000 plus assets migrated within the 12-month timeline with zero production disruptions.
• Content teams run their own show. Publishing no longer waits on senior engineers, and content components are reused across channels instead of rebuilt for each one.

“It was the most uneventful migration we’ve ever had. That’s music to developers’ ears.”

Visier engineering