Legacy Framework Mapping


The legacy Well-Architected Framework was organized around three capabilities — Trusted, Easy, and Adaptable — each with its own sub-pillars. The current framework reorganizes that guidance into five pillars. This page maps each legacy sub-pillar to the single file where its guidance is now most directly addressed, so you can jump straight from an existing concept to its current home.

Each destination links to a live page. The new framework splits several sub-pillars across more than one pillar, so we link the primary (most-addressed) home and call out any secondary homes in the notes.

Trusted

Sub-Pillar Now Most Addressed In Notes
Secure Trust Organizational, session, and data security; expanded with Agentforce agent-user authentication and data exposure.
Reliable Reliability Availability and scalability; adds Scale Center. Performance optimization and some aspects of data-lifecycle move to Resource and Cost Optimization; monitoring to Operational Excellence.
Compliant Fairness Ethical standards, AI fairness, accessibility, and privacy rights. Legal adherence and data residency stay in Trust.

Easy

Sub-Pillar Now Most Addressed In Notes
Intentional Operational Excellence Strategy, prioritization, and governance. Maintainability and readability live in Resource and Cost Optimization.
Automated Operational Excellence Process design and data integrity. Query mechanics and business-value/ROI move to Resource and Cost Optimization; bulkification serves scalability in Reliability and resource efficiency in R&CO.
Engaging Fairness Equity-relevant UX — form-factor/device equivalence, forms cognitive load, deliberate in-app guidance — is in Fairness.

Adaptable

Sub-Pillar Now Most Addressed In Notes
Resilient Operational Excellence Application lifecycle management, operational incident response. Disaster recovery/continuity moves to Reliability; security-incident response to Trust.
Composable Resource and Cost Optimization Separation of concerns and architecture efficiency. Messaging/eventing and API management live in Integration Patterns; packaging in Operational Excellence.

How to read this map

  • "Now Most Addressed In" is the single file where the bulk of that sub-pillar's guidance now lives — the best first click. It's not the only place the topic appears.
  • Splits are called out in Notes when a sub-pillar was deliberately divided across pillars (for example, Legal Adherence: infrastructure/security in Trust, personal rights in Fairness).
  • Engaging (Streamlined and Helpful) contributes its equity-relevant guidance to Fairness (responsive/form-factor equivalence, forms cognitive load, and deliberate in-app guidance).