Native importer
Migrate from Tekmetric to Pitlane. One CSV, no manual mapping.
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. The import is a single one-way CSV pull you run inside your account, previewed before anything writes.
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 (these don't transfer via CSV; Pitlane writes new ROs itself)
- —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). Signup is instant, there's no email-confirmation wall. 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. A preview shows exactly what will land before anything writes.
- 5
Connect Stripe and paste your Google review link
Two more steps: connect Stripe so customers can pay by a texted link, and paste your Google review link so review requests route to the right page. Texting activates after carrier registration, usually a few business days. Pitlane files the registration.
After the migration: what to keep, what to drop.
Keep
- Tekmetric for your historical repair orders and parts (RO line items don't transfer via CSV; Pitlane writes the new ones)
- 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 on your shop's own dedicated local number and automated follow-ups, in the base price)
- —Tekmetric's basic review-request flow (Pitlane sends an automated review request after pickup)
- —Manual win-back campaigns (Pitlane runs automated win-back sequences for lapsed customers)
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 historical line items, keep Tekmetric for that history and let Pitlane handle the customer-side workflow and new repair orders.
Can I run Pitlane and Tekmetric in parallel?
Yes. That's the standard path right now. Pitlane runs alongside Tekmetric: import your Tekmetric Customer List, 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 takes over what Tekmetric's was doing, it doesn't stack on top of it. Run one outreach system, not two.
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. If a customer already exists in Pitlane, the importer skips the duplicate row instead of overwriting your existing data.
Migrating from another tool?
Run your next job on one work order.
Start free for 30 days. No credit card, no setup fee, no per-transaction platform fee.