# Integration requirements that drive CRM adoption

*Integration Architect Study Guide · Evaluate Business Needs · Last updated October 16, 2026 · https://www.certifyforce.com/study-guide/integration-architect/evaluate-business-needs/integration-requirements-that-drive-crm-adoption*

Which integration requirements make or break CRM adoption: surfacing external data in Salesforce without needless replication, a system of record per field, acceptable latency per data set, visible exception handling, a separate historical load, one API Only integration user per integration, and reuse of an existing ESB.

- Certification: Salesforce Integration Architect
- Exam section: Evaluate Business Needs
- Study guide: https://www.certifyforce.com/study-guide/integration-architect

**Official exam objective:**

> Given a use case, identify key factors for CRM success that should be included as integration requirements.

## What the exam expects

- Turn "reps work entirely in Salesforce" into which external data users must see, and whether it must be stored in Salesforce.
- Name the system of record per field and the acceptable latency per data set.
- Require that integration failures reach the user, with retry and notification defined.
- Plan the one-time historical load separately from the ongoing sync, and set integration standards (one API Only integration user per integration, External Client Apps, reuse of an existing ESB).
- Key terms: **system of record** (the system whose value wins for a field); **data virtualization** (showing external data in Salesforce without copying it); **integration user** (a dedicated API-only Salesforce user per integration); **External Client App** (the app registration for new integrations); **ESB** (enterprise service bus, centrally governed middleware).

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Avoid unnecessary replication | Use data virtualization with Salesforce Connect unless data must reside in Salesforce | [Data Integration with Salesforce](https://architect.salesforce.com/docs/architect/decision-guides/guide/data-integration.html) |
| Salesforce Connect mechanism | External objects access data in real time via web service callouts, no copy | [Salesforce Connect](https://help.salesforce.com/s/articleView?id=sf.salesforce_connect.htm&language=en_US&type=5) |
| Direction question | "What system should be the source of truth?" is a data flow question | [Data Integration with Salesforce](https://architect.salesforce.com/docs/architect/decision-guides/guide/data-integration.html) |
| Exception handling question | Retry, notify or fail; does the user need to see the result | [Data Integration with Salesforce](https://architect.salesforce.com/docs/architect/decision-guides/guide/data-integration.html) |
| Initial load | Plan bulk loads such as the initial load for a new instance in advance | [Data Integration with Salesforce](https://architect.salesforce.com/docs/architect/decision-guides/guide/data-integration.html) |
| Data Import Wizard and Data Loader | Not a recommended base for a data integration strategy | [Data Integration with Salesforce](https://architect.salesforce.com/docs/architect/decision-guides/guide/data-integration.html) |
| Integration user standard | One user per integration; Integration license with Minimum Access - API Only Integrations profile | [Give Integration Users API Only Access](https://help.salesforce.com/s/articleView?id=platform.integration_user.htm&type=5) |
| App registration | Dedicated External Client App per new integration; new connected apps disabled by default from Spring '26 | [Trust](https://architect.salesforce.com/docs/architect/well-architected/guide/trust.html) |
| Existing ESB | Reuse it for governance and centralized management before adding tools | [Data Integration with Salesforce](https://architect.salesforce.com/docs/architect/decision-guides/guide/data-integration.html) |

## Check yourself

- When should external data be replicated into Salesforce instead of virtualized?
- Why does naming a system of record per field restore trust in shared data?
- Why give each integration its own API Only user?
- Which two requirements cover "complete history on day one, then daily changes"?

## Sources

- [Data Integration with Salesforce](https://architect.salesforce.com/docs/architect/decision-guides/guide/data-integration.html)
- [Trust | Well-Architected](https://architect.salesforce.com/docs/architect/well-architected/guide/trust.html)
- [Give Integration Users API Only Access](https://help.salesforce.com/s/articleView?id=platform.integration_user.htm&type=5)
- [Access External Data With Salesforce Connect](https://help.salesforce.com/s/articleView?id=sf.salesforce_connect.htm&language=en_US&type=5)
- [External Client Apps](https://help.salesforce.com/s/articleView?id=xcloud.external_client_apps.htm&type=5)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 7 linked practice questions, and unlimited timed mock exams are included with the Integration Architect pack (USD $19): https://www.certifyforce.com/practice-exams