Guide
When to run Backup Now
Backup Now crawls the live store now. Use it when webhooks are not enough and before you restore.
Quick answer
Click Backup Now before a significant change, before a restore, and after an edit you are not sure was captured. It records new/changed/deleted items. Previous versions stay. Optionally pin the crawl as a named restore point (max 7).
Key takeaways
- One crawl at a time. If Backup in progress is showing, wait.
- Backing up the current (wrong) state is required so restore has something to revert from.
- Pin the crawl if you are on trial and need that point to last more than 7 days.
Who this page is for
- Anyone about to import a CSV or publish a theme
- Anyone about to restore an item or a restore point
Before a significant change
CSV import, bulk price edit, theme publish, or an app that rewrites catalog. Run Backup Now, wait until it completes, then make the change.
Before a restore
If the last crawl is stale, Backuply prompts you to run Backup Now first. The current live store — including the mistake — must be on the timeline. Restoring without that capture can leave you unable to return to “right before the restore.”
After a silent edit
BigCommerce often does not webhook inline/autosave product edits or thumbnail changes. Ecwid webhooks carry IDs only. Backup Now is the guarantee those edits are versioned.
- Confirm no crawl is already running.
- Click Backup Now. Optionally check Keep as restore point and set a label.
- Wait until the progress banner completes before restore or export.
FAQ
Does Backup Now overwrite yesterday?
No. Unchanged items are skipped. Changed items get a new version. Old versions remain until retention (or a pin keeps them).