Third-party and middleware solutions for external data
Key Takeaway
Ask first whether the data needs to live in Salesforce. If it doesn't, consider Salesforce Connect. If it must be stored in Salesforce, use a tool that copies the data in, such as MuleSoft Anypoint or the native Salesforce APIs.
Third-party and middleware tools connect Salesforce to outside systems. They move or sync data between those systems, and some of them back up or archive Salesforce data. As an admin, your job is to match each need to the right tool, and to know when the data should not be copied at all.
First ask whether the data needs to live in Salesforce
Before you choose a tool, ask whether the data needs to live in Salesforce at all. Salesforce recommends avoiding unnecessary data replication, because more data means larger data volumes. Larger data volumes can hurt performance and add technical debt.
The rule works in both directions: for data coming into Salesforce and for data going out of it.
If the data does not absolutely need to reside in Salesforce...
Consider data virtualization with Salesforce Connect instead of copying the data in.
If a scenario requires data replication in Salesforce...
Use a tool that copies data in, such as MuleSoft Anypoint or the native Salesforce APIs. Salesforce Connect and external objects are not recommended for this need. For example, an ERP contact update that must be stored in Salesforce requires data replication.
If data already lives in Salesforce and an external system needs it...
Have the external system read the data through the native Salesforce APIs instead of copying it out, unless copying is absolutely necessary.