ArticlesCRM, projects & time

Moving customer records to a CRM: an import checklist

Prepare field mapping, customer identifiers and duplicate decisions, then test a small import before migrating the full register.

GlomivaUpdated November 10, 20263 min read

A new CRM will not organise unclear data automatically. Decide which customers, contacts and open deals you need, and how they should relate in the new system. Confirm supported formats, fields and relationships with the supplier.

Choose an original and an owner

Designate the authoritative export and save a protected copy before editing. Assign decisions about ambiguous records and duplicates. Limit access and use secure transfer. Fictional records are often enough for an initial supplier demonstration; do not put real customer data in an open test environment.

Separate companies, people and deals

A company may have several contacts and deals. Check whether the old sheet mixes everything into one row. Creating a company for each contact can make the register less clear.

Use a suitable stable identifier when available. A display name can change and may not be unique. Define company, person and project relationships before importing history.

Create a field map

This example is fictional.

Existing fieldDestinationCheck before import
Customer numberExternal customer IDPreserve format and uniqueness
CompanyCompany nameSeparate names from internal comments
ContactContact personIdentify the correct company
OwnerUser or ownership fieldConfirm the recipient exists
Next stepActivity or noteCheck text and date handling

Treat identifiers as identifiers, not quantities. Check leading zeros, dates, delimiters and character encoding. Obtain the required format from the supplier.

Decide how duplicates work

Consider alternate company spellings, a person with a changed email and genuinely different companies with similar names. Do not merge solely on name similarity.

Agree comparison rules and who reviews uncertain cases. Establish whether an import appends or updates, and how existing records are recognised.

Test a small, varied sample

Include accented names, multiple contacts, empty optional fields and specially formatted IDs. Define expected company, person and deal counts before the test.

Check counts, relationships and sample fields afterwards. Have a colleague find a customer and identify the next activity. A successful import message does not prove correct mapping.

Plan the final switch

Decide when the old register stops changing and how transition updates are captured. Apply the approved import and verify it before changing daily work.

Ask how to correct or undo a bad import without losing later manual edits. Retain originals according to company policy, rather than spreading unnecessary customer copies.

Glomiva’s CRM page describes CSV and Excel import. Bring your field map to a walkthrough and confirm support for your relationships and fields. For an earlier decision stage, read when a small business needs a CRM.