🏗️Interactive Checklist
Legacy Modernisation Checklist
Evaluate and plan legacy system modernisation initiatives.
25 items0%
Critical items (marked ★) carry higher weight. Start with Assessment & Discovery and Strategy & Approach — choosing the wrong modernisation path is more expensive than the legacy system itself.
Assessment & Discovery
Understand the current state of legacy systems before selecting a modernisation approach.
0/5
A complete inventory of legacy systems exists, including technology stack, age, vendor support status, and business criticality.★ Critical
Business processes supported by each legacy system are documented with process owners identified.
Integration points and data flows between legacy systems and other applications are mapped.★ Critical
Total cost of ownership (TCO) for each legacy system is calculated, including maintenance, licensing, and operational overhead.
Technical health of each system is assessed (e.g., code quality, infrastructure currency, vendor support roadmap).
Strategy & Approach
Select the right modernisation strategy for each system.
0/5
A modernisation strategy is selected for each system (e.g., rehost, replatform, refactor, replace, retire, retain).★ Critical
Build-vs-buy analysis is completed for systems being replaced.
A target architecture is defined that supports the modernised portfolio.
Modernisation is sequenced based on business value, risk, and technical dependencies.
Quick wins are identified (e.g., retire unused systems, rehost stable workloads) to build momentum.
Migration Readiness
Ensure the technical foundations are in place for successful migration.
0/5
Data migration strategy is defined, including cleansing, transformation, validation, and rollback procedures.★ Critical
Testing strategy covers functional, integration, performance, and regression testing for modernised systems.
Co-existence and cutover strategy is defined for the transition period (e.g., parallel run, phased cutover, big bang).
API or integration layer is designed to decouple legacy systems during the transition period.
Infrastructure and environments (dev, test, staging, production) are provisioned for the target platform.
Organisational Readiness
Prepare people and processes for the change.
0/5
A change management plan addresses user training, communication, and adoption for modernised systems.
Skills assessment identifies gaps between current team capabilities and target technology requirements.
Executive sponsorship is secured with a clear business case and funded programme.★ Critical
Vendor and partner strategy is defined for systems requiring external implementation support.
Knowledge transfer plan captures institutional knowledge from legacy system experts before retirement.
Risk Management
Identify and mitigate risks that commonly derail modernisation programmes.
0/5
A risk register is maintained with mitigation plans for key modernisation risks (data loss, scope creep, business disruption).
Rollback plans are defined for each modernisation wave in case of critical failures.
Business continuity is ensured during modernisation — legacy systems remain operational until validated cutover.
Security and compliance requirements are validated in the target environment before decommissioning legacy systems.
Programme governance includes stage gates, health checks, and go/no-go decision points at each phase.