Join the waitlist

Bring your shop records to BenchKey

Connect RepairShopr or RepairDesk, or import CSV or Excel files. Preview before saving; your old system stays unchanged. Every plan includes imports. Imported tickets never count toward Standard's 75 new tickets a month.

Join the waitlist Read import guide
A recreated Migrate Data screen after a sample RepairShopr import. The record counts are illustrative.

See which records come over

Choose your current system to see what the importer brings over, what needs a file export and what stays behind.

Where your records are now

Open Migrate Data in System settings. Enter your RepairShopr address and a Custom Permissions API token that can read the records you want to import. Preview counts: customers are exact; tickets, invoices and payments are estimates. RepairShopr stays unchanged.

Records in a direct RepairShopr import
Record typeImport statusDetails
Customers Imports directly Customer profiles with phone numbers, including extras, emails and addresses
Tickets Imports directly Comments, messages and their files transfer, with device password, ticket and issue types, technician, signatures and uninvoiced charges
Invoices Imports directly Invoices import with their line items. The token needs invoice access; the preview flags missing access
Payments Imports directly Payments import directly from RepairShopr. Review the saved payment records before you switch
Estimates Imports directly Estimates import with their line items
Inventory items Imports directly Products and inventory import from RepairShopr
Customer assets (equipment tracking) Imports directly Assets and devices import directly as device records in BenchKey, including the separate asset list
Leads Imports directly Leads import directly from RepairShopr in every status, including New and Won
Appointments Imports directly Appointments import directly from RepairShopr, including appointments that are not linked to a ticket
Canned responses Imports directly Saved replies import directly from RepairShopr as canned responses in BenchKey
Additional contacts on a customer Not imported directly The primary customer comes over. Additional named contacts stay in RepairShopr

Records in a direct RepairShopr import

  • Customers Imports directly

    Customer profiles with phone numbers, including extras, emails and addresses

  • Tickets Imports directly

    Comments, messages and their files transfer, with device password, ticket and issue types, technician, signatures and uninvoiced charges

  • Invoices Imports directly

    Invoices import with their line items. The token needs invoice access; the preview flags missing access

  • Payments Imports directly

    Payments import directly from RepairShopr. Review the saved payment records before you switch

  • Estimates Imports directly

    Estimates import with their line items

  • Inventory items Imports directly

    Products and inventory import from RepairShopr

  • Customer assets (equipment tracking) Imports directly

    Assets and devices import directly as device records in BenchKey, including the separate asset list

  • Leads Imports directly

    Leads import directly from RepairShopr in every status, including New and Won

  • Appointments Imports directly

    Appointments import directly from RepairShopr, including appointments that are not linked to a ticket

  • Canned responses Imports directly

    Saved replies import directly from RepairShopr as canned responses in BenchKey

  • Additional contacts on a customer Not imported directly

    The primary customer comes over. Additional named contacts stay in RepairShopr

RepairShopr import guide Compare BenchKey and RepairShopr

Connect in Migrate Data with an Offline Token, or choose Use RepairDesk sign-in instead; old-style API keys don't work. RepairDesk stays unchanged. Tickets include passcodes, device custom fields, accessories, device notes and due dates.

Records in a direct RepairDesk import
Record typeImport statusDetails
Customers Imports directly Customers import with their profile fields
Tickets Imports with limits SMS, email, team-only notes, device photos and status history import. Files attached to staff notes stay in RepairDesk because its API omits them; download any you need there.
Invoices Imports directly Invoices import, including those not tied to a ticket
Payments Imports directly Ticket invoice payments import as real payment records with their actual dates and methods, including split payments. Invoices sold without a ticket arrive with one summary payment each. Check the imported records against RepairDesk before cutover.
Inventory items Imports directly Inventory items import directly from RepairDesk
Call logs Imports directly Call logs import directly from your RepairDesk account
Leads Imports directly Leads import directly from your RepairDesk account
Appointments Imports directly Appointments import directly from your RepairDesk account
Estimates Not imported directly Estimates use RepairDesk's CSV export in Migrate Data's file option. Its API has no estimates endpoint

Records in a direct RepairDesk import

  • Customers Imports directly

    Customers import with their profile fields

  • Tickets Imports with limits

    SMS, email, team-only notes, device photos and status history import. Files attached to staff notes stay in RepairDesk because its API omits them; download any you need there.

  • Invoices Imports directly

    Invoices import, including those not tied to a ticket

  • Payments Imports directly

    Ticket invoice payments import as real payment records with their actual dates and methods, including split payments. Invoices sold without a ticket arrive with one summary payment each. Check the imported records against RepairDesk before cutover.

  • Inventory items Imports directly

    Inventory items import directly from RepairDesk

  • Call logs Imports directly

    Call logs import directly from your RepairDesk account

  • Leads Imports directly

    Leads import directly from your RepairDesk account

  • Appointments Imports directly

    Appointments import directly from your RepairDesk account

  • Estimates Not imported directly

    Estimates use RepairDesk's CSV export in Migrate Data's file option. Its API has no estimates endpoint

Invoices Full Excel exports have a dedicated upload option. If RepairDesk rejects your token during import, don't start another run. Follow the import page.

RepairDesk import guide Compare BenchKey and RepairDesk

Export CSV, Excel, TSV or text files. Choose the file option and source system, upload, map columns, check the preview and select the store. RepairQ and other systems use this route.

Records you can map from a file
Record typeImport statusDetails
Customers Map to import Names, phone numbers, emails, addresses, notes and customer creation dates, when mapped
Tickets Map to import Map an identifying field: ticket ID, ticket number, device or subject
Invoices Map to import Invoices and totals; check the money format in the preview
Line items Map to import Invoice line items from a separate file or mapped columns
Payments Map to import Payment amounts, methods and invoice numbers; vendor invoice exports can include individual payments
Estimates Map to import Estimate numbers, customers, totals and statuses
Inventory Map to import Parts with SKU, name and quantity columns
Notes Map to import Notes linked to their tickets
Time logs Map to import Time logs with ticket and technician details
Leads Map to import Leads, including those exported from RepairShopr
Appointments Map to import Appointments with customer, time and title fields

Records you can map from a file

  • Customers Map to import

    Names, phone numbers, emails, addresses, notes and customer creation dates, when mapped

  • Tickets Map to import

    Map an identifying field: ticket ID, ticket number, device or subject

  • Invoices Map to import

    Invoices and totals; check the money format in the preview

  • Line items Map to import

    Invoice line items from a separate file or mapped columns

  • Payments Map to import

    Payment amounts, methods and invoice numbers; vendor invoice exports can include individual payments

  • Estimates Map to import

    Estimate numbers, customers, totals and statuses

  • Inventory Map to import

    Parts with SKU, name and quantity columns

  • Notes Map to import

    Notes linked to their tickets

  • Time logs Map to import

    Time logs with ticket and technician details

  • Leads Map to import

    Leads, including those exported from RepairShopr

  • Appointments Map to import

    Appointments with customer, time and title fields

Check date and money formats in the preview. Ambiguous dates need a format choice. Columns that don't fit a BenchKey field won't show in BenchKey; the rest of each row still imports. Download the row report afterward to see what didn't come over.

Spreadsheet import guide Compare BenchKey and RepairQ

Choose a connection or a file export

Both routes start in Migrate Data under System settings and show a preview. A direct connection skips the export step and can carry more ticket detail.

Direct connection

  • Both import messages and payments. RepairShopr transfers message files; staff note files stay in RepairDesk.
  • Preview counts and choose record types. Start with customers, check them, then import the remaining history.
  • Runs on BenchKey's servers, so you can close the tab. Shared provider limits can slow or delay the import.

File import

  • Accepts CSV, Excel, TSV and text exports in different column layouts from your current system.
  • File imports avoid your old system's API rate limits; duration depends on the records and waiting work.
  • You check suggested column matches. Optional AI receives anonymous column IDs and broad value types, within a monthly allowance.
  • Vendor exports can omit conversations, attachments, payment detail, contact preferences and links between customers, tickets and invoices.
Check the sample rows and adjust column matches before the import writes any records.

Watch data import in BenchKey

The shop and customers are made up. English narration with captions in English, Spanish, and Brazilian Portuguese.

Check the records before switching your counter

Start with a small sample and check it before the full import.

  1. Your existing records

    Connect RepairShopr or RepairDesk, or export files. Keep a separate copy of every export.

  2. Preview

    Review record counts or sample rows before saving. Fix column matches and any required fields.

  3. Import

    The import runs on BenchKey's servers and saves progress. Close the tab and return to Migrate Data to check it.

  4. Verify

    Read the result, open familiar records and check their links. Use the row report to fix anything that didn't import.

Give each store its own import

Direct connections reject accounts with multiple stores before saving anything. Export each store's records separately, then import its files into the matching BenchKey store. The importer needs you to choose where the records belong.

  • Choose a destination for every source store found in the file, including records with no store listed.
  • Multiple stores require Business. US monthly pricing: $149 for the first store, $79 per additional store.

Know what Undo can leave in place

Open an import under Your imports in Migrate Data and choose Undo this import, then Undo import. It removes unchanged imported records, including unused customer profiles it created.

What Undo can remove

  • Available for 7 days after an eligible import finishes.
  • Unchanged records created by the import, including unused customer profiles, devices, categories and vendors it can be verified to have created.

What stays or blocks Undo

  • Customer profiles already used or changed, shared with another import, or that existed before stay. Changed or shared records are kept and listed. Email and text opt-outs stay.
  • Stock already used or transferred stays in place.
  • Imports that brought in invoices, estimates or payments can't be undone. Changed or used imported tickets also block Undo. A later import can block Undo if it still holds the same customers or brought in records for them from the same account.

You can't reverse an Undo. Preview a small customer file carefully before importing tickets, invoices and inventory.

Plan when the counter switches systems

Choose a clear cutover moment, such as the end of the week. Agree where staff will enter new repairs from then on.

  1. Keep your export files

    Save copies somewhere separate from either system, so you can refer back to the original records.

  2. Check a small sample

    Start with a small customer file. Check the mappings and saved customer records before bringing over the rest.

  3. Set up your shop

    Prepare statuses, templates, message automations and intake forms before staff enter the first new repair.

  4. Run the full import

    Bring over the remaining records. Check the result, open familiar tickets and compare their invoice totals with the old system.

  5. Agree the cutover time

    Tell staff when new repairs will go into BenchKey. Choose a clean break, such as the end of the week.

  6. Import the latest records

    Run again before cutover for new records. Choose one route for your tickets: a direct connection or files. Tickets imported through one route aren't matched by the other. Invoices and payments come from one import source per shop.

    Tickets20,317 already in BenchKey

  7. Close the old connection

    After checking the final import, revoke the token or delete the OAuth client. Update your website's lead widget and customer instructions.

Check the records your staff will use

Open customers and repairs you know well. Check that tickets, invoices and customer records still connect, as well as comparing counts and totals.

  • Pick familiar customers and confirm that their tickets and invoices are attached to the right records.
  • Compare ticket details, invoice totals, payment dates and methods with your old system.
  • Read the result status and counts for each record type, including anything that only partly imported or didn't finish.
  • Download the row report to see which rows didn't come over and why.

We run your import on Business

Send us your export or tell us your old system, and we'll run the import for you on Business. Every plan includes the same importer and preview if you want to handle it yourself.

Trial accounts can also request migration help. Confirm the scope and availability with support.

Compare plans

Questions about moving your records

How long does an import take?

Timing depends on record volume, histories, attached files and your source system's shared rate limits. An import may wait its turn. File imports avoid provider API rate limits. Imports keep running after you close the tab; return to check progress.

Do imported tickets count toward Standard's monthly ticket limit?

No. Imported tickets never count toward Standard's 75 new tickets a month. The importer is included on every plan.

Will the import change my old system?

No. BenchKey only reads a copy. After you've checked the final import, revoke the token or delete the OAuth client in the old system.

Can I keep my existing ticket numbers?

For a RepairShopr direct import, choose Keep RepairShopr’s ticket numbers · Recommended or Give them new BenchKey numbers. New numbers apply only to newly imported tickets. Previously imported tickets keep their saved numbers, and original provider IDs and numbers are retained.

Can I import from RepairQ or another system?

Yes, through a file export. Under Where are these files from?, choose your source system or leave Work it out from the files. Map the columns and check the preview before importing. RepairQ uses this file route.

The waitlist is open for repair shops

Leave your email for access updates. Your name and shop name are optional.

Join the waitlist Talk to us
Watch the product tour 3:34 Follow a repair from check-in to pickup in BenchKey