Platform migrations

Moving to a new platform without losing content, search rankings or the forms people rely on. We have moved Ohio JFS sites from HCL Digital Experience to Contentful, a research website from SharePoint to Liferay, and intranets across regions.

4: Ohio JFS websites moved from HCL Digital Experience to Contentful
100,000+: pieces of content we migrated onto the State’s shared website platform
764: URLs of Sigma’s European intranet mapped before migration

Schematic — client UI under NDA

Content inventory
URL and redirect map
New platform

Trusted by

A migration is a content project, a URL project and a people project before it is a technical one. What moves, what retires, where every old address goes, and who will run the new platform on day one — those decisions decide whether the move is invisible to the public.

For the Ohio Department of Job & Family Services we moved four sites from HCL Digital Experience to the State’s Contentful-based platform in 2025–2026, keeping their forms, search and chatbots, and trained the department on Contentful and Piwik PRO before go-live. For Honda Research Institute we moved the US website from SharePoint to Liferay CE (2018) and the research application to Honda’s infrastructure in Japan (2018–2019). For the Chicago Metropolitan Agency for Planning we upgraded two websites and a contact-management application to Liferay DXP 7.2.

Cloud moves follow the same rule: decide what to move and when, then move in phases with the legacy systems still running. And we practice it at home: base22.com moved from WordPress to Payload with every legacy URL mapped.

01What we deliver

Everything arrives, nothing breaks.

Content inventory and strategy
What you have, what people use, and what should move, be rewritten or retire.
URL map and redirects
Every old address mapped to its new home, so links, bookmarks and search rankings survive the move.
Integration and infrastructure planning
Cloud, security and integration roadmaps that work with the systems you already have.
Phased cutover
Migration in phases, with legacy applications running until their replacement is proven.
Testing and acceptance
System and user acceptance testing, each closed with an exit report, before go-live.
Training for your teams
Authors and administrators trained on the new platform before it goes live.

02How an engagement runs

From inventory to a quiet go-live.

Inventory
Content, URLs, integrations and dependencies, with what moves and what retires agreed.
Map
A target architecture, a redirect map and a migration plan in phases.
Move
Build on the new platform and migrate content, keeping forms, search and integrations working.
Verify
System and user acceptance testing, redirect checks and accessibility checks before go-live.
Hand over
Training, go-live, hypercare, then support on the new platform.