In short: an Excel CRM is enough for an SME with a single salesperson, a few hundred contacts and a handful of follow-ups. It breaks at five specific points: several sales reps working in the same file, follow-ups that get lost, access that cannot be restricted, a file that travels by email, and no record of who changed what. If two of these signs apply to you, start preparing the migration now.
An Excel CRM is where most small businesses start. One column for the name, one for the phone number, one for the last conversation, and a filter to find the hot leads. The file costs nothing beyond the Microsoft licence you already pay for, and everyone knows how to use it.
Excel is not the problem. The problem starts when the spreadsheet becomes the company's sales memory without the safeguards that role requires. This guide does not argue for dropping your file tomorrow. It describes what Excel handles well, the five signs that a breaking point is near, what the revised Federal Act on Data Protection (FADP) requires of a customer file, and how to move to a CRM without losing your history. For the criteria for choosing the tool itself, see our grid for choosing a CRM as a Swiss SME.
Excel as a CRM: who is it really enough for?
Excel works as a CRM when one person maintains the file, contacts number in the hundreds, the sales cycle is short and follow-ups fit in a calendar. A freelancer, a tradesperson or a small fiduciary firm with one sales partner can work this way for years without any real loss.
Raw capacity is never the issue: Microsoft states that a worksheet holds up to 1,048,576 rows and 16,384 columns. The limits come from how the file is used: how many people write to it, how many actions need tracking over time, and the obligations attached to personal data.
| Need | Where Excel does well | Where Excel struggles |
|---|---|---|
| Contact list | Sorting, filtering, quick search | Duplicates as soon as two people enter data |
| Deal tracking | A "status" column for one salesperson | Shared pipeline, stages, weighted amounts |
| Follow-ups | Filterable next-action date | No automatic reminders, nothing alerts you |
| Access | Password-protected file | No rights per row or per customer |
| History | Free-text notes in a cell | No record of who changed what, or when |
| Sharing | Email attachment, shared folder | Competing versions, uncontrolled copies |
What are the 5 signs that your spreadsheet can no longer cope?
Five signs show that an Excel CRM has reached its limit: several sales reps write to the same file, follow-ups are forgotten, you cannot limit who sees what, the file travels by email or USB stick, and nobody knows who changed a record. One sign is manageable; two or more are already costing you deals.
1. Two or more sales reps on the same file
Co-editing exists, but with conditions. According to Microsoft's documentation on co-authoring, you need a Microsoft 365 subscription, AutoSave turned on and a workbook stored on OneDrive or SharePoint Online; on-premises SharePoint does not support it. Without these conditions, everyone works on their own copy and merging is done by hand. With them, your customer file is hosted in Microsoft's cloud, and it is up to you to check in which region, as explained in our comparison of hosting in Switzerland or in Europe.
2. Follow-ups that slip through the cracks
A spreadsheet warns you about nothing. The "next action" column is only useful if someone filters the file every morning. Once the volume exceeds what you can keep in your head, quotes sent without a follow-up pile up. A CRM reverses the logic: the task comes to you, with the date, the contact and the history of the conversation.
3. No way to restrict access
Whoever opens the workbook sees everything: every customer, every amount, every note. Hiding a sheet changes nothing, and Microsoft says so itself: worksheet protection is not intended as a security feature. The day an intern, a business introducer or a new salesperson needs to see only part of the portfolio, Excel has no answer.
4. A file that travels
"I'll send you the latest version" is the sentence that marks the end of the Excel CRM. Every attachment creates a full copy of your customer base, in a mailbox, on a personal computer or on a phone. You no longer know how many copies exist, or which one is authoritative.
5. No record of who changed what
An amount changes, an address disappears, a customer is marked "lost": in a spreadsheet, nobody can say who did it or when. That is a sales problem, and it is also where the file runs into the FADP.
Is an Excel customer file compatible with the FADP?
The FADP does not ban Excel. It imposes obligations that a spreadsheet makes hard to meet: data must be accurate, deleted when no longer needed, protected by limited access, and any access request must be answered within 30 days. With a customer base scattered across several copies, each of these obligations becomes manual work.
Let's take the requirements one by one. Art. 6 FADP requires data to be accurate and to be destroyed or anonymised as soon as it is no longer needed. Deleting an old lead from the main file does not delete it from the five copies sent by email. Art. 25 FADP gives everyone the right to know what data you hold about them, and Art. 18 of the Data Protection Ordinance (DPO) sets the response deadline at 30 days. Finding every mention of a person across several versions of a spreadsheet takes time.
On the security side, Art. 3 DPO lists measures that mirror the weaknesses of Excel point for point: giving authorised persons access only to the data they need for their tasks, preventing data from being read or copied when it is disclosed, and being able to check which data was entered or changed, by whom and when. The text calls for measures "appropriate" to the risk: a five-person SME does not have the obligations of a bank, but it must be able to show what it has put in place.
Good news for small businesses: under Art. 24 DPO, a company with fewer than 250 employees does not have to keep a record of processing activities, unless it processes sensitive data on a large scale or carries out high-risk profiling. All other obligations apply regardless of size. For details on penalties, including the fine of up to CHF 250,000 under Art. 61 FADP for intentionally failing to meet the minimum data security requirements, read our article on management liability under the FADP.
Why is emailing your customer file a risk?
A customer file sent by email duplicates your entire base in mailboxes you do not control. And email is the most common entry point for attacks: according to Deloitte, phishing is the cyber threat most often reported by employees of Swiss SMEs. A compromised mailbox then hands over your whole portfolio.
The figures from the Deloitte survey published on 20 August 2026 give a sense of scale. Of 924 employees of Swiss companies with fewer than 250 staff surveyed in April 2026, 49% report a serious cyber incident at their employer in the previous three months, and 38% in micro-enterprises with 1 to 9 people. Phishing comes top, cited by 25% of respondents. Only 66% of companies use multi-factor authentication.
For an Excel file, the scenario is simple: an employee clicks a fake link, the attacker reads their mailbox and retrieves the attachment "clients_2026_v7.xlsx". If this is likely to result in a high risk for the people concerned, Art. 24 FADP requires you to report it to the Federal Data Protection and Information Commissioner (FDPIC) as soon as possible. A CRM does not eliminate the risk of phishing, but it replaces copies with named user accounts that can be revoked as soon as an employee leaves the company.
When and how should you move from Excel to a CRM?
Move from Excel to a CRM as soon as two of the five signs are present, or before a second salesperson joins. Migrating a small customer base takes a few days: clean up the file, choose the fields, test the import on a sample, switch over on a fixed date, then delete the old copies.
- 1
Gather and deduplicate
240 minCollect every version of the file (mailboxes, computers, USB sticks), merge them into a single source and remove duplicates. Take the opportunity to delete contacts you no longer need, as Art. 6 FADP requires.
- 2
Structure the columns
180 minSplit street, house number, postcode and town into separate columns, and standardise sales statuses and date formats. A structured address will also be useful for the QR-bill.
- 3
Test an import of 50 rows
120 minImport a real sample into the CRM you have chosen, check that each field lands in the right place, then test the export in the other direction. A tool you cannot get your data back out of is a poor starting point.
- 4
Switch over on a fixed date
300 minImport the full base on a Friday, give each user a named account with rights limited to their own customers if needed, and set the Excel file to read-only.
- 5
Delete the old copies
120 minAfter two to four weeks with no rollback, archive a final version somewhere safe and delete the copies in circulation. Record the date and the measures taken: this is your proof of due diligence.
Two points to watch. First, do not import the mess: a CRM full of duplicates loses the team's trust within a week. Second, check where the new tool hosts your data and which subcontractors it uses; our guide to the FADP and CRMs for Swiss SMEs lists the questions to ask. As for addresses, our article on the QR-bill after 30 September 2026 explains why structured fields become essential by that deadline.
FAQ: Excel as a CRM and moving to a real CRM
Can a small business use Excel as a CRM?
Yes, as long as one person maintains the file and follow-ups remain few. Excel easily handles a few thousand contacts. It becomes a constraint when several people write to it, when access needs to be restricted or when you need to trace who changed a record.
Is an Excel customer file illegal under the FADP?
No. The FADP does not require any particular software. It requires data to be accurate, deleted when no longer needed, protected by measures appropriate to the risk, and access requests to be answered within 30 days. It is the scattering of copies that makes these obligations hard to meet in a spreadsheet.
Is password-protecting the Excel file enough?
It protects the file against unauthorised opening, not against copying by those who have access. Microsoft states that worksheet protection is not a security feature. A password creates neither differentiated rights per user nor a change history.
Does an SME need to keep a record of processing activities for its customer file?
In principle no, if it has fewer than 250 employees. Art. 24 DPO exempts it, except where it processes sensitive data on a large scale or carries out high-risk profiling. The other obligations, namely security, accuracy and the right of access, still apply.
How long does migrating from Excel to a CRM take?
For a base of a few hundred to a few thousand contacts, allow two to three days of actual work, spread over one to two weeks. Cleaning up the file often takes longer than the import itself.
Why does leaving the spreadsheet pay off in sales and trust?
Three key takeaways. Excel remains a good starting tool for a lone salesperson. As soon as two of the five signs appear, the hidden cost shows up in forgotten follow-ups and copies in circulation. And the FADP does not ask you to change tools, but to be able to prove where your data is, who accesses it and what has changed.
That proof becomes a selling point with your customers: a fiduciary firm, a property management agency or a professional practice that can say "your data is in a single tool, hosted in Switzerland, with named user access" is more reassuring than a file sent as an attachment. That is the approach of Helvee, a CRM hosted in Switzerland. Compare it using our CRM selection grid, then contact us to talk about your current customer file.
