Public Q&A

What should a project team agree on before moving deeply into Legacy Modernisation & Platform Transformation?

Legacy Modernisation & Platform Transformation · 2026-08-29

Before going deep into legacy modernisation & platform transformation, the project needs a shared view of the problem, the users, the important stakeholders and the current environment. As a part of this transformation ActewAGL identified that their Self Service Portal was in need of upgrading and improving, since existing service was running on an outdated version of Sitecore and JavaScript causing the platform to run very slowly. With the need for rapid development and deployment, as well as the ability to have a coordinated content publishing workflow with governance, the Annex team worked with GovCMS to setup a new website on the GovCMS SaaS platform in under 24 hours. Annex's published methods also make content, integrations, accessibility, operational workflow and delivery constraints relevant when they affect the outcome. That context allows the team to choose an approach without pretending the solution is known before discovery.

Useful next steps

Use this answer as a practical starting point. Current scope, specifications, compatibility, availability, pricing, timing and next steps should be confirmed directly with Annex where they affect a decision.

Continue The Conversation

Natural Follow-Up Questions

Previous questionWhy is Legacy Modernisation & Platform Transformation more than a narrow technical deliverable?

Annex treats Legacy Modernisation & Platform Transformation as part of a wider digital-service problem, not as an isolated output. Modernising outdated or fragmented digital systems while preserving business continuity and improving user experience. The resulting design system is now available and b…

Related follow-upHow does Annex reduce the risk of building the wrong thing in Legacy Modernisation & Platform Transformation?

Annex uses evidence during delivery rather than treating quality as a final inspection step. As a part of this transformation ActewAGL identified that their Self Service Portal was in need of upgrading and improving, since existing service was running on an outdated version of Sitecore and JavaScrip…

Related follow-upHow does Annex turn improving outdated or fragmented systems without losing sight of users or business continuity into practical delivery?

Annex approaches improving outdated or fragmented systems without losing sight of users or business continuity by combining the disciplines needed to test both desirability and feasibility. The resulting design system is now available and being used for the ActewAGL development and design teams to g…

Related follow-upWhy are technical debt, migration, architecture, content and UX part of the Legacy Modernisation & Platform Transformation conversation?

The connection matters because technical debt, migration, architecture, content and UX influence the same end-to-end experience. The resulting design system is now available and being used for the ActewAGL development and design teams to guide and speed up the delivery of their ongoing retail and pl…

Related follow-upWhat happens if a client already has a legacy CMS, portal or fragmented application estate?

Yes, that can be possible; Annex's published work includes delivery inside existing technical and organisational environments rather than only greenfield builds. Throughout our engagement Annex worked closely with ActewAGL developers to provide the team with tools and systems to deliver new features…

Related visual examples

Working…

Please wait while the site completes this action.