Skip to content
Migration guide

From Excel to a CRM: the hard part isn't the data, it's the habit.

Excel isn't a bad tool — it's the wrong tool for tracking sales. This page covers when to make the move, how to prepare your data, and where migrations got stuck in our own projects.

When does Excel stop being enough?

A spreadsheet is fine for holding a customer list for a long time. The moment it stops being enough usually announces itself like this:

  • Three versions of the same file are in circulation. Whose copy is current has become a matter of debate.
  • Follow-up is nobody's job. “Who is going to call this customer?” has no answer in the file.
  • The history is gone. What was discussed and what price was quoted lives on somebody's phone or in their email.
  • Reports are assembled by hand. At month end, someone loses two days to pivot tables.
  • When an employee leaves, the customer leaves too. The relationship belongs to the person, not the company.

If a few of those sound familiar, the problem is no longer the file — it's the process.

Preparation

How to prepare your spreadsheet before the move

  1. 1

    1. Consolidate into one file

    Pull the scattered files into a single sheet. Decide now which version is authoritative — deciding during the migration is far more expensive.

  2. 2

    2. Fix the header row

    Give every column one clear heading: company, contact, phone, email, city, last contact, status. Merged cells and stacked header rows make migration harder.

  3. 3

    3. Deduplicate on phone and email

    We match duplicates on the phone number: if the same number shows up on two records, that is where the match is made. Unify the format — a mixed country code makes one number look like two records. We clean duplicates during the import too; we saw this in our own migration work.

  4. 4

    4. Flag the dead records

    Don't delete companies that closed or haven't been touched in years — flag them in a separate column. They move across as archive and stay out of the daily list.

  5. 5

    5. Decide what won't move

    Not every column needs an equivalent in the CRM. Fields nobody uses stay empty in the new system too and fill the screen with columns nobody completes — we saw this in our own migration work.

Where did migrations get stuck in our own projects?

There are three places where we have seen a migration get stuck in our own projects; all three were about the setup, not the software. This is our own observation, not a measured industry rate:

1. The system went in and nobody used it. The team stayed on Excel because the new system didn't make their work easier — it produced reports for the manager. The fix: configure it around the salesperson's daily flow.

2. Too many fields. “While we're at it, let's record everything” turns into a long list of mandatory fields. In the first week everyone started leaving them blank. The fix: start with few fields and add as the need appears.

3. The migration landed in the busiest month of the year. The team had no time to learn. The fix: pick an off-season date.

How it runs here

An Excel migration at Rapitek

  1. 1

    Discovery

    We open your file together. Which column goes where, and which piece of information becomes a field rather than a note — we work that out in 30 minutes.

  2. 2

    Import

    Records are imported, duplicates cleaned out and phone formats unified. You keep the original file; after the import we compare record counts, and anything missing is corrected and re-run.

  3. 3

    Configuration

    Your pipeline stages, fields and reports are set up around your process. Modules you won't use don't get switched on.

  4. 4

    Training and the first week

    We train the team and stay close through the first week. If the team doesn't move into the new system in that first week, sliding back to the old file gets easier — we saw this in our own projects.

FAQ

About the Excel migration

My spreadsheet is a mess — can it still be migrated?
Yes. A messy file is expected and it doesn't block the migration. We look at it together in the discovery call and decide there how much of the cleanup is yours and how much is ours.
Will we lose data?
You keep the original file and we never write over it. After the import we compare record counts; if anything is missing, it is corrected and re-run.
What if the team goes back to Excel?
It is a real risk and we'll say so plainly. A CRM that doesn't make a salesperson's day easier won't be used — we saw this in our own projects; what decides the outcome is not the software itself but the setup decisions. That is why we do the setup ourselves and stay close through the first week.
How many records can be migrated?
The import wizard has measured limits: 25 MB per file and 100,000 rows per job. Larger files are imported in parts, and after each part record counts are compared; if anything is missing, that part is corrected and re-run. We measure your file's size and structure together during discovery and build the import plan around it.
How long does the move take?
We don't commit to a timeline before discovery. After the discovery call we give you a date, not a range: once the file's structure, the columns to be migrated and the training plan are settled, you get the schedule in writing.

Let's look at your file together.

In a 30-minute call we'll open your spreadsheet and work out which column goes where. If it's still too early to move, we'll say that too.

30 minutes · No obligation · The call is held in Turkish

Made with RapitekGO

We would like to use optional cookies to measure your visit. The site works exactly the same if you decline. Cookie policy