Shopify Backups: Export Limits and a Store Recovery Checklist
Documentation checked October 5, 2026. This guide combines official Shopify documentation with HRL planning recommendations. It does not report hands-on store, restoration or billing tests.
A backup is useful when it can help you recover the thing that went wrong. A product spreadsheet may help repair a catalogue; it does not automatically restore orders, app settings and a functioning checkout to one consistent point in time.
HRL recommends defining the recovery problem before choosing a backup app. Are you protecting against accidental product edits, theme changes, deleted content, or a wider interruption? Each requires different records, restore permissions and acceptance checks.
What Shopify documents as a backup
Shopify’s backup and duplication guide describes CSV exports for products, customers, orders, gift-card codes, discount codes and financial data, plus a theme download. Its duplication workflow still requires app reinstallation and manual settings work.
That guide says orders cannot be imported through the standard Shopify admin; third-party apps or the API are separate routes. It also lists issued gift cards, discount codes, custom reports and visitor traffic among duplication restrictions. A Theme Store theme is licensed to its original store. Treat export availability and supported recovery as different questions.
Build a recovery inventory
| Store area | Preserve | Prove before relying on it |
|---|---|---|
| Catalogue | Products, variants, media and collection relationships. | Restore a representative item with its options and images. |
| Theme and content | Theme version, pages, menus and custom changes. | Restore the intended layout without removing newer required changes. |
| Trading records | Orders, customer records and outstanding obligations. | Explain how older records coexist with newer orders and stock. |
| Apps and integrations | Settings, app-owned data and external accounts. | Verify each service’s own export and recovery path. |
| Access and operations | Account ownership, permissions and recovery contacts. | Confirm who can authorize and carry out recovery. |
The table is an HRL planning checklist, not a claim that Shopify or any app supports every row. Ask the selected service which fields it captures, what it excludes, when collection begins, and whether it can recover records deleted before installation. Obtain explicit answers rather than assuming “automatic backup” covers the whole business.
How often should a store back up?
Set the interval from the amount of change you can afford to reconstruct. A catalogue edited occasionally and a store receiving frequent orders have different recovery needs. Record your acceptable data gap and recovery time, then check whether the proposed service meets both.
Keep a dated export before bulk edits, a theme change or a migration. Store sensitive records with controlled access and a documented retention policy. Avoid leaving customer exports in shared folders that everyone can open.
Recover without overwriting newer activity
- Identify the affected records, the last known correct state and changes since that point.
- Preserve the current state before attempting a restore, where the selected workflow allows.
- Choose the narrowest repair that addresses the problem; document which records it will replace.
- Reconcile orders, stock changes, refunds and other obligations created after the backup.
- Check product pages, checkout, notifications and required integrations after recovery.
These are HRL incident-planning recommendations. Avoid a broad rollback simply because it is available. Restoring an old catalogue can also restore outdated stock assumptions; trading records need reconciliation rather than blind replacement. If the restore tool cannot explain its overwrite behavior, escalate to its support before using it on the live store.
Questions to ask a backup app provider
- Which objects and app-owned data are captured, and which are excluded?
- What are the frequency, retention period and export options?
- Can individual records be restored, and what happens to newer changes?
- Can a restore be demonstrated safely outside the production workflow?
- Who can access the backup, and what happens after uninstalling or canceling?
Price the verified service in the app and renewal budget. We have not tested or ranked backup apps here, so no provider receives a recovery endorsement.
Write a recovery question that an export can answer
For a hypothetical accidental product edit, identify the saved record, how it will be restored and how newer product changes will be preserved. For a deleted integration configuration, ask whether the same backup covers it at all. Record the result for each object type. A product CSV and a theme download are useful assets, but their presence does not establish complete store recovery.
Recovery is separate from moving platforms
A recovery process aims to repair an existing store; migration must make the destination work. Read export versus backup and our Shopify-to-WooCommerce migration checklist for that distinction. Use the launch checklist to define the customer journey you must verify after a repair.
See our review methodology and affiliate disclosure. Provider links are direct. App capability, pricing and account-specific conditions must be verified for the selected service.