Home › Work › Platform Modernisation and CMS Migration

Platform Modernisation and CMS Migration

Sitecore to AEM modernisation for a state road authority serving 4 million residents

Migrated a high-traffic government website from Sitecore to AEM, modernising 300+ pages, adding translation into 6 languages and journey analytics, and going live with zero P1 or P2 issues.

SectorGovernment
ClientState government road authority
RoleAdobe Solution Architect and Tech Lead
PeriodApr 2025 - Nov 2025
EmployerAnchora
201020122014201620182020202220242026
Outcomes at a glance

The numbers

300+pages modernised and migrated to AEM
4Mresidents in the target audience
5%increase in self-serve adoption
0P1 or P2 issues at go-live
6languages via automated translation
10key user journeys tracked in Adobe Analytics
Why it mattered

Business goals

User experience

A unified, seamless experience across websites, the customer portal, in-store self-service and mobile apps.

Self-service

More registration and licensing transactions completed online.

Commercial opportunities

New commercial opportunities through enhanced digital interactions.

Content management

Less complexity for authors and business users.

Cost to serve

Fewer bottlenecks and lower licensing costs, freeing investment for critical services.

The challenge

Where it started

  • The website ran on Sitecore; migration to AEM was assessed as the viable option
  • Content publishing was complex for authors and business users
  • Licensing and hosting costs constrained investment elsewhere
  • Limited insight into how customers moved through key journeys
Approach

How it was delivered

  1. 1

    Evaluate and decide

    Which platform is right, and why.

  2. 2

    Discover

    Build the scope.

  3. 3

    Implement

    Execute on the scope and test.

  4. 4

    Optimise

    Create and optimise the feature roadmap.

What was delivered

Scope and deliverables

  • Sitecore to AEM Sites and Assets migration
  • 300+ pages modernised on the new platform
  • AEM components to accelerate and control publishing
  • Improved content publishing workflow
  • Translation into the 6 most used languages via the Google Translation API
  • GA4 and Adobe Analytics through Adobe Launch, with a UI-based event tracking approach
Architecture view

How the pieces connect

Architecture view: AEM Sites and Assets connected to Google Translation API, Adobe Launch, Adobe Analytics, GA4, Content authors, Residents (4M)AEM Sites andAssetsGoogle Translation APIAdobe LaunchAdobe AnalyticsGA4Content authorsResidents (4M)

Simplified view of the main platform and the systems it connects to.

The result

Outcomes

  • Enhanced customer experience and reach for 4 million residents
  • Cost savings from Adobe infrastructure, reducing maintenance and hosting expenses
  • Self-serve adoption up 5%
  • Journey insights supporting the client's FY26 priorities: an evolved digital experience, and secure and trusted reporting
  • Strong feedback from the product owners, head of technology and business analyst

Facing a similar challenge?

Let's talk about strategy, architecture and delivery.

Get in touch