From spreadsheets to a CRM, step by step.
Most CRMs start life as a spreadsheet that got too big for one person. Moving off it is mostly tidying and deciding, not technology. Here are the steps in the order I would take them.
- Most of the work is in the spreadsheet: one row per person, one meaning per column, duplicates merged.
- Decide your pipeline stages and who owns each lead before you touch any software.
- Capture new enquiries at the source, so nothing depends on someone typing it into a sheet.
- Test the import on a copy, count the rows, then stop editing the old sheet on a set day.
- In the quote builder a move from spreadsheets is about 10–25 hours of work.
Step 1: be sure you have outgrown the sheet
A spreadsheet is a perfectly good CRM for one or two people with a short list. The signs that it is time to move are practical: two people edit it at once and overwrite each other, nobody can say who replied to which enquiry, follow-ups depend on memory, and you keep a second tab to work out what the first one means.
If that is not you yet, stay put. The spreadsheets versus a system comparison goes through what each does well. If it is you, the next steps apply whether you move to a custom CRM or an off-the-shelf one.
Step 2: clean the sheet before you move it
Software does not fix messy data, it just stores it faster. Do this in the spreadsheet, where it is easy to see:
- One row per person or company, not one row per conversation.
- One meaning per column. If “Notes” holds phone numbers, statuses and reminders, split it.
- One format per column: dates written the same way, phone numbers with the country code, names split into first and last where you need that.
- Find the duplicates (the same email, the same phone number, the same company spelled two ways) and decide which row wins.
- Mark the rows you will never contact again. Move them to a separate tab rather than deleting them.
Step 3: decide the pipeline and the owners
Write down the stages a lead moves through in your business, in plain words. Often that is something like new enquiry, quoted, waiting, won, lost, but yours might have a site visit or a deposit in the middle. Then decide who owns a lead at each stage.
This is the part that makes a CRM yours rather than a template. A custom system is shaped around these stages, and an off-the-shelf one makes you bend to its defaults. Either way, the answers come from you.
Step 4: map columns to fields
Make a two-column list: each column in the sheet on the left, the field in the new system on the right. Some will map one to one. Some will split, such as a full name into two fields. Some will have nowhere to go, and you decide whether they matter or can be archived.
Also decide where history lives. A client’s past quotes, emails and files may sit in several places. Decide what comes across and what stays in the old folders, and write it down so nobody is surprised later.
Step 5: capture new enquiries at the source
Moving old data is a one-off. The lasting fix is that new enquiries land in the CRM by themselves: the website form, WhatsApp and email, rather than being copied across by hand. In the quote builder that is a few hours each, for example 4–8 for a website form and 6–12 for WhatsApp.
It matters more than it sounds. The old form on the concreting contractor’s site had been silently dropping leads. The fix was lead capture that stores every enquiry, emails the owner and gives it a reference,
Step 6: test the import, then switch over
Import a copy first. Count the rows in the sheet and the records in the new system and check that the two numbers agree. Open ten records at random and compare every field. Then fix the mapping and import again. The data migration checklist goes into the detail.
On a chosen day, make the old sheet read-only. Run both for a very short overlap if you must, but a CRM that shares its job with a live spreadsheet quietly turns back into a spreadsheet. Storex began as a client and invoice tracker synced with Wix and grew from there, which is a good pattern: move one clean thing first, then add.
What it costs in hours
In my quote builder a move from spreadsheets is about 10–25 hours, and cleaning up duplicates as a CRM feature adds 4–10. Moving from another system is 25–60. The custom CRM cost guide shows how that sits inside a whole project, and the quote builder lets you pick spreadsheets as your starting point and see the effect.
Questions, answered.
Can I import a spreadsheet into an off-the-shelf CRM myself?
Often yes, if the CRM accepts a CSV file. The cleaning and mapping steps above matter just as much there. A custom build helps when the data needs reshaping or the CRM must connect to other tools.
What if my spreadsheet has years of mess in it?
Clean the active clients first and archive the rest on a separate tab. You rarely need all of the old data live on day one.
How do I stop people going back to the spreadsheet?
Make it read-only on a set day, and make the new system faster for the common tasks than the sheet was. If adding a lead is slower than typing a row, people will drift back.
Will WhatsApp conversations come across?
Past chats do not usually move across. What you can do is file new WhatsApp messages against the right client from the switch-over day, and bring key facts from old chats into notes.
How long does the whole move take?
The import itself is usually a small part of a project, around 10–25 build hours from a spreadsheet. The tidying and the pipeline decisions take as long as you take to make them.
Read next, then decide.
Enquiries, clients, pipeline and follow-ups in one place, shaped to how you sell.
ComparisonSpreadsheets vs a systemWhen Excel or Google Sheets is enough, and the signs it’s time for a system.
GuideData migration checklistA checklist for moving data to a new system: mapping, cleaning, duplicates, test imports and cut-over.
GuideWhat a custom CRM costsA custom CRM explained in build hours and weeks, with three worked examples.
PageGet a quoteSix short steps. You see the scope as you go, and get a fixed quote back.
Case studyNathan Fenech ConcretingFrom a one-page Malta site to a brand, website and quote-to-cash portal for a concreting business now serving Melbourne.
Case studyStorexA storage and logistics company’s whole operation in one custom system: quotes, clients, invoicing, the warehouse and the crew in the field.
PageGuidesCosts, timelines, briefs, migration, VAT invoices and the SME grant, explained.