Compare
Native export vs Backuply
Platform CSV export is a snapshot of a slice. Backuply is a version stream of items you can restore without downloading a file.
Quick answer
Use native export for one-off reporting or a bulk edit you will re-import yourself. Use Backuply when you need undo: version history, Backup Now before a risky change, and restore of a selected item or Automated category as of a date.
Key takeaways
- CSV export does not version pages, themes, modifiers, or deletes as restore targets.
- Backuply does not replace your own CSV workflow; it versions what the APIs can write back.
- Backup Now before an import so the pre-import state is on the timeline.
Who this page is for
- Merchants who have recovered from a bad import with no prior version
- Operators comparing Backuply with “we already have CSV export”
What native export is good at
CSV export is useful for spreadsheets, BI, and a bulk edit you will re-import. It is a point-in-time file you hold.
It is not an undo. Re-importing a stale CSV can overwrite good data. It does not restore a deleted page or a previous theme zip.
What Backuply is good at
Backuply stores a new version when an item changes. You search the Vault, compare live vs a version, and restore that item. Advanced Restore updates a category as of a date without deleting newer items.
That model fails where the API cannot write (digital download files, some V2 rules, Instant Site, payment instruments). Those limits are documented per platform.
FAQ
Can Backuply export a zip of the store?
No. Restore is item-level and category-level through the platform API, not a downloadable archive of the whole store.