Native importer
Migrate from Tekmetric to Pitlane in under 10 minutes.
Pitlane has a native column-aware importer for the Tekmetric "Customer List" CSV export. Phones, emails, addresses, vehicles (VIN, year, make, model, plate), last-known mileage, and last-RO date all map across without manual column mapping.
The migration tool runs entirely inside your Pitlane account at /settings/migration. There's no integration to set up, no sales call, and no per-row charge. Most 2-3 bay shops are fully imported in a single coffee break.
What transfers from Tekmetric
- Customer first/last name, phone, and email — deduplicated by email or phone
- Address, city, state
- Vehicles per customer with VIN, year, make, model, license plate
- Last-known mileage per vehicle
- Last RO date as a service-record stub (full RO line items don't transfer)
What stays behind (and why)
- —Repair-order line items, parts, and labor (Pitlane's RO writer is in beta as of May 2026)
- —Inventory and parts catalogs (those stay in Tekmetric)
- —Internal tech notes that aren't tagged on the Customer List export
Where to find the export inside Tekmetric.
Tekmetric → Reports → Customer List → Export to CSV. The newer 'split by vehicle' export and the older single-row-per-customer format both work.
The full migration in five steps.
- 1
Export your Customer List from Tekmetric
In Tekmetric, run the Customer List report and export it as CSV. Don't filter — let the full list come out. The importer dedupes on email or phone, so re-imports stay safe.
- 2
Sign up for Pitlane
Create your account (no credit card). Skip the sample-data toggle on step 4 if you'd rather start fresh — the migration will populate the workspace.
- 3
Open Settings → Migration
Drop the CSV in. Pitlane auto-detects the Tekmetric format from the column fingerprint (the 'Customer ' prefix is distinctive), maps every column, and shows a preview before the import.
- 4
Confirm and import
Review the row count and a sample of warnings (rows with no first name, malformed phones, unparseable years). Click import. The job runs in seconds for typical shop lists; multi-thousand-row imports stream in.
- 5
Connect Stripe and your Google Business Profile
Two more clicks: connect Stripe so customers can pay invoices, and link your Google Business Profile so review requests route correctly. You're done.
After the migration: what to keep, what to drop.
Keep
- Tekmetric for repair orders, parts, and labor estimates (until Pitlane's RO writer reaches GA)
- Your existing tech workflow on the shop floor
- Any third-party integrations you actively use (accounting, parts ordering)
Drop
- —Tekmetric's customer messaging add-on (Pitlane handles two-way SMS, A2P 10DLC, and auto-followups)
- —Tekmetric's basic review-request flow (Pitlane's star-gating routes 4-5 stars to Google, 1-3 stars to private feedback)
- —Manual win-back campaigns (Pitlane runs 90/120/180-day sequences automatically)
Questions about migrating from Tekmetric.
Does Tekmetric export contain service history?
Not deeply — the Customer List export gives last-RO date and last-known mileage but not full RO line items. Pitlane brings those across as service-record stubs so reminder logic still works. If you need full history, keep Tekmetric running and let Pitlane handle the customer-side workflow until the Pitlane RO writer reaches GA.
Can I run Pitlane and Tekmetric in parallel?
Yes — that's the standard path right now. Most shops import their Tekmetric Customer List into Pitlane, run Pitlane's customer-side workflow (reviews, follow-ups, DVIs, payments), and keep Tekmetric for the RO workflow. There's no duplicate-billing risk because Pitlane's customer outreach replaces Tekmetric's, not adds on top of it.
What if my Tekmetric export has columns the importer doesn't recognize?
The parser ignores unknown columns rather than failing. Your import still completes; the unrecognized columns just don't transfer. If you need a specific field that's missing, email support@usepitlane.com with the column name and we'll map it in the next provider release.
Does the import overwrite existing customers in Pitlane?
No. The importer dedupes by email first, phone second, then a name-based fallback. If a customer already exists in Pitlane, the importer skips the duplicate row instead of overwriting your existing data.
Ready to import your Tekmetric list?
30-day free trial, no credit card. The migration tool is included in the trial — drop in your CSV and you’re live.