RepairPlugin
Admin & reportingIncluded on every plan

Build on staging.
Ship to production.

Set up your full RepairPlugin catalog on a staging site, perfect every model, price, and setting, then export it to a single .rpdata file and load it onto your live site. Your active license code must be the same on both sides.

1
file for everything
1
license required
8 MB
chunked upload
Import / Export
.rpdata · full backup
8 MB chunks
Export
repairplugin-2026-04.rpdata
42.3 MB · ready
100% complete
Import
Drop .rpdata here
or browse files
FileSizeStatusAction
repairplugin-2026-04.rpdata42 MBReadyRestore
repairplugin-2026-03.rpdata39 MBReadyRestore
repairplugin-2026-02.rpdata37 MBReadyRestore
Why repair shops use it

Set up once. Move it anywhere.

Built for internal moves: configure on staging, ship to production, or take a snapshot before risky changes. The .rpdata file carries your entire setup in one go.

Exporting…
repairplugin.rpdata42.3 MB
78% · 9 of 12 tables
· Models · Brands · Categories
· Prices · Schedules · Settings
1import to live

Build on staging, deploy to production

Configure RepairPlugin on a staging site without touching customers, models, brands, repairs, prices, schedules, and settings. Export the result to a single .rpdata file and import it on your production site. No copy-paste, no rebuilding the same catalog twice.

License check
Source
staging.shop.com
ACTIVE
Destination
shop.com
ACTIVE
Same license code
1matching license

Same active license, both sides

To restore an .rpdata file, the destination site needs the same active RepairPlugin license code as the source. Activate your license on the target site first, then run the import. Without a matching active license, the import will not start.

Backup history
Apr 2026
42 MB
Mar 2026
39 MB
Feb 2026
37 MB
Jan 2026
34 MB
snapshots stored

Snapshot before risky changes

Run an export before bulk edits, big imports, or catalog overhauls. Every export is saved in a management table with file name, size, and timestamp, so you can roll the shop back to the exact state it was in at any earlier point.

Upload chunks8 MB · ea.
5 / 8 uploadedno timeouts
8 MBupload chunks

Large files import without timeouts

Imports are automatically split into 8 MB chunks during upload, so 40+ MB backups complete on shared hosting with strict upload limits. No timeouts, no half-finished imports, and the destination ends up identical to the source.

How it works

Three steps. Staging to live.

From a fresh export on your staging site to a fully restored production setup, with cache cleanup, in under ten minutes.

Step 1 · export
Start Export
62% · gathering tables…
1

Export from your source site

On the staging or source site, go to RepairPlugin > Settings > Import / Export Data and click Start Export. A progress bar tracks the export. When it finishes, the .rpdata file appears in the management table and downloads to your machine.

Step 2 · import
repairplugin.rpdata
42.3 MB · chunked
2

Activate your license, then import

On the destination site, make sure RepairPlugin is installed and that your license code is active and matches the source. Click Start Import, upload your .rpdata file (chunked automatically for large files), and the import runs to completion.

Step 3 · clear caches
Varnish & HTML
Database
Object
3

Clear caches and verify

Disable Varnish and HTML cache if active, clear the database cache and object cache, then load your booking page to confirm everything looks right. Your customers now see the imported setup live.

Plan availability

Included on every plan.

Import and export are core admin tools, available from Essentials onwards.

EssentialsIncluded

Included

GrowthIncluded

Included

ScaleIncluded

Included

FAQ

Common questions.

Can I use this to migrate from a staging site to production?

Yes, that is the main use case. Build and test your full setup on staging, export to .rpdata, then import on production. As long as the same license code is active on both sites, the destination becomes an exact copy of the source.

Do I need the same license on both sites?

Yes. The destination site needs the same active RepairPlugin license code as the source. If your license is tied to a single domain, deactivate it on the source first, then activate it on the destination before importing.

Can I import into a site that already has RepairPlugin data?

Yes, but importing replaces all existing RepairPlugin data with the contents of the .rpdata file. Always run an export on the destination first as a fallback before importing.

Do I need to clear the cache after importing?

Yes. Disable Varnish and HTML cache if active, then clear your database and object caches. Without this, customers can still see the pre-import configuration in the booking flow.

Documentation

Read the full guide.

Export internals, the chunked-upload pipeline, multi-version backup management, license requirements, and post-import cache rules, straight from the help centre.

Popular topics

Turn visitors into customers.

Join 583+ repair shops already fixing their massive drop-offs.
Easy to install and live on your WordPress site in minutes.