In this article
- When a spreadsheet stops being a sales system
- What two weeks actually covers
- Days 1 to 3: decide what moves
- Days 4 to 7: customer data cleanup
- Mapping Excel columns to CRM fields
- Days 8 to 10: import contacts, then verify
- Days 11 to 13: rebuild the pipeline and train the team
- Day 14: go live, and the mistakes that cost a week
- Frequently asked questions
- Where to start this week
Most small sales teams in Saudi Arabia start in a spreadsheet, and for a while it works. The trouble starts when three people edit the same file, the follow up column goes stale, and nobody can say what is really in the pipeline this month. An Excel to CRM move does not have to be a six month project. Two focused weeks are enough for a team of three to ten people, as long as you clean the data before you move it.
What follows is a day by day plan. It assumes one person owns the migration, your sheet holds a few hundred to a few thousand rows, and you want the team working in the new system by the end of week two.
When a spreadsheet stops being a sales system
A spreadsheet records what happened. A CRM helps you decide what to do next. That difference is why teams outgrow Excel long before the file gets big.
The warning signs are familiar. Two salespeople call the same lead in one week because each kept a private copy. A deal closes and nobody can find the quotation sent in March. The manager asks for a forecast and gets a number typed by hand instead of one calculated from stages.
There is a quieter cost too. In Excel nothing reminds you, so a lead that went quiet in week two stays quiet, and pipeline leaks stay invisible until the quarter ends.
Accuracy matters for compliance as well. If you issue tax invoices, buyer details have to be correct, and a sheet with three spellings of one company name is a slow problem. The ZATCA e-invoicing programme started Phase 1 on 4 December 2021 and Phase 2 on 1 January 2023, and clean customer records sit underneath all of it.
What two weeks actually covers
Set the scope before you start. Two weeks is enough to move customers, open deals and recent history into a CRM and have the team working there. It is not enough to redesign your sales process or connect four other systems.
| In scope for the first pass | Leave for month two |
|---|---|
| Customers, contacts and companies | Ten years of closed deals |
| Open deals and their stages | Automation rules |
| Notes from the last 6 to 12 months | Integrations beyond invoicing |
| Owner, next step and next date | A dashboard for every role |
| A pipeline the team agrees on | Importing old email threads |
Everything in the right column can wait. Teams that attempt both columns at once are the ones still migrating three months later.
Days 1 to 3: decide what moves
Make three decisions before you touch a cell. First, what counts as a customer and what counts as a lead. Pick a rule, for example a lead becomes a customer when the first invoice is issued, then apply it to every row.
Second, which rows are dead. A contact you have not spoken to in two years who never replied is noise, not data. Park those rows. Moving them gains nothing today and costs search time every day after.
Third, who owns each record. If the owner column is blank or says sales, assign a person by name. Unowned records teach a team that nobody is responsible.
Then copy the sheet, work on the copy, and keep the original untouched with the date in its name. Finally, write down the five questions you want the system to answer on day one: what is in the pipeline this month, which deals have had no contact for ten days, what did we last quote this customer, and what closed last month. Those questions decide which fields matter.
Days 4 to 7: customer data cleanup
This is the step teams skip and then regret. Customer data cleanup is the difference between a system people trust and a system people work around.
- Split combined columns. A cell holding a name, a city and a phone number together has to become three fields.
- Fix phone numbers. Choose one format, such as +966 5XX XXX XXX, and apply it everywhere. Phone and date formats cause most failed imports.
- Standardise dates. Use YYYY-MM-DD and Western digits. Mixed formats import silently as the wrong day.
- Remove duplicates. Sort by company, then phone, then email. One company written three ways is the most common duplicate in Saudi B2B lists.
- Check VAT numbers. A Saudi VAT registration number is 15 digits. Anything shorter, or with letters in it, needs a human to review it before it reaches an invoice.
- Trim text fields. Strip leading spaces, line breaks inside cells and stray quotation marks, because these break CSV files.
Set a rule for Arabic and English names. Decide whether the company field holds the Arabic legal name or the English trading name, and put the other one in a second field. Mixing both in one column makes search fail half the time.
When you finish, record the counts: rows in, rows parked, duplicates merged. That record is your evidence later, when a number in the CRM does not match somebody's memory.
Mapping Excel columns to CRM fields
Write the map before you import anything. One row per spreadsheet column, one target field, one note. An hour on paper saves two days of correction.
| Excel column | CRM field | Watch out for |
|---|---|---|
| Company | Customer name | One language per field, the other in an alternate name |
| Contact person | Contact name | Split into first and last if the CRM expects two |
| Mobile, phone, other no. | Phone | One primary number, one alternate, the rest in notes |
| One address per record | ||
| City | City | Standardise spellings before import |
| Status | Deal stage | Map loose words like hot or maybe to a real stage |
| Value | Deal value | Digits only, currency in its own field, SAR |
| Notes | Description | Strip line breaks, keep the last 6 to 12 months |
| Owner | Assigned user | Must match a real user account exactly |
| Next action | Next follow up date | One date format across the whole file |
If a column has no home, ask whether anyone used it in the past year. Usually nobody did. If it genuinely matters, create a custom field, but keep that list short.
Days 8 to 10: import contacts, then verify
Run the import in three passes rather than one.
Start with a test file of twenty rows chosen on purpose: a long Arabic company name, a contact with no email address, a row with two phone numbers, and a record you know is a duplicate. If those twenty land correctly, the rest almost certainly will.
Check that test by hand. Open five records and compare them to the sheet field by field, looking closely at Arabic text, dates and decimals.
Then import customers and contacts in full, and only afterwards import deals, so every deal has a customer to attach to. The wrong order creates orphan deals, and fixing those takes longer.
Verify with counts, not with a feeling. Rows in the clean sheet should equal records in the system plus the duplicates it merged, and the total open pipeline value should match the sheet. If the numbers differ, find out why before anyone starts working. One unreconciled import is how teams end up keeping the spreadsheet alive just to check.
Days 11 to 13: rebuild the pipeline and train the team
A CRM is only as good as its stages. Keep them few, and make each one mean something observable rather than a feeling. Five to seven stages suits most small teams.
A workable default for Saudi B2B is New lead, Qualified, Quotation sent, Negotiation, Won and Lost. Every stage needs an exit rule the whole team can repeat. Qualified means you have confirmed a need and a budget holder. Quotation sent means a document actually left the building.
Train in two short sessions rather than one long one. The first covers three things only: find a customer, log a call, move a deal. The second, two days later, covers quotations and reporting.
Put the ground rule in writing: if it is not in the system, it did not happen. Managers have to hold that line for the first fortnight. A CRM for small businesses in Saudi Arabia earns its place when it covers the handover too, so a won deal becomes a quotation, the quotation becomes an invoice, and the customer reaches the help desk with their history attached.
Day 14: go live, and the mistakes that cost a week
Going live is a decision, not a drift. Pick the date, announce it, and set the spreadsheet to read only that morning. Keep it accessible for sixty days, then archive it.
Run a fifteen minute check every day for the first week: every open deal has an owner, a stage and a next date.
- Importing before cleaning. Duplicates are far harder to remove inside a CRM than inside a sheet.
- Running both systems in parallel. Two sources of truth means none.
- Creating thirty custom fields on day one. Add a field when someone asks for it twice.
- Letting the manager stay in Excel. If the forecast is still built in a sheet, the team keeps feeding the sheet.
- No single owner. Shared responsibility means everybody waits.
Two weeks is realistic. Two weeks alongside a quarter end, a trade show and a system upgrade is not, so choose a quiet fortnight.
Frequently asked questions
How long does a migration really take?
For three to ten people and a few thousand rows, two weeks of part time work by one owner is realistic. The variable is data quality, not software. A sheet with merged cells and five years of blended notes can take a week on its own.
Should we import all of our history?
No. Import customers, open deals and roughly the last six to twelve months of activity, and keep the full sheet as an archive. You avoid filling a new system with records nobody opens.
What usually breaks during the import?
Phone numbers, dates and encoding. Save the file as CSV UTF-8 so Arabic text survives, use one date format, and keep numbers clear of currency symbols and thousand separators.
How do we stop the team going back to the spreadsheet?
Make the system the only source of the forecast, set the sheet to read only on go live day, and keep the daily checks running for the first week.
Where to start this week
A migration is mostly a data project with a short software step at the end. Clean first, map second, import third. If you are still choosing, our guide on how to choose the best CRM in Saudi Arabia covers the criteria that matter.
Ready to move off the sheet? Book a demo and we will look at your spreadsheet and the fields it maps to.
