We're Eskore, a digital and technology studio with offices in Toronto, Thornhill, London and New York. This is a plain-English guide to help you move from spreadsheets to a CRM: when the move makes sense, which of three paths fits, how to map and clean your data, how to cut over without a gap, and how to make sure leads stop waiting in someone's inbox. Most businesses don't decide to make this move. They drift into it, usually after a lead gets lost, a quote goes out twice, or a client asks for the same file for the third time.
We build custom CRM software and can also help configure off-the-shelf platforms. This guide is vendor-neutral because the right answer depends on how your team sells, not on which product we prefer. We work across software, design, cloud and marketing as one team, so the CRM, the website that feeds it and the hosting don't have to be handled by three suppliers.
Signs your spreadsheet has become the problem
The cost of a spreadsheet rarely shows up as a line item. It shows up as a deal that went quiet for three weeks because its owner was on leave, or a customer who received two different quotes because two people were working from two copies of the same file.
Watch for these symptoms:
- Nobody can say which deals are active without asking around.
- The owner column is half-filled, or the names are out of date.
- The history is missing: last contact, what was promised, what was sent.
- Next steps live in people's heads rather than in the file.
- Staff keep asking for the file to be resent.
- Follow-ups slip, and you only notice when the client chases you.
If several of these sound familiar, the problem is the process, not the people. Our guide to moving from spreadsheet workarounds to working software covers the wider pattern.
The goal is simple: never lose a lead in someone's inbox again. A spreadsheet can't enforce that. A well-set-up CRM can.
Lost follow-ups and the inbox problem
Leads usually disappear in three places. A website form lands in one person's inbox and nobody else sees it. A phone call gets answered, a promise is made, and nothing is written down. A quote sits in a shared drive under a name like final_v3_REAL.xlsx, and the person who needs it can't find it.
None of these is really a people problem. Each depends on someone remembering to copy information into the sheet. When the business gets busy, the copying stops first.
That's why the capture section later in this guide matters as much as the import. Moving existing data is the easy part. Making sure new leads arrive without manual copying is where most moves succeed or fail.
How to move from spreadsheets to a CRM: stay, configure or build
There are three realistic options: keep the spreadsheet, configure an off-the-shelf CRM, or build a custom one. None is right by default. Ask how standard your sales or operations process is, and how many other tools the new system has to work with.
When a spreadsheet is still the right tool
A well-kept spreadsheet is fine for many small teams. If you have a handful of clients, one or two people working in the file, a simple pipeline and no need for automated follow-up, a sheet with clear columns, one owner and a weekly review can do the job for years.
We don't decide this with a contact count or a deal count. Published thresholds vary widely, and they tend to ignore how the team actually works. Our test is practical: can the people who sell see what's active, who owns it, what happened last and what happens next, without asking anyone? If yes, the sheet may be enough.
Change is due when more than one person needs to act on the same record every day, when follow-ups have to happen without someone remembering, or when someone spends more time maintaining the file than selling. If those describe your team, you've passed the point where a spreadsheet is the cheapest option, even if it still looks free.
When to configure HubSpot, Zoho, Pipedrive or Salesforce
Configuring a platform such as HubSpot, Zoho, Pipedrive or Salesforce is the right call when your sales process is fairly standard. Leads come in, get qualified, move through stages, receive a quote, and then close or go cold. A mature platform covers most of that, along with integrations and a large base of people who have solved the same problems.
Configuration is not the same as installing. You still need a defined pipeline with agreed stage names and clear entry rules, a field plan that says what each record holds, and integrations that bring leads in. Teams that skip those steps end up with a tidy tool that is just as messy as the spreadsheet was.
Pricing, plan limits and seat rules change often and vary by region. Some platforms offer a free tier with limits, and those limits can be the deciding factor, so check them before you rely on one. Check each vendor's current pricing page directly before you budget. We don't quote subscription figures in this article.
When a custom CRM is the better fit
A custom CRM makes sense when your process doesn't look like the standard one. Picture a freight broker in Denver that quotes by lane, weight and carrier rules. Or a property management firm in Austin where tenants, owners and vendors each need a different view of the same building. Or a clinic in Raleigh that needs intake, referrals and billing tied to one patient record. In New York, a staffing firm might need candidate, client and placement records that don't fit a standard sales pipeline. In Thornhill, a renovation company might quote by room, material and crew availability. These are illustrations, not case studies, but the pattern is common.
A custom build also fits when quotes and client portals must match how the business works, or when several existing tools need joining so staff stop re-keying data. If clients need to log in to see quotes and invoices, our custom software development service covers that work. If the same problem runs through inventory, finance or HR, our ERP systems bring those processes into one system.
Custom doesn't have to mean starting from nothing. Often the best answer is a focused system built on a framework such as Laravel or Next.js, connected to the accounting and email tools you already use. For cost and build-versus-buy trade-offs, read our custom CRM development in Toronto guide. We won't repeat that analysis here.
If you're comparing partners, our guide to choosing a custom software developer for your small business in Toronto sets out what to ask.
Eskore's CRM development and setup work runs to a written scope, a fixed price and a launch date, all agreed before work starts. You own the code and the accounts.
Map every spreadsheet column before you import anything
Migration is a definitions exercise, not a data transfer. Most failed imports don't fail on the technical step. They fail because nobody agreed what "Status" meant, and the new system ends up with fourteen values that mean roughly the same thing.
Before importing, list every column in every tab. For each one, write a plain-English definition and decide where it goes. Here is an example for a sales tracker:
| Sheet column | What it means | Where it goes |
|---|---|---|
| Company | Organization the deal is with | Company record |
| Contact name | Person you speak to | Contact record, linked to company |
| Email / Phone | How to reach them | Standard contact fields |
| Status | Where the deal is | Pipeline stage (fixed values, not free text) |
| Owner | Who is responsible | Deal owner (a user) |
| Quote value | Amount quoted or expected | Deal amount |
| Lane / Service area | Route or service type | Custom field |
| Last contact | Date of last touch | Calculated from logged activity, not typed |
| Next step | What happens next | Task with a due date |
| Notes | Free-text history | Activity notes |
| Colour code | Visual marking | Drop |
Notice that "Last contact" becomes something the system calculates from logged activity. If you keep it as a typed field, it will go stale within a month.
In HubSpot, Zoho, Pipedrive and Salesforce, the import tool asks you to match each file column to a field, and it can create custom fields where nothing matches. The labels differ, but the logic is the same: decide the target, then map. Salesforce separates accounts, contacts and opportunities, so one sheet often has to be split across several imports. Companies need to come in before the contacts and deals linked to them.
Turn each column into a field, a stage or nothing
For each column, make one of three decisions. Use a standard field if the platform has one that means the same thing. Use a custom field if it holds real information you'll report on. Drop it if it's a leftover.
Status columns need the most attention. Free-text values such as "quoted", "Quoted - waiting" or "waiting on Dan" should become pipeline stages from a short, agreed list. Something like New, Qualified, Quoted, Waiting on client, Won and Lost works for many teams. Each stage needs a clear meaning. Anything more specific becomes a task or a note.
Watch for duplicated columns. Sheets collect them over the years: "Phone", "Phone 2", "Mobile", "Cell". Pick one standard field and move the rest into notes or drop them. Watch too for columns that look like data but are really reminders, such as "Call Friday". Those belong in tasks with due dates.
Clean the data before you move it
Plan a day or two for cleaning. It's tedious, and it's where much of the value comes from. Dirty data makes automations misfire, makes reports wrong, and teaches the team to distrust the new system in its first week.
Work through this checklist:
- Duplicates: Merge duplicate contacts and companies. Decide which record survives and combine the notes.
- Phone numbers: Use one format throughout, including country codes if your list mixes Canadian and US numbers.
- Dates: Pick one format. A date like 03/04/2026 is 3 April in one office and 4 March in another.
- Places: Use one form for province and state names (ON or Ontario, NY or New York) and one format for postal and ZIP codes. A Thornhill business with clients in Toronto and New York will have both in the same list.
- Currency: Use one currency per deal amount and check that totals reconcile.
- Critical fields: Every open deal needs a company, a contact, an owner and a stage. Flag anything missing.
- Departed owners: If someone has left, reassign their open deals before import, not after.
- Old history: Decide how much closed history to bring across. Old lost deals rarely justify the clutter.
Run a dated cutover, not a big-bang switch
Don't switch everything over on a Friday night. A dated cutover gives you a clear line between the old system and the new one, and a short window to compare them.
- Export each tab as CSV. In Google Sheets, go to File, then Download, then Comma Separated Values (.csv). In Excel, use Save As and choose CSV UTF-8. Leave the original file untouched.
- Agree a cutover date and write it down. From that date, new contacts and deals go into the CRM only.
- Run both systems in parallel for a short, fixed period. Use it to check the import and confirm the team is switching. Keep the window short, because long parallel running creates two sources of truth.
- Freeze the spreadsheet. Set it to read-only, for example by changing shared access to viewer, and rename it with the archive date. Keep it for reference.
- Enter new records only in the CRM from the cutover date onward.
How long this takes depends on the volume of data and how many people use the system. We agree the launch date in writing, alongside scope and price, before work starts, so the plan has a fixed end point.
Verify records after import
Check the data before you trust it. A sample of at least 20 random records is a sensible starting point, not a full audit. Compare each one with the original sheet and confirm:
- The contact is linked to the right company.
- The deal sits under the right contact, with the right amount and close date.
- The owner matches the sheet.
- The stage matches the old status value.
- Notes came across, or you know where the rest live.
Then check the totals: row count in the sheet against records in the CRM, and total open pipeline value in both. Have the owner sign off on the checklist before you count the migration as complete. If the sample turns up errors, find the pattern behind them and re-run the import. Fixing records one by one hides the cause.
Capture leads automatically from the first day
A CRM with clean data but manual entry will be out of date within a month. Every route into the business should land in the pipeline and be assigned without anyone copying it.
- Website forms: Send submissions straight to the CRM with a source tag, such as the page or campaign that produced the lead. Website forms are part of our web development work, so the form and the connection to the CRM can be scoped together.
- Email: Use a shared enquiries address, not one person's inbox. Connect it so each new message creates a deal or a task.
- Phone: Log calls where your phone system supports it. Twilio can send call events to your own systems, so an unanswered call can create a task or trigger a follow-up text.
- Accounting tools: When an invoice is paid or a quote accepted in QuickBooks or Xero, update the deal. That removes the "did they pay?" question from sales conversations.
- Connectors: Zapier and Make can join forms, spreadsheets and tools that don't talk to each other. They suit simple flows well. Once a flow has branching rules, high volume or sensitive data, a custom integration is often easier to maintain and monitor.
No integration removes the need to check it. Test every route with a real submission before go-live, and set up an alert for failed flows, so a broken form doesn't quietly drop leads for a week.
Follow-up, quoting and reporting that run themselves
Switch on a small number of automations at go-live, not all of them at once.
- Follow-up reminders: A task when a deal has been idle for a set period.
- Quote creation: Templated quotes built from the deal record, with line items drawn from a product list.
- Stage-change alerts: A notification to the owner when a deal is won, or when a high-value quote is waiting for a response.
- Weekly pipeline report: One page, sent to the same people each Monday, showing new, moved, stalled and won deals.
Each automation should answer a question someone actually asks. The trade-off is clutter. Too many notifications and people mute the channel, which is worse than having no alerts. Start with three, review them after a month, and add or remove as needed. If you want help designing the follow-up logic, see our follow-up automation service.
Get the team to adopt the new CRM
Adoption decides whether the move works. Three things help it stick.
First, train around real work. Run short sessions built on the three actions people perform every day: add a lead, move a deal, log a call. Skip the tour of every menu.
Second, agree one place to log activity. If calls are recorded in the CRM but notes live in email, the CRM is wrong from the start. Choose one place and make it the expectation.
Third, take the old sheet out of daily use. While the spreadsheet is still open on someone's desktop, people will keep updating it. Archive it on the cutover date.
Keep the first screens simple. If the new system feels like a more complicated spreadsheet in week one, people drift back to the sheet. Show the fields people need to act on, and hide the rest until someone asks for them. A CRM should make your sales team faster, not add data entry. If people are typing the same information twice, fix the process before you add more users.
Data ownership, access and privacy during the move
Settle ownership before you start. You should own the code, the accounts and the data. At Eskore, the client owns the code and the accounts, and that is written into the scope before work begins.
Set access and roles before the import, not after. Decide who can see every deal, who sees only their own, who can export data and who can delete it. Give each person the least access they need, and remove access promptly when someone leaves.
Privacy needs care. Customer records often contain personal information, and the rules on how you collect, store, use and send it can apply to your CRM. In Canada, that can include PIPEDA, which covers personal information handled in commercial activity, and CASL, which governs commercial electronic messages such as marketing and many follow-up emails. In the United States, most businesses don't fall under a single federal privacy law, but several states have their own rules, and which ones apply depends on your business and where your customers are.
A CRM can help you keep organized records and track consent, but the software doesn't make your business compliant on its own. We are not legal advisers. Ask a lawyer to confirm which rules apply to you, especially before you import marketing lists or send follow-up email from the new system. Share sample files with your development team only after removing sensitive personal information.
Next step: book a free CRM consultation
If you're ready to move from spreadsheets to a CRM, start with a scoping conversation, not a software purchase. Bring a copy of your spreadsheet with sensitive personal data removed, and we'll map it to a pipeline that updates itself. We'll also tell you honestly whether a spreadsheet, a configured platform or a custom build fits your process. Anything we agree is written down, with a fixed price and launch date, before work starts. For how fixed pricing handles changes once work is underway, see our fixed price custom software development guide.
Book a free 30-minute scoping call and we'll take it from there.