Switching software
Spreadsheet to CRM: Move Your Shop's Data
The short version
- A spreadsheet export — a CSV with a header row — imports straight into Service VIN; the column matcher recognizes dozens of common headers and you map the rest with a dropdown.
- Clean the sheet first: one field per column, one email and one phone per cell, consistent formatting, and dead leads removed.
- Dedupe on a real unique key, like a normalized email or phone, before you import.
- Back up the sheet and test a small batch first; a spreadsheet has no undo, but Service VIN's re-import is safe.
- The dry-run validation report flags blanks, duplicates and bad rows by row number before a single record is written.
The spreadsheet did its job — here's when it stops scaling
A spreadsheet is a perfectly good first tool. It's cheap, it's fast, and it does not judge you. But there comes a job where you're scrolling row 812 looking for the guy who wanted a full front in the spring, and you realize the sheet stopped helping you a hundred customers ago. Now it's just where information goes to get lost.
I'm not here to trash the humble grid. Half the shops I know started exactly where you are — a green-and-white sheet, a few color-coded tabs, a column for “called back?” that slowly filled with nobody's honest answer. It got the shop off the ground. The problem isn't that the spreadsheet is bad. It's that it can't grow with you, and past a certain size it quietly starts costing you money instead of saving it.
Here are the tells, and you'll recognize at least two:
- Double-entry. A customer texts, you write it on a sticky note, then you type it into the sheet later — if you remember. Every hop is a chance to drop a digit or a lead.
- No follow-up.The sheet doesn't nudge you. It can't remind you that the ceramic quote you sent three weeks ago is going cold. It just sits there, and so does the lead.
- Three versions of the same file. customers_FINAL.xlsx, customers_FINAL_v2.xlsx, the one on your phone that's two weeks behind. Which is right? Nobody knows, and that's the whole problem.
- The history lives in your head.You know Dave likes his rocker panels done and pays cash. That's worth real money, and it exists nowhere but your memory. The day you hire a second installer, none of it transfers.
None of that means you failed at spreadsheets. It means you outgrew them. The sheet capped how big the shop could get, and you've hit the cap. Good news: getting off it is a lot less scary than the dread makes it feel, and you don't have to lose a single row to do it.
What a CRM gives you that a sheet never will
Before the how, let's be clear on the why — because “a fancier spreadsheet” is not the pitch. The difference isn't prettier cells. It's that a real customer CRM turns a flat list into a working system where things actually happen on their own.
In a sheet, a customer is a row. In a CRM, a customer is a record — and everything that ever happened with that person hangs off it. The vehicles they own, with the VIN and plate. The quote you sent and whether they opened it. The deposit they paid. The booking history. The note that says “prefers text, hates phone calls.” All of it in one place you can pull up in a second, instead of scattered across a sheet, your inbox, and your memory.
That's the part that changes the math. When every contact is a real record, nobody falls through the cracks — because the system can watch the cracks for you. The quote that's gone quiet gets a follow-up nudge. The customer who booked a coating last year is due for a maintenance wash. And the cold leads that would've just rotted at the bottom of a sheet become a win-back list you can actually work, instead of forgotten rows nobody will ever scroll to again.
A spreadsheet stores. A CRM works. That's the upgrade, and the whole rest of this post is just how to get your book from one to the other without leaving anyone behind.
Illustrative example, not measured data — the bars show the shape of the effort, not a benchmark. Actual work depends on your file.
| Item | Re-type by hand (relative effort) | Mapped CSV import (relative effort) |
|---|---|---|
| Enter contacts | 100relative effort | 5relative effort |
| Fix duplicates | 100relative effort | 15relative effort |
| Keep vehicles & notes attached | 100relative effort | 5relative effort |
The honest secret: cleaning is the slow part, not importing
Let me set the right expectation before we start, because it'll save you a bad afternoon. The import is fast. Genuinely — you drop a file in, the columns line up, you review, you commit. Minutes. The part that takes real time is what you do to the sheetbefore it ever touches the importer.
That's not a knock on the tool. It's true of every migration, and every serious guide on moving off spreadsheets says the same thing: clean and standardize first, dedupe on a real key, back up, and test a small batch before you run the whole file. The reason is simple — garbage in, garbage out. A messy sheet imports into a messy CRM, and now the mess lives in a nicer house.
So the steps below front-load the boring work on purpose. Push through the cleanup and the actual move is the easy, satisfying part. Skip the cleanup and you'll spend next week untangling three copies of the same customer. Do it once, do it right.
Spreadsheet to CRM, step by step
- 1
Decide what's actually worth bringing
Open the sheet and be ruthless. Every old file is stuffed with dead leads, the tire-kicker who ghosted in 2022, and columns somebody added once and never filled. Migration is your one clean moment to leave that weight behind — it's moving houses, and this is when you throw out the junk drawer instead of repacking it. Bring the customers who are real and the history that matters. Don't drag the rest into the new place just because it's already typed.
- 2
Clean the sheet so every field has its own column
This is the slow step, so settle in. Give every piece of information its own column: split a combined “John Smith” into first and last name, pull the vehicle out of the notes field, put one email and one phone per cell with no stray spaces or “n/a” filler. Standardize your phone numbers to one shape. The importer is smart, but it can't un-mash a cell where you crammed a name, a number and a plate together. Tidy in, tidy out.
- 3
Dedupe on a real unique key
Pick one field that should be unique per customer — normally a normalized email or phone — and sort by it so duplicate rows land next to each other. Merge or delete the copies now, in the sheet, where you can see them. You don't have to catch every last one by hand; the importer does a second pass and skips duplicates it recognizes. But the cleaner you start, the less it has to guess.
- 4
Save it as a CSV with a header row
Once the sheet is clean, export it to CSV — comma-separated values, the option is right there in your “Save As” or “Download” menu. Keep a clear header row at the top (Name, Email, Phone, Vehicle, and so on); that row is what the matcher reads. Then keep the original workbook untouched as your backup. Your spreadsheet has no undo button, so that saved copy is your undo if you ever want to redo anything.
- 5
Import and let the matcher map your columns
Drop the CSV into Service VIN's import wizard. The matcher recognizes dozens of common column names automatically — your Name, Email and Phone columns usually snap into place on their own. Anything it doesn't know, you map yourself with a dropdown, and it shows a live example value pulled straight from your file so you can confirm the “email” column is actually emails before you commit. No guessing.
- 6
Test a small batch first
Don't run three thousand rows on faith. Import a handful first, then open those records and check them: is the name split right, did the phone land in the phone field, is the vehicle attached to the right owner? A spreadsheet has no undo, but a re-import is safe here — already-imported customers get matched and skipped, so a test batch can't poison the full run. Confirm the small pile looks right, then send the whole file.
- 7
Read the validation report, then commit
Before it writes a single record, the importer dry-runs the file and hands you a validation report: which rows are ready, which are flagged, and which would be skipped — each one by row number, with the reason. A blank email here, a duplicate there, a row missing anything to reach the customer by. You fix them or accept them with your eyes open, then commit. No surprises discovered three weeks later.
Duplicates, and why a re-import can't hurt you
The question I'd be asking is “what if I map a column wrong and have to run the file again?” — because a bad re-import is exactly the nightmare that keeps people frozen on the sheet. So here's how the importer protects you from yourself.
Customers are matched by email or phone. Run a file twice and the second pass recognizes people who are already in and skips them — it doesn't stamp out a shadow copy of every contact. And every skip is reported, not silent, so you can watch the safety net do its job in the report.
The clever bit is what happens when a “duplicate” row isn't fully a duplicate. Say a returning customer's row carries a VIN your shop hasn't seen — a truck they picked up since your last update. The contact is skipped as already-known, but that new vehicle gets added to their existing record instead of being dropped or spawning a second customer. You get the update without the mess. That's the difference between a system that's afraid of your data and one that's built to absorb it.
A re-import is a two-minute do-over, not a disaster
Because duplicate-skipping makes re-runs safe, you don't have to nail the mapping on the first try. Fix a column, drop the file in again, and the rows that already imported simply skip. That's the entire point of the dry-run report: look before you leap, then leap again if you need to, without breaking anything. The spreadsheet had no undo. This one effectively does.
Turn the imported list into booked work
Here's the moment it stops being a data project and starts paying you back. The second the import finishes, that frozen grid is gone. In its place is a living book: every row is now a real customer record with vehicles, tags, notes and lead source attached — a record you can edit, quote off, book against and follow up on like any other.
So work it. Those cold leads you almost didn't bring over — the quotes that never closed, the one-time washes from two summers ago — wire them straight into win-back follow-up and let the system chase them while you're under a hood. Your real customers are due for reminders, maintenance, the next tier of protection. None of that was possible when they were rows in a file nobody scrolled to. All of it is one working list now.
And if you're a solo or mobile operator finally leaving the sheet behind, the same import gets you a real book on mobile detailing software you can run from the driveway, not a workbook you're scared to open on your phone. You can bring your list in and see the whole thing work on the free trial — no credit card — so the first real test is your own data, in your own shop, before you commit a dollar.
The spreadsheet did its job. It carried you this far, and it deserves a respectful retirement. But you've outgrown the grid, and your book deserves to be somewhere it can actually go to work for you. Clean it, map it, import it. Then quit scrolling to row 812 and let the software find the guy who wanted a full front.
Frequently asked questions
Can I import a spreadsheet directly, or do I need special software?
Directly. If your spreadsheet exports a CSV with a header row, Service VIN imports it. The column matcher recognizes dozens of common headers, and you map the rest with a dropdown, using live examples from your own file to confirm you got it right.
How do I stop duplicate contacts when I import?
Dedupe in the sheet first on a normalized email or phone, then let the importer do a second pass. It matches customers by email or phone and skips duplicates, and if a duplicate row carries a new vehicle it adds that vehicle to the existing customer instead of creating a second record.
How much of my spreadsheet do I need to clean up first?
It depends on how tidy the sheet already is, but plan for some cleanup: one field per column, one email and one phone per cell, consistent formatting, and dead leads removed. Cleaning is usually the slowest part of any migration, while the import itself is fast.
Can I test before importing everything?
Yes, and you should. Import a small batch first and check it, then run the full file. A spreadsheet has no undo, but Service VIN's dry-run report shows flagged and skipped rows before you commit, and re-importing is safe because already-imported records are skipped.
What happens to my data after it's imported?
Every row becomes a normal Service VIN customer with vehicles, tags, notes and lead source attached — records you can edit, quote, book and follow up on like any other. The imported book feeds the CRM directly, so cold leads can go straight into win-back follow-up.
Gabriel, who runs a working PPF and detailing shop in Canada
Runs a working PPF and detailing shop in Canada · builder of Service VIN
Gabriel runs a working PPF and detailing shop in Canada and built Service VIN. He got his start detailing and wrapping his own car, taught himself color PPF, and spent his day job in digital marketing and SEO before building the shop software he could never find. Six years in, he writes to help other owners get out of the bay and actually run their business.
Keep reading
The newsletter
Get the next one in your inbox
Pricing, quoting, hiring and margin — written from the bay and the books. We send new posts and nothing else.
Run your shop on Service VIN
Quote for margin, book without double-booking, and put your follow-up on autopilot. Try every feature free for 14 days — no credit card required.