Switch from RepairShopr

There are two ways out of RepairShopr and into BenchKey, and both end the same place: customers linked to their tickets, tickets linked to their invoices, nothing written until you approve a preview, and a clean rollback if you change your mind.

• Connect with your RepairShopr token (recommended): BenchKey pulls the data itself, no CSV wrangling.
• CSV import: export from RepairShopr yourself and drop the files in.

Both live in Settings → System → Data & Backups → Start import.

Option A: connect with your token

1. In RepairShopr, go to Admin → Tokens and create an API token. Give it all permissions so the importer can pull invoices and payments along with customers and tickets.
2. In BenchKey, open Settings → System → Data & Backups, choose RepairShopr, and enter your workspace name, the part before .repairshopr.com in your URL (for example mdrs if your URL is mdrs.repairshopr.com).
3. Paste the token and connect. BenchKey pulls your customers, tickets, and invoices in the background and respects RepairShopr’s rate limits while it works.

Your token is used for this migration and nothing else. You can delete it in RepairShopr the moment the import is done.

Option B: CSV export

Export your data as CSV from RepairShopr (their export tools cover customers, tickets, and invoices). Get at minimum Customers, Tickets, and Invoices; inventory and other lists can come later, imports are incremental.

Then in Settings → System → Data & Backups → Start import, drop the files in. The importer recognizes RepairShopr’s column names, people, phones, devices, statuses, money, and maps them automatically. Adjust anything it got wrong.

A RepairShopr-style CSV dropped in, detected, and mapped. Recorded from the real app with demo data.

Preview, then commit, then check

Either path lands on the same review screen: real rows, exactly as they will be written. Nothing touches your account until you approve it.

After the run, spot-check a handful of customers you know well: their tickets, their invoices, their totals. If anything looks off, roll the import back cleanly, fix the mapping, and run it again. Rollback means even a full import is not a commitment.

What carries over

• Customers with contact info
• Tickets with status, device, and customer links
• Invoices with totals and customer links
• Your old ticket numbers, kept on the record so old paperwork still cross-references

What to set up fresh

Statuses, automations, templates, and forms are worth rebuilding rather than copying, this is the moment to fix the workflow you always meant to fix. The fastest path: tell the AI assistant how your shop runs and let it build the starting configuration.

More detail on the importer itself: Import your data.