Moving to a new CRM is exciting until you reach the data. Years of customer records live in spreadsheets, an old CRM, email contacts and accounting software — and all of it needs to arrive in the new system complete, correct and without duplicates. A rushed migration is the most common reason a new CRM loses the team’s trust in its first week.
The good news is that a careful migration follows a predictable plan. These are the steps we use when moving clients into vTiger CRM, SuiteCRM and other systems.
Step 1: Take an inventory of your data
List every place customer information lives today: the old CRM, shared spreadsheets, individual salespeople’s files, the email platform, the accounting system. For each source, note roughly how many records it holds, who maintains it and how up to date it is.
This often reveals surprises — a second customer list nobody mentioned, or a spreadsheet that is more current than the old CRM. It is far better to find these now than after go-live.
Step 2: Decide what not to migrate
Not everything deserves a place in the new system. Leads that went cold years ago, contacts with no email or phone number, and test records just add clutter. Agree on rules, for example:
- Migrate all customers and any contact active in the last three years.
- Archive older leads to a file rather than importing them.
- Keep historical invoices in the accounting system, and link to them rather than copying them.
A smaller, cleaner dataset is easier to import and easier for your team to trust.
Step 3: Clean the data before importing
Cleaning is easier in a spreadsheet than inside a live CRM. Typical tasks include:
- Removing duplicates — the same company spelled several ways, or the same person entered twice.
- Standardising values — country names, phone number formats, states and cities.
- Splitting combined fields — for example, “Full name” into first and last name, which most CRMs keep separately.
- Fixing obvious errors — invalid email addresses, missing company names, notes typed into the wrong column.
Step 4: Map every field
Create a simple mapping document: for every column in the source data, which field it goes to in the new CRM, and in which format. Pay particular attention to:
- Picklists. If the new CRM has fixed values for lead status or industry, translate the old values to the new ones explicitly.
- Record owners. Each record should be assigned to a real user in the new system. Create the users first.
- Required fields. Find out which fields the new CRM insists on and make sure every record has them.
- Custom fields. Create any custom fields in the new CRM before importing, so data has somewhere to go.
Step 5: Import in the right order
CRM records are linked to each other, so order matters. Import the records that others depend on first:
- Users and teams
- Organisations (accounts)
- Contacts, linked to their organisations
- Leads
- Opportunities / deals, linked to organisations and contacts
- Activities, notes and documents
Keep each source record’s original ID in a custom field. It makes linking related records reliable and lets you trace any record back to where it came from.
Step 6: Do a trial run
Import a sample — a few hundred records from each type — into a test copy of the CRM. Then check it carefully with the people who will use it:
- Are contacts linked to the right organisations?
- Do picklist values, dates and currencies look correct?
- Do the main reports and dashboards show sensible numbers?
- Can a salesperson find their own customers and understand their history?
Fix the mapping or the source data, then repeat until the sample is right. Built-in import tools in vTiger and SuiteCRM can detect duplicates during import, but they work best on data that is already clean.
Step 7: Plan the cut-over
Choose a cut-over date, ideally at the end of a week or month. Agree on a short freeze: after a certain time, new information goes only into the new CRM, never into the old spreadsheets. Then:
- Take a final export from every source.
- Run the full import using the tested mapping.
- Check record counts against the source.
- Spot-check important customers by hand.
- Make the old system read-only, but keep it available for a few months for reference.
Step 8: Support the team after go-live
The first two weeks decide whether the new CRM is adopted. Make it easy to report problems, fix data issues quickly, and show the team the benefits — a pipeline report that used to take a day, now available instantly. Small early wins build trust in the data.
Common mistakes to avoid
- Importing everything “just in case” and cleaning it later. Later rarely comes.
- Skipping the trial run because the deadline is close.
- Forgetting to create users before importing, so every record ends up owned by the administrator.
- Letting people keep using the old spreadsheets after go-live.
- Not keeping a full backup of the source data as it was before migration.
A well-planned migration takes a little longer at the start, but it means your team opens the new CRM on day one and finds data they recognise and trust. If you are moving to vTiger CRM or SuiteCRM, from spreadsheets or from another system, we can plan and run the migration with you — including the cleaning, mapping and trial imports.
