Backups in SFCC: What You Need to Protect Your Store

Backups aren't sexy, but when things break (and they eventually will), they’re your lifeline. If you're working with Salesforce Commerce Cloud (SFCC), having a solid backup strategy can be the difference between a bad day and a total disaster.

Let me walk you through how we’re handling it on our side, and maybe you’ll get some ideas for your own setup.

The goal is simple: be able to recover quickly if something serious happens. Whether it's a platform failure, human error, or corrupted data, we want to restore everything we need to keep selling without missing a beat.

In the staging environment, we run three types of backups. One covers the platform configuration — things like site preferences, OCAPI settings, and tax rules. Another one focuses on dynamic business data like promotions, pricebooks, and content slots. And finally, we take a weekly snapshot of static files, mostly product images and library assets.

These backups are stored in the Impex folder and accessed via WebDav. With a properly configured Client ID in Account Manager, a simple integration pulls the files to external storage. Nothing fancy, just consistent and reliable.

As for source code, we rely on GitHub and CI/CD pipelines for everything. Our full deployment history is there, and if needed, we can roll back by grabbing one of the last 10 deployed cartridge versions, which SFCC keeps available in WebDav.

Now, production is where things get more delicate. Salesforce does have its own disaster recovery process (you can check this official article), but it doesn’t include things like customer accounts or order history. If you want to give your users a full recovery experience — letting them log in and see their past purchases — you’ll need to export that data manually. Customers can usually be restored using external tooling. Orders are trickier. Since they impact GMV and reporting, restoring them might require Salesforce's help.

So that’s where we are: backups running daily in staging, static content saved weekly, source code in Git, and a plan to start backing up critical production data like customers and orders.

It’s not glamorous work, but it’s the kind of thing that keeps your business alive when things go sideways.