| Solution Option | Data Replication Automation | Out-of-the-box UI Capabilities | Benefits | Key Considerations |
|---|---|---|---|---|
| Manual spreadsheets | No | Low | Low-tech way to capture data changes during system unavailability At a minimum, this can (and should) be used as a last contingency for worst-case scenarios in which the primary Salesforce instance and other BCP solutions are unavailable at the same time. |
Need to sync data back to production Need to determine high value data |
| Salesforce Full Sandbox | Automated | Same Salesforce UI | Production-like system | Refresh limit only once every 29 days May take long time to refresh Many potential gotchas to consider (for example, outbound email limitations) |
| Secondary Production Instance | Custom | Same Salesforce UI | Full production system | Licensing cost Control of data center location |
| Heroku Connect or AppExchange solutions | Custom | Custom UI Needed | Salesforce data and metadata syncing through a standard connector Quick to get up and running |
No UI availability Database maintenance effort Additional licensing cost |
| Custom On-Premises Solution | Custom | Custom UI Needed | Flexible data replication option Highly customizable Transformation capabilities can be included |
High infrastructure costs Custom development Ongoing maintenance |
Last active
October 15, 2021 16:30
-
-
Save mbraga-sfdc/5ca2e95c173847e3b4ab3bea7845787f to your computer and use it in GitHub Desktop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
IMHO "secondary production instance" is missing a key consideration of change management/metadata sync — it's non-trivial.