A sales rep resigns on a Friday. On Monday, his manager opens the shared spreadsheet and finds 40 clients marked "in talks", with no date for the last contact and no record of what was quoted. The emails sit in a mailbox nobody checks anymore. That same week, two of those clients call asking about a proposal no one can find.
Most companies start out with an Excel spreadsheet and whatever the team remembers. It works until the information starts living in people's heads and inboxes. A customer management CRM fixes that, as long as the move is done in order: what to record, how to build the pipeline, how to connect email and how to migrate without losing the history you already have.
If you're still comparing tools, we covered selection criteria in Enterprise CRM software: how to choose one people actually use. This article is about the next step: getting off the spreadsheet.
Signs the spreadsheet has run its course
A spreadsheet doesn't stop working overnight. It slowly falls short, and these are the usual signs:
- To know where a client stands, you have to ask the rep, because the spreadsheet is out of date.
- There are several versions of the file ("clients_final_v3_JP.xlsx") and nobody knows which one is right.
- The weekly sales report is put together by hand and takes hours.
- When someone leaves the company, the context on their accounts leaves with them.
- You can't answer simple questions, like how many opportunities have gone 30 days without movement or how much was closed per channel.
- Client emails are scattered across personal mailboxes and nobody else can see them.
If two or three of these sound familiar, staying on Excel already costs more than fixing the process.
What data to record (and what to skip)
The most common mistake when moving to a CRM is trying to record everything. Every required field that never shows up in a report is one more reason for the team not to update the system. Start with the minimum you need to manage the relationship and measure the process:
| Entity | Essential data | What it's for |
|---|---|---|
| Account (company) | Legal name, tax ID, industry, size, account owner | Knowing who the client is and who handles them |
| Contact | Name, job title, email, phone, linked account | Knowing who you talk to at each company |
| Opportunity | Product or service, estimated amount, stage, estimated close date, source | Building the pipeline and forecasting sales |
| Activity | Type (meeting, call, email), date, summary, next step | Keeping the history of the relationship |
| Loss reason | Price, timing, competitor, no budget, other | Understanding why deals don't close |
In B2B customer management, splitting accounts from contacts is the change people notice most. A spreadsheet usually has one row per person, so when the purchasing manager moves to another company, the account seems to vanish with him. In a CRM the company stays, with its history.
Leave out the "just in case" fields at first, like birthdays or hobbies. They clutter the system, and they're personal data you'd later have to justify holding.
The pipeline: stages with exit criteria
A pipeline is the list of open opportunities sorted by stage. For it to be useful, each stage needs an exit criterion you can verify, not the rep's gut feeling. Here's an example for a CRM for B2B sales teams:
- Qualification: need, budget and a decision maker have been confirmed.
- Discovery: there has been at least one discovery meeting and the specific problem is understood.
- Proposal: a formal proposal with amount and timeline has been sent.
- Negotiation: the client has responded to the proposal and terms are being adjusted.
- Close: won (purchase order or signed contract) or lost (with a recorded reason).
With stages like these, Monday's report builds itself: how many opportunities sit in each stage, what they add up to, which ones are stuck and how long they take to go from proposal to close. With a spreadsheet, hardly anyone can measure even two of those four without spending an afternoon cross-checking data.
Something that looks minor but isn't: review the pipeline in the weekly sales meeting straight from the CRM. If the meeting still runs off the spreadsheet, the CRM turns into paperwork.
Connecting email so reps actually log their work
Much of a client relationship happens over email and in meetings. If reps have to copy and paste every email into the CRM, they won't, and two months later the system holds half the story. Of everything you configure, this has the biggest effect on whether the team uses it.
In Dynamics 365 Sales, this is handled by Dynamics 365 App for Outlook, which lets users link emails and appointments to an account, contact or opportunity without leaving Outlook. According to Microsoft's documentation, the app requires server-side synchronization to be set up correctly on each user's Exchange mailbox. Without it, users can still look up CRM information but can't track emails and appointments. Synchronization runs in the background, so a newly linked email can take a few minutes to show up.
A note for the project plan: mailbox setup is done by an administrator, not by the user. Have it ready and tested before training the team, so they can log emails from Outlook on day one.
How to migrate from Excel without losing history
Migration is where these projects fall behind most often, and the cause is almost always messy source data. This is the order of work that has given us the best results:
1. Clean up before migrating
Remove duplicates, standardize tax ID and phone formats, and split out whatever is crammed into a single cell ("Juan Pérez - Manager - Company X").
2. Decide which history is worth keeping
Active clients and open opportunities, yes. Contacts with no interaction in years, probably not.
3. Use the system's template
Dynamics 365 lets you import data from Excel or CSV with a wizard that maps columns. Microsoft recommends starting from the template the app provides and not changing its columns. The wizard accepts .xlsx, .csv and XML Spreadsheet 2003 files, up to 8 MB per file (32 MB for .zip), so a large database has to be split into several batches.
4. Import in the right order
Accounts first, then contacts (linked to their account), then opportunities and finally activities. Lookup fields, like a contact's account, are mapped in the wizard so the relationships are kept.
5. Avoid duplicates
The wizard lets you choose whether to allow duplicates, and for CSV files you can set an alternate key (the tax ID, for example) to identify and update existing records instead of creating new ones.
6. Test with a small batch
Import 50 records, check that dates, amounts and relationships came through correctly, and only then load the rest. If you need to keep the original date a client or opportunity was created, check how it gets stored during that test.
If clients come from the ERP and will keep syncing, a manual import isn't enough and you'll want a permanent integration. We wrote about that in when automating with Power Platform is worth it.
Client data and Chile's Law 21.719
A spreadsheet with people's names, emails and phone numbers is a personal database, even if nobody calls it that. Law 21.719 requires you to know what data you process, for what purpose and who has access to it. It is set to take effect on December 1, 2026. As of October 2026 there is a bill in Congress proposing to postpone it, but until it is passed and published, that date stands.
A CRM with properly configured roles and permissions helps: each rep sees their own accounts, access is logged and copies of the file stop circulating by email.
Frequently asked questions
When should you move from Excel to a customer management CRM?
When knowing a client's status means asking each rep, when the sales report is built by hand, or when context gets lost every time someone leaves.
Can email history be migrated into the CRM?
New emails are linked from Outlook. For older history, the practical option is to migrate a summary of activities for active clients, not the whole mailbox.
How long does it take to move from the spreadsheet to a CRM?
It depends on the volume and condition of the data. A first team with the essentials and email connected can be up and running in weeks; data cleanup usually takes longer than configuration.
From a shared file to a process you can measure
Buying the software is the easy part. The hard part is agreeing on what gets recorded, when an opportunity moves to the next stage and where each client's history lives. Once that's settled, setting up the tool goes quickly.
At Disrupsoft we implement Dynamics 365 in stages: a review of your sales process, modular configuration, integration with Outlook, Teams and your other systems, and training with ongoing support. If you want to look at how to move your customer management from Excel to a CRM, let's talk through our Dynamics 365 service.
