How do I import my history?

Where it goes

Open Integrations and find the history import. Choose the location the past work belongs to, then choose a .csv file exported from your old system — one row per past repair.

What the file needs

Each column is matched to a field by its own heading; a heading nothing matches is simply left out of the import, not refused. A row needs at minimum a history reference and a customer name — those are what a past repair is identified by. A row missing both of those cannot be imported at all.

Check before it writes anything

As soon as the file is read, four counts appear: rows in the file, rows ready to import, rows left out, and columns not matched. Check the import runs those same rows through a dry run — nothing is written — and reports what it would import, skip, or refuse.

Then import it

Only after the check has run does Import N rows appear. It sends the file in chunks and reports what actually landed: imported, skipped, and refused, with the reason for each refusal. The import is keyed on each row's own reference, so running it again after a partial failure picks up where it stopped rather than doubling what already landed.

What this is not

This is not a Tekmetric connection, and no migration needs one: every shop's history, whatever it runs today, comes in through this CSV import. BayStacker does keep a separate, ongoing Tekmetric connection for a shop that goes on using Tekmetric day to day, but it is not a migration tool, and turning it on needs an authorized partner connection that is not open to every shop today — do not plan a switch around it. Plan on CSV.