Small Business
Small business: drop the spreadsheet as the CRM
A sheet can start you off. It cannot own follow-up, history or who did what last. Move the live work, then stop feeding both systems.
6 min read
Spreadsheets are honest on day one and messy by month three. Columns multiply, colours mean different things, and nobody knows which row is true. Two people edit two copies. A third person is still on last month's email attachment.
You do not need to pretend the sheet never helped. You do need to stop using it as the place live work lives, once more than one person has to follow up.
You do not need to pretend the sheet never helped. It did. It also cannot remind you, cannot show the last email, and cannot stop two people editing different copies.
The move is not a perfect migration. It is moving live work, then stopping the dual run before the familiar file wins again.
If you are still updating the sheet 'as well', the sheet will win. Dual running is not a transition. It is a decision to keep the old list.
What the sheet cannot do
It will not remind you. It will not show the last email. It will not stop two people editing different copies. It will not attach a quote, a booking and an invoice to the same row in a way the next person can trust.
Colour codes feel like a system. They are a private language. When the person who invented 'orange means maybe' is on leave, orange means nothing.
Move the live work first
You do not need a perfect migration. Move open leads and current customers. Old rows can wait. The mistake is trying to import 4,000 stale lines before tomorrow's callbacks, then drowning and going back to the sheet.
Live work is anything with a next step. If it has no next step and you have not spoken in a year, it is archive, not a reason to delay.
- ✓Open enquiries
- ✓Customers you still serve
- ✓Anything with a next step this month
“We kept 'just updating the sheet as well' for months. Of course the sheet won. It was the thing people already opened. We only broke the habit when we deleted the live tab and left a read-only archive. Uncomfortable for a week. Then the CRM was the list.”
Stop feeding both
Running the sheet and the CRM together guarantees the sheet wins until you delete it. People will update the familiar file under pressure. The CRM will look empty, so they will trust it less, so they will use the sheet more.
Pick a day. After that, live follow-up only happens in the CRM. The spreadsheet becomes the archive. Not a second pipeline.
What 'good enough' looks like in week one
Every open enquiry is a lead with an owner. Every current customer is searchable. This week's follow-ups have dates. You can live without historic jobs from 2019 sitting in the new system on day one.
That is a successful move. Polish can come later. Dual running cannot.
Pick one list
The CRM is the list. The spreadsheet is the archive. If you need a report the CRM cannot do yet, export once for that report. Do not start maintaining the export.
Why colour codes feel like a system
Orange means maybe. Green means hot. Blue means the person who invented the colours is on leave. Colour codes are a private language. They look organised and they do not travel.
Columns multiply for the same reason lists do. Nobody wants to delete. Then nobody knows which row is true.
Two copies is the real failure. A third person is still on last month's email attachment. The sheet cannot stop that. A CRM cannot stop it either if you keep feeding both.
Move live work, leave the museum
Live work is anything with a next step. Open enquiries. Customers you still serve. Anything you will touch this month. Old rows from 2019 can wait.
The mistake is importing 4,000 stale lines before tomorrow's callbacks, then drowning and going back to the sheet.
If a row has no next step and you have not spoken in a year, it is archive, not a reason to delay.
- ✓Open enquiries become leads with owners
- ✓Current customers become searchable records
- ✓This week's follow-ups get dates
- ✓Historic jobs wait until they matter
Pick a day, then stop feeding both
Running the sheet and the CRM together guarantees the sheet wins until you delete the live tab. People will update the familiar file under pressure. The CRM will look empty, so they will trust it less, so they will use the sheet more.
Pick a day. After that, live follow-up only happens in the CRM. Leave a read-only archive if you need comfort. Do not leave a live tab.
Uncomfortable for a week. Then the CRM is the list, because it is the only list that still moves.
What good enough looks like in week one
Every open enquiry is a lead with an owner. Every current customer is searchable. This week's follow-ups have dates. You can live without historic jobs sitting in the new system on day one.
That is a successful move. Polish can come later. Dual running cannot.
If you need a report the CRM cannot do yet, export once for that report. Do not start maintaining the export as a second pipeline.
Delete the live tab
A read-only archive is comfort. A live tab is a rival. People open what they already know when they are under pressure.
Pick a day. After that, the CRM is the only place a next step can live. Uncomfortable for a week. Then the new list is the list.
Do not migrate the museum first
Old rows feel important because they are numerous. They are not this week's work. Move open enquiries and current customers. Let 2019 wait.
A perfect historic import is how teams drown and go back to the sheet. Live work first is how they stay.
Foxtra is for teams that have outgrown the sheet but do not want an enterprise project to replace it. Move what is live, stop dual running, and let old rows wait until they actually matter.
Move what is live, stop dual running, and let old rows wait until they actually matter. The spreadsheet becomes the archive. Not a second pipeline.
Foxtra is for teams that have outgrown the sheet but do not want an enterprise project to replace it. Pick one list. The CRM is the list.
The sheet can stay as an archive. It cannot stay as the place live follow-up happens. Pick one list and stop feeding the other.