Back up your store and roll back changes instantly
RollbackPro, Vortex Backup, and DryRunPro give continuous backup and one-click rollback for BigCommerce, Shopify, and Adobe Commerce when something goes wrong.
Use this file to discover all available pages before exploring further.
Every ecommerce platform lets you make changes. None of them give you a reliable undo button. A bulk price import with a wrong column mapping, a contractor who edited the wrong product, a promotion that corrupted on migration — these are the everyday accidents that RollbackPro, Vortex Backup, and DryRunPro are built to recover from. Continuous backup runs in the background so you always have a recovery path, regardless of who changed what.
A confirmed rollback is irreversible for the records it targets. Before clicking Restore, use the side-by-side version comparison to verify that the version you are restoring is the correct one. Items already processed during a bulk or point-in-time rollback retain their restored state even if you cancel.
RollbackPro gives BigCommerce merchants something the platform itself does not: a real undo button. It continuously backs up your store and lets you restore any record — or an entire entity type — to any earlier version with a single click.
Backup runs in two modes depending on what BigCommerce exposes:Real-time backup listens to BigCommerce webhooks and captures changes as they happen. Entities covered by real-time backup:
Products, categories, customers
Channels, pages, email templates
Orders (backed up for version history only — not restorable)
Manual and scheduled backup covers entities BigCommerce does not expose webhooks for:
Brands, coupons, promotions, blog posts, 301 redirects, gift certificates
Trigger a manual backup from Settings before any major change to these entities, or configure a scheduled backup to capture them at regular intervals automatically. Every change captured creates a new version, so you can scroll back through prior states and restore to whichever was the last good one.
RollbackPro captures 14 BigCommerce entity types with their full field sets, including:
Products
Core fields (name, SKU, type, description, all pricing tiers, weight, dimensions, inventory, availability, condition, SEO and Open Graph fields, custom URL). Sub-entities: custom fields, bulk pricing rules, videos, images, options, modifiers, variants, reviews, and channel assignments.
Categories, brands, and customers
Categories (hierarchy, sort rules, SEO fields, image). Brands (name, SEO fields, custom URL). Customers (profiles, all addresses, form fields, store credit, channel associations, attributes).
Pages, blog posts, channels, 301 redirects, and gift certificates
Pages (HTML body, SEO fields, channel association, visibility). Blog posts (content, tags, SEO fields, thumbnail). Channels (name, status, visibility). 301 Redirects (source path and destination). Gift certificates (balance, status, recipient details, expiry).
Orders cannot be restored. BigCommerce orders cannot be deleted, and restoring them could trigger customer notification emails. Order versions appear in the Restore Center for comparison and reference only.
Navigate to the Restore Center tab in RollbackPro. Three filters let you narrow the grid: a full-text search across all entity fields, a date picker (presets include Today, 7 days, 30 days, 12 months, All Time, or a custom range), and a content type filter to isolate one entity type at a time.
2
Find the record
Search for the product name, SKU, customer email, or any other field value. The grid shows the ID, name, price, date modified, date created, and version number for each matching record.
3
Compare versions
Click Preview on a row. The side-by-side comparison opens in Summary view (human-readable field comparison) or Source Code view (raw JSON diff). Use the version dropdown to scroll through every tracked version and pick the one you want to restore.
4
Restore the record
Click Restore to this version. For a single record, the restore completes in seconds. The record is updated to match the stored version if it exists, or recreated if it was deleted.
For larger accidents, two additional rollback modes are available:Bulk rollback — select multiple records in the Restore Center grid and restore them in one orchestrated operation. The platform processes records in parallel batches with built-in API rate limiting, automatic retry for transient errors, real-time progress tracking, and cancellation at any point.Point-in-time rollback — restore an entire entity type (for example, all Products) to its state at a specific date and time. RollbackPro automatically discovers all records of that type modified at or before the target date and restores them in parallel batches. Use this after a bad CSV import that overwrote prices or descriptions across hundreds of products.
Vortex Backup gives Shopify merchants a per-record undo button. Real-time backup covers the entities Shopify exposes via webhook; on-demand manual backup covers the rest. You can restore a single product, a navigation menu, a delivery profile, or an entire entity type — without touching anything else in the store.
After installing, run a manual backup of all 17 non-realtime entities once to establish a complete baseline. From that point, real-time entities update automatically and the others update each time you run a manual backup.
Products: title, description, pricing, all images and media, variants, SKU, barcode, inventory per location, tags, SEO fields, product status, custom fields (metafields), vendor, and product type. Collections: title, handle, description, sort order, template, image, product associations (manual), and automation rules (smart collections including all rule types and match logic).
Customers
Name, email, phone, all saved addresses, customer tags, internal notes, tax exemptions, and marketing consent (email and SMS preferences). Customer passwords cannot be restored for security reasons.
Themes
Full ZIP archive including templates, sections, snippets, layouts, CSS and JS assets, and settings. Theme restore creates a new unpublished theme with a _restored_{timestamp} suffix — the current live theme is not overwritten.
Other entity types
Discounts (code-based and automatic, including value, rules, usage limits, schedule, and combination settings). Navigation menus (title, handle, all items, nested hierarchy, and links). Markets (regions, currency settings, web presence). Delivery profiles (shipping zones, rates, location groups). URL redirects, locations, price lists, catalogs, metafield definitions, metaobject definitions, and metaobjects.
Orders are backed up for reference but cannot be restored — Shopify protects them to preserve financial records. Customer passwords and blog comments cannot be backed up due to platform constraints.
Navigate to the Restore Centre tab in Vortex Backup. Use the search, date, and entity type filters to find the record you want to restore.
2
Find the record and pick a version
Records are matched by their original Shopify ID, so you can find the right item even if you renamed it. Click into the record’s version history and use the version dropdown to choose the state you want to restore.
3
Compare versions side by side
Use the Summary view for a human-readable comparison or Source Code view for a JSON diff. Verify that the selected version is the state you want before proceeding.
4
Restore
Click Restore. If the item exists it is updated to match the stored version. If it was deleted it is recreated — Shopify may assign a new ID, but Vortex Backup tracks the original ID for future rollbacks. For products, inventory is restored per location matched by location name.
Smart collections restore with their automation rules intact — Shopify rebuilds product membership automatically. Manual collections explicitly restore product associations.
DryRunPro is the Adobe Commerce Cloud staging launcher inside Vortex Apps. One DryRunPro account holds many Adobe Commerce Cloud projects and gives every project a clean, isolated, on-demand dryrun staging surface that mirrors the production Magento topology. You spin a dryrun, push a branch into it, run smoke tests and a SWAT report, and merge with confidence.
Adobe Commerce Cloud ships with three environment tiers per project: integration, staging, and production. That ceiling becomes a bottleneck the moment you have multiple feature branches queued for QA at the same time. DryRunPro removes the bottleneck by giving every project an on-demand dryrun fleet.A dryrun is a fully isolated clone of your production environment, spun up against any branch you point at it. Each dryrun runs SWAT reports, extension audits, and code audits. When you are done, tear it down with one click and the resources return to the pool.
One DryRunPro tenancy manages many Adobe Commerce Cloud projects at once. The Projects tab shows each project with two columns of metadata: the Adobe Commerce Cloud column (environments, storage, users) and the DryRun Pro column (staging environments, packages, users). A team assignment on each project card lets you route groups of users to the right projects without per-user access grants on every project.
From the Dryrun Environments tab, click the launcher, select the project, and point it at the branch you want to test. The environment typically spins up within a few minutes.
2
Run tests and audits
The dryrun generates a public Fastly-fronted URL your whole team can hit. Run smoke tests, review the SWAT report, check extension audits, and run bin/sync against the canonical environment to catch any drift.
3
Promote or discard
If the dryrun is green, promote the branch to the Adobe Commerce Cloud staging or production environment. If the dryrun reveals a problem, discard it, fix the branch, and spin a new dryrun. There is no impact on the live store.
4
Download environment packages
Completed dryruns produce downloadable artefacts available on the Packages tab until the dryrun is torn down. These let your development team replicate the environment locally if needed.
DryRunPro requires an Adobe Commerce Cloud subscription with super-admin credentials. It does not work against Magento Open Source or on-premise Adobe Commerce installations.
DryRunPro dryruns are ephemeral by design — they are torn down when their job is done. The staging packages (Docker snapshot and Warden package) that each completed dryrun produces remain available for download until the dryrun is deleted. For point-in-time backup and restore of data at the entity level, pair DryRunPro with your Adobe Commerce Cloud platform’s built-in snapshot tools.
