The Legacy Application Modernisation Playbook
A practical strategy, architecture and field guide for moving legacy Windows line-of-business applications towards AWS without forcing an immediate rewrite or exposing a full remote desktop.
This book helps enterprise architects, security teams, AWS and partner sellers, and software vendors decide whether governed browser delivery can unblock a legacy application migration. It combines decision guidance with a reference architecture, governance model and repeatable field evaluation.
Access today. Transform tomorrow. Browser delivery is a transition and control strategy. It can create room for a measured refactor; it is not a claim that every application should remain unchanged forever.
Choose a reading path
Strategy and decisioning
Understand the trilemma, qualify candidate applications and compare delivery options.
Architecture and governance
Review the AWS topology, control points, workload fit and deployment reference.
Ecosystem and co-selling
Apply vertical patterns, MAP alignment, hybrid guidance and competitive positioning.
Field execution
Run a focused proof of concept, discovery process and evidence-based evaluation.
How to use this book
- Architects should begin with Parts 3, 5, 9 and 15.
- Security teams should begin with Parts 6, 7 and 15.
- AWS and partner teams should begin with Parts 1, 8, 10 and 13.
- ISVs should begin with Parts 2, 3, 9 and 11.
Scope and evidence
The book generalises lessons from a legacy warehouse-management application and a June 2026 AWS Malaysia launch session. Product names and customer-identifying material from the source case study are intentionally omitted. Time, capacity and performance figures are evaluation inputs, not guarantees; validate them against the current product manual and your own workload.
The four-module method
- Decide: identify the actual migration blocker and select the right delivery pattern.
- Design: place identity, application execution, data and governance controls in a defensible architecture.
- Align: connect the technical outcome to programme milestones and stakeholder needs.
- Prove: evaluate one representative application against explicit success criteria.