Salesforce Connect external objects versus replicating ERP data
Key Takeaway
Choose Salesforce Connect external objects over copying ERP data when the data is large, users need only small amounts at a time, and they need the latest data in real time. External object records are read only by default, so users can't edit them unless the external data source enables writable external objects.
Agentforce Manufacturing customers often keep orders, pricing, and inventory in an ERP system. A consultant must decide whether to copy (replicate) that data into Salesforce or reach it where it lives. Salesforce Connect reaches it where it lives, so users can view, search, and change ERP data in real time without a copy stored in the org. A copy sits in Salesforce objects, but it can include data you don't need and can quickly go stale.
Copying ERP data versus Salesforce Connect
The traditional way to give users ERP data is to copy it into the org. Salesforce Connect works the other way: it maps external objects to data tables in the external system and leaves the data there.
| Copying the data | Salesforce Connect | |
|---|---|---|
| Where the data lives | In Salesforce objects, as a copy | In the external system |
| How users get it | Import or copy, for example with extract, transform, and load (ETL) tools | On demand, through web service callouts |
| How current it is | Can quickly become stale | Never stale, accessed in real time |
| How much is brought in | Can include data you don't need | Only what you need |