Architecting a Scalable Content System: A Multi-Phase Contentful Migration
Role
UX Lead / Organization Change Management Lead
Contentful Certified Professional
Content design, content strategy, training lead
Collaboration
Project manager
Full-stack developer
UX designer
Content designer
Business analyst
Client
Government agency
Timeline
November 2025-March 2026
Tools
Teams
UXPin
Atlas/Jira/Confluence
Excel
Miro
PowerPoint
Contentful platform
The migration strategy: maintaining integrity in a "lift and shift"
I led the content architecture and organizational change strategy for a major government agency’s migration to Contentful. By mapping legacy data to a structured component library, I transformed a fragmented digital presence into a governed, accessible, and “AI-ready” ecosystem—achieving 100% content parity while meeting strict WCAG 2.1 accessibility standards.
Component mapping as content logic
The Challenge: The project mandate was a "lift and shift" migration, requiring 100% content parity between the legacy environment and the new Contentful CMS. We were restricted from altering on-page copy, which meant the design challenge was purely structural.
Because the legacy site and the new State Design System used different component libraries, I had to architect a "Translation Layer" to ensure content remained functional and accessible. Here’s an overview of the approach:
| Technical Constraint | Design & Logic Solution | Outcome |
|---|---|---|
| Component Mismatch | Deconstructed monolithic legacy pages into modular content types (Hero, Body, CTA), establishing a scalable foundation for future personalization and omnichannel delivery. | Maintained content hierarchy while improving back-end Content Governance and Naming Conventions. |
| Strict Parity | Created a rigorous Mapping Documentation to track every element from source to destination, ensuring no loss of context during the migration. | Achieved zero data loss across the "digital front door" for the agency. |
| System Limitations | Worked with developers to define custom Validation Rules within Contentful to prevent future users from breaking the "lift and shift" structure. | Established a scalable, error-proof environment for agency staff. |
1. Planning and requirements: aligning people and data
To ensure a seamless transition for both users and agency staff, I led the strategic alignment between technical constraints and organizational needs.
Organizational Change Management (OCM): Conducted stakeholder interviews to architect an OCM plan, ensuring all impacted teams were aligned on the new Contentful workflow.
Content Inventory & Mapping: Partnered with engineering to audit legacy content and map it to modular Contentful components, proactively resolving technical constraints before development began.
DesOps & Component Definition: Led the requirements gathering for new global components, defining their data structure in the Contentful back end to ensure a scalable, accessible front-end experience.
2. Design and prototyping
Next, I supported our UX designer in using the State Design System to design the new components and implement them into clickable prototypes for both desktop and mobile experiences. I confirmed the prototypes matched the look and function of real Contentful components and guided communication between our designer and the agency.
3. Development and migration: from architecture to implementation
During the build phase, I ensured that every content type and component was implemented with 100% accuracy and scalability:
Content Modeling & QA: Along with the team, I architected the full website structure in Contentful, overseeing the transfer of all legacy data and conducting rigorous Quality Assurance on every page to ensure no loss of context.
System Governance: I created and maintained strict naming conventions and validation rules for each content type, preventing future "content debt" and ensuring long-term system health.
Cross-Migration Collaboration: I partnered closely with separate project teams to align on shared components, ensuring all technical dependencies were met before the site went live.
DesOps Integration: I oversaw the developer in building new components that followed agreed-upon designs and accessibility requirements, ensuring they were both user-friendly and deployment-ready.
4. Training and governance: empowering the team
I created and delivered a multipart training program to ensure the agency was self-sufficient post-launch:
Contentful 101 & Deep-Dives: Led virtual sessions covering everything from basic entry creation to complex task management, reducing the agency's reliance on external dev support.
Analytics & Performance: Conducted Piwik training to empower the team to run and export reports, enabling data-informed iteration of the new site.
5. Go-live and hypercare
Following the structured Go/No-Go process, we successfully launched the site and provided two weeks of hypercare support. We delivered a complete XML sitemap, final project summary, and established clear pathways for ongoing maintenance and enhancement.
The results
Our successful migration of the website to the Contentful platform delivered measurable improvements across operational efficiency, user experience, and accessibility:
Operational Efficiency: Reduced the agency's content deployment cycle time through the implementation of structured Contentful components and standardized naming conventions. Replaced manual “copy-paste” tasks with structured components.
Accessibility: Achieved 100% WCAG 2.1 Level AA conformance across 1,000+ migrated pages, ensuring equitable access for all citizens.
Stakeholder Readiness: Empowered agency staff members through Contentful 101 training, resulting in more independent content updates without developer intervention.
Bridging to the future: AI readiness
While this project was a "lift and shift," the decision to move from monolithic legacy pages to a modular, component-based architecture in Contentful created a critical foundation for AI-driven personalization.
Modular Content for LLMs: By deconstructing "blobs" of text into structured content types (headers, body, metadata), the system is now optimized for LLM ingestion, enabling future agentic experiences like automated content tagging or conversational search.
Systemic Consistency: The strict naming conventions and governance frameworks I established ensure that any AI-generated or AI-augmented content remains grounded in the brand’s specific voice and tone.
Future Personalization: This structured approach allows for dynamic content delivery, moving beyond static pages toward an ecosystem where discovery is something users actively shape through intent and feedback.