Salesforce Backup and Restore – Know Your Options


In this blog post, I want to detail out the options you have when it comes to Salesforce data and metadata backup. Before getting into all the details and specifics around the different options, let us first address the question ‘Why should you consider backup of your Salesforce data?’

  • Protect against data loss due to inconsistent data governance and stewardship
  • Ensuring continuity of business operations
  • Adherence to established data retention and compliance policy
  • Mitigate performance issues by reducing data footprint
  • Preserve business context with the enterprise
  • Support analytics and BI
  • Hedge against data loss during the data migration activity
  • Backup needs to be a core business capability for enterprises

There will always be different requirements when it comes to backup of your Salesforce data and depending on your use case, you can explore the options best suited to your requirements and processes.

Options Description When to Use It Limitations
Data Export Service Customers can generate backup files of their data on a weekly or monthly basis depending on their edition. It can export all your organization’s data into a set of comma-separated values (CSV) files. Well suited for backing up data on a regular scheduled basis. Good option for smaller organizations. To export data on an adhoc basis.
  • Does not include metadata
  • Heavy Traffic can delay export delivery
Salesforce APIs Movingyour organization’s data and/or metadata to and from Salesforce. Customers can move data and metadata to either a 3rd party application or another Salesforce org. You have pre-existing enterprise software or middleware services for backing up critical data. Well suited for customers who have data warehouses, analytics/BI solutions, enterprise source control systems etc. You have over a million records to process and speed is a requirement.
  • Salesforce has governor limits for all APIs
  • Develop functionality to replicate / backup data & metadata using APIs
  • Bulk API Support
Full Sandbox Copy A Full Sandbox is an environment with a replica of your entire production org and all its data. Record IDs from production are preserved. Good option for taking a snapshot of production on a one-off basis. Consider this for pre-planned events.
  • Can only refresh full sandbox once every 30 days
Org Sync With Organization Sync, you can set up a secondary, synced Salesforce organization where users can work on your most business-critical processes and data whenever your primary organization is experiencing downtime or maintenance. Organization Sync is ideal for companies whose users need access to Salesforce at all times. When the primary organization is down for maintenance, users are redirected to the secondary organization until the maintenance is complete. All actions (creating a case, deleting an attachment, and more) that users perform in one organization are automatically applied to the other organization.
  • Subset of data and business processes
  • Initial setup and ongoing maintenance
Heroku Connect Cloud Based Service to move data to and from Salesforce to Heroku(Postgres). Using bi-directional synchronization between Salesforce and HerokuPostgres, HerokuConnect unifies the data in your Postgres database with the contacts, accounts and other custom objects in the Salesforce database. Does not count against API limits so this is a good option for high velocity changes.
Good option for consolidating data across multiple Salesforce Orgs for analytics, backup etc.
  • Heroku Connect does not support in-flight transformations.
3rd party data integration tools such as Informatica, Jitterbit, Cast Iron with Salesforce API support Mature data integration tools that support a wide range of database platforms, temporal requirements, large data volumes, and in-flight data transformations. These tools are well established in the traditional data integration space and now being adapted for cloud integration use cases. Tools provide a lot of flexibility by way of customization. Can support high velocity as well high volume, batch changes. Robust CDC capabilities with ability to support in-flight transformations.
Ideal for moving large volumes of data, consolidating data from multiple sources, and complex transformations. Typically do not count against API limits
  • Requires specialized developer skills. Support for new Salesforce APIs may not be immediately available.
Appexchange Products These offerings support automated backup of every standard and custom object in customer’s Salesforce database including accounts, leads, contacts, files, Chatter messages, and metadata.
The most popular ones are Backupify, Ownbackup for Salesforce, Spanning Backup, Odaseva
Tools provide a high degree of automation and are easily configurable with robust SF API support. Typically, can support multiple Salesforce environments
  • Some offerings are constrained by API limits. Very minimal transformation support.


Categories: Best Practices, Salesforce Architecture

Tags: ,

1 reply


  1. Salesforce Backup and Restore – Know Your Options — Blog.Salesforce.Study

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: