---
schema_version: "1"
id: bb1fb8a5e91a097e400f75e38a11f1bd7e52d3a4fdc0eacab7eb156e61800ee1
title: Legacy Framework Mapping
collection: architect
version: current
locale: en-us
portal_url: https://docs.salesforce.com/architect/current/en-us/well-architected/guides/tea-pillar-mapping.md
canonical_url: https://architect.salesforce.com/docs/architect/well-architected/guide/tea-pillar-mapping.html
source_site: architect.salesforce.com
content_type: documentation
content_hash: 462547206eebc1c0976e50053d9d86f3753d4eeda214c95912133bec4aada45d
products:
  - Well-Architected Framework
  - Architect Site Content Repo
---
# Legacy Framework Mapping

<br/>

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.

<div style="width: 95%; margin: 0 auto;">

## Trusted

<table style="width: 100%;">
<thead>
<tr><th style="width: 22%;">Sub-Pillar</th><th style="width: 33%;">Now Most Addressed In</th><th style="width: 45%;">Notes</th></tr>
</thead>
<tbody>
<tr><td><strong>Secure</strong></td><td><a href="https://architect.salesforce.com/docs/architect/well-architected/guide/trust">Trust</a></td><td>Organizational, session, and data security; expanded with Agentforce agent-user authentication and data exposure.</td></tr>
<tr><td><strong>Reliable</strong></td><td><a href="https://architect.salesforce.com/docs/architect/well-architected/guide/reliability">Reliability</a></td><td>Availability and scalability; adds Scale Center. Performance optimization and some aspects of data-lifecycle move to <a href="https://architect.salesforce.com/docs/architect/well-architected/guide/resource-and-cost-optimization">Resource and Cost Optimization</a>; monitoring to <a href="https://architect.salesforce.com/docs/architect/well-architected/guide/operational-excellence">Operational Excellence</a>.</td></tr>
<tr><td><strong>Compliant</strong></td><td><a href="https://architect.salesforce.com/docs/architect/well-architected/guide/fairness">Fairness</a></td><td>Ethical standards, AI fairness, accessibility, and privacy rights. Legal adherence and data residency stay in <a href="https://architect.salesforce.com/docs/architect/well-architected/guide/trust">Trust</a>.</td></tr>
</tbody>
</table>

## Easy

<table style="width: 100%;">
<thead>
<tr><th style="width: 22%;">Sub-Pillar</th><th style="width: 33%;">Now Most Addressed In</th><th style="width: 45%;">Notes</th></tr>
</thead>
<tbody>
<tr><td><strong>Intentional</strong></td><td><a href="https://architect.salesforce.com/docs/architect/well-architected/guide/operational-excellence">Operational Excellence</a></td><td>Strategy, prioritization, and governance. Maintainability and readability live in <a href="https://architect.salesforce.com/docs/architect/well-architected/guide/resource-and-cost-optimization">Resource and Cost Optimization</a>.</td></tr>
<tr><td><strong>Automated</strong></td><td><a href="https://architect.salesforce.com/docs/architect/well-architected/guide/operational-excellence">Operational Excellence</a></td><td>Process design and data integrity. Query mechanics and business-value/ROI move to <a href="https://architect.salesforce.com/docs/architect/well-architected/guide/resource-and-cost-optimization">Resource and Cost Optimization</a>; bulkification serves scalability in <a href="https://architect.salesforce.com/docs/architect/well-architected/guide/reliability">Reliability</a> and resource efficiency in R&CO.</td></tr>
<tr><td><strong>Engaging</strong></td><td><a href="https://architect.salesforce.com/docs/architect/well-architected/guide/fairness">Fairness</a></td><td>Equity-relevant UX — form-factor/device equivalence, forms cognitive load, deliberate in-app guidance — is in Fairness.</td></tr>
</tbody>
</table>

## Adaptable

<table style="width: 100%;">
<thead>
<tr><th style="width: 22%;">Sub-Pillar</th><th style="width: 33%;">Now Most Addressed In</th><th style="width: 45%;">Notes</th></tr>
</thead>
<tbody>
<tr><td><strong>Resilient</strong></td><td><a href="https://architect.salesforce.com/docs/architect/well-architected/guide/operational-excellence">Operational Excellence</a></td><td>Application lifecycle management, operational incident response. Disaster recovery/continuity moves to <a href="https://architect.salesforce.com/docs/architect/well-architected/guide/reliability">Reliability</a>; security-incident response to <a href="https://architect.salesforce.com/docs/architect/well-architected/guide/trust">Trust</a>.</td></tr>
<tr><td><strong>Composable</strong></td><td><a href="https://architect.salesforce.com/docs/architect/well-architected/guide/resource-and-cost-optimization">Resource and Cost Optimization</a></td><td>Separation of concerns and architecture efficiency. Messaging/eventing and API management live in <a href="https://architect.salesforce.com/docs/architect/well-architected/guide/integration-patterns">Integration Patterns</a>; packaging in <a href="https://architect.salesforce.com/docs/architect/well-architected/guide/operational-excellence">Operational Excellence</a>.</td></tr>
</tbody>
</table>

</div>

---

## 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).