- Company size alone does not tell you when to move. Re-keying, version conflicts and dependence on one person do.
- There are three routes: off-the-shelf, configured, and custom. Most owner-operated businesses belong in the first two.
- An implementation is mostly process and data work, not software work. Plan your own team's time accordingly.
- Data migration is where most projects go wrong. Clean the data before you move it, not after.
- We take no vendor commissions or referral fees, so our platform advice carries no hidden incentive.
Spreadsheets are a good tool. They are flexible, everyone knows how to use them, and they cost almost nothing to start. Most businesses we meet run on them far longer than anyone planned, and that is not a failure. It is a sign the business grew.
The question is not whether spreadsheets are bad. It is whether they are now the thing slowing you down. Around twenty people is where many owners first ask it, because that is roughly when one person can no longer hold the whole operation in their head. But the real answer comes from how work moves through your business, not from a headcount.
What an ERP and a CRM actually are
- ERP (enterprise resource planning)
- An ERP is a single system that records the core transactions of a business, such as orders, purchasing, inventory, billing and accounting, in one shared database so every department works from the same numbers.
- CRM (customer relationship management)
- A CRM is a system that records every interaction with customers and prospects, including enquiries, quotes, follow-ups and history, so the relationship does not live in one person's inbox.
The two often overlap. Many small-business platforms combine accounting, invoicing and a light CRM. Larger ERPs include CRM modules. What matters is not the label but the principle: each piece of information is entered once, in one place, and everyone who needs it can see it.
Spreadsheets break that principle by design. Each file is its own island. The moment the same customer, product or job lives in three files, someone has to keep them in sync by hand, and that someone is usually you or your most reliable employee.
Signs you have outgrown spreadsheets
Work through this checklist honestly. Each item is a symptom we see repeatedly in growing businesses. None of them alone means you need an ERP. Several together usually do.
- The same data is typed twice. An order is entered in a tracking sheet, then again in the invoicing tool, then again in the accounting software.
- Nobody is sure which file is current. Filenames end in “final”, “final v2” and “USE THIS ONE”.
- Month-end depends on one person. If that person is away, the close waits.
- Inventory counts never match the books. Stock on the shelf and stock in the sheet drift apart between counts.
- You cannot answer simple questions quickly. “What is our margin on this customer?” takes a day of copying and pasting.
- Formulas break silently. A row is inserted, a range is missed, and a total is wrong for months before anyone notices.
- Access control is all or nothing. Either someone can see the payroll tab or they cannot use the file at all.
- Approvals happen in email. Purchase approvals and price changes exist only as replies in someone's inbox.
- Customer history walks out the door. When a salesperson leaves, so does their knowledge of the accounts.
- Your accountant spends time fixing, not reviewing. Year-end starts with reconciling your spreadsheets to your books.
The clearest sign is not any single symptom. It is when the effort of keeping spreadsheets consistent starts to compete with the work the business actually exists to do.
If only one or two items apply, the better answer may be tidier spreadsheets, a small automation, or using features already in software you pay for. That is often what a business systems audit recommends before anyone mentions an ERP.
Off-the-shelf, configured or custom
Once you decide to move, there are three broad routes. The words get used loosely, so here is how we define them.
- Off-the-shelf
- Off-the-shelf software is used as the vendor ships it, with only basic settings changed. Your processes adapt to the software.
- Configured
- A configured system is an established platform set up with custom fields, workflows, forms, permissions and reports to fit how your business works, without changing the platform's underlying code.
- Custom
- A custom system is built specifically for your business, either from scratch or as a purpose-built layer on top of other tools. The software adapts entirely to your processes.
| Off-the-shelf | Configured | Custom | |
|---|---|---|---|
| Best fit | Standard processes, common industry | Mostly standard, with a few important differences | Genuinely unusual processes that are a competitive advantage |
| Upfront effort | Lowest | Moderate | Highest |
| Fit to your workflow | You adapt to it | Close fit on what matters | Exact fit |
| Ongoing maintenance | Vendor handles updates | Vendor updates; configuration needs occasional review | You own it, so you maintain it |
| Dependency risk | On the vendor | On the vendor and whoever configured it | On whoever built it |
| Exit difficulty | Usually straightforward export | Moderate; configuration does not travel | Depends on how it was built and documented |
Most owner-operated businesses belong in the first two columns. Custom is right when the way you work is the reason customers choose you, and no platform can represent it without contortion. It is wrong when the real problem is that nobody has written the process down.
What an implementation involves
Owners often picture an implementation as installing software. In practice the software is the smallest part. Here are the steps we work through, in order.
- Map current processesWe document how orders, purchasing, billing and reporting actually happen today, including the workarounds. This is the baseline everything else is measured against.
- Define requirementsWe separate must-haves from nice-to-haves and write them down. A short, honest list beats a long wish list.
- Shortlist and selectWe compare a small number of platforms against the requirements, with demonstrations using your real scenarios rather than vendor scripts.
- Design the future processWe decide how work will flow in the new system, who approves what, and which reports the business needs. This is where most of the value is created.
- Configure and buildWe set up fields, workflows, permissions, templates and integrations, and build anything custom the design calls for.
- Clean and migrate dataWe clean customer, supplier, product and opening-balance data, then load it and reconcile it to the old records.
- Test with real scenariosYour team runs real transactions end to end before go-live. Problems found here are far less costly than problems found after.
- Train and go liveWe train people on their own tasks, not on every menu, then switch over with a clear cut-off date for the old files.
- Adapt after launchWe review how the system is being used once it settles, fix friction points, and adjust as the business changes.
The duration depends on the number of processes involved, the state of your data, and how much of your team's time is available. We set out a timeline in the written proposal once we have seen the scope, rather than quoting a generic one.
Data migration: where projects go wrong
- Data migration
- Data migration is the process of extracting records from old systems, cleaning and reformatting them, loading them into the new system, and proving that what arrived matches what left.
A new system with bad data is worse than the old spreadsheet, because people now trust it. These are the risks we plan for on every project.
- Duplicates. The same customer entered three ways becomes three customers with split history.
- Inconsistent formats. Dates, phone numbers, units and product codes recorded differently across files.
- Orphaned records. Invoices pointing to customers or products that no longer exist in the clean list.
- Opening balances that do not tie. Receivables, payables and inventory in the new system must agree to the accounting records at the cut-off date.
- Lost history. Deciding too late which historical data to bring across, and in what level of detail.
- Hidden logic. Spreadsheet formulas that quietly applied a rule, such as a discount or a commission, that nobody remembered to rebuild.
- No reconciliation. Loading data without a sign-off that totals and counts match the source.
Clean the data before you move it. Every error carried into a new system is harder to find and more expensive to fix once it is there.
Because a CPA partner reviews opening balances, the accounting side of the migration ties back to your books, not just to the old spreadsheet.
Common mistakes to avoid
- Choosing the platform first. Selecting software before defining requirements means the demo decides your process.
- Recreating the spreadsheet. Rebuilding every old tab in the new system carries the old problems forward.
- Underestimating staff time. Your people know the exceptions. The project needs them for mapping, testing and training.
- Over-customizing. Each customization is something to maintain and test with every vendor update.
- Running two systems indefinitely. Without a firm cut-off, people keep the old spreadsheet “just in case” and double entry returns.
- Taking advice from someone paid by the vendor. Ask every adviser directly whether they receive commissions or referral fees.
How we approach the ERP question
We are neutral on platforms. We take no vendor commissions, referral fees or reseller margins. Our recommendation may be a well-known platform, a configured system, a custom build, or no new system at all. Sometimes the right answer is to clean up what you have.
The work is led by a partner who has built CRM and admin systems for operating businesses, with our CPA partner involved wherever the system touches the books. You can read how we scope and run these projects on our ERP and CRM services page.
If you are weighing the move and want an independent view, request a consultation.
Questions
Is there a company size at which we need an ERP?
No single size applies. A small business with inventory, multiple locations and complex billing may need one early, while a larger professional practice may run well on accounting software and a CRM. The signs in your processes matter more than headcount.
Can we keep using Excel for some things after moving?
Yes. Spreadsheets remain useful for analysis and one-off modelling. The goal is that transactions are recorded once in the system, and spreadsheets read from it rather than replace it.
Should we buy off-the-shelf software or build custom?
Start with off-the-shelf or configured options and move to custom only when your processes are genuinely unusual and central to how you win work. Custom gives an exact fit but makes you responsible for maintaining it.
How long does an ERP or CRM implementation take?
It depends on the number of processes involved, the condition of your data, and how much time your team can give the project. We set a timeline in the written proposal after scoping, rather than quoting a generic duration.
Do you receive commissions from software vendors?
No. We take no commissions, referral fees or reseller margins from any vendor, so our recommendation is based only on fit for your business.
This guide is general information for Ontario businesses, not advice for your situation. Rules change; talk to us before acting on it.