What to check before importing a prospect list into your CRM

A bought list or an event export can be useful, but importing it straight away usually creates more work for the sales team. Company names may be incomplete, contacts may be attached to the wrong site and some accounts may already be in your CRM.

We treat the import as a decision about which records are ready, which should be excluded and which need another look.

Start with the purpose of the list

Decide what the team wants to do with it. Finding new accounts, updating existing ones and following up with event contacts call for different checks.

Agree the target market and the exclusions before researching the rows. Keep the source of the list with the records, and decide separately which contacts are eligible for outreach.

Match the company before changing the record

A similar name is not enough to establish a match. Look at the domain, the location, the business identity and the parent or site relationship. A branch may need its own record rather than an update to the group account.

Flag uncertain matches. An ambiguous row should never silently overwrite a record your team already relies on.

Check the facts that affect qualification

Use the same criteria your team uses to decide whether a company is worth approaching. For an industrial supplier, that might include the customer sectors, the distribution model, the product range and the territory.

In the fictional Meridian example, research turns a broad "wholesale" label into industrial distribution with trade ordering and maintenance products, which matches the agreed distributor criteria. A consumer-only retailer on the same list would be excluded under the same rules, and a row whose company identity cannot be resolved would stay in review.

Treat contact checks as separate results

Show whether a person's role is relevant, whether their company association is supported and which contact details are available. Email verification should have its own status. Unknown is a useful result when the alternative is a guess.

A deliverable address does not establish permission to send a campaign. Your audience exclusions and approval rules still apply.

Agree the write rules and review the sample

Decide which fields may change, which existing values are protected and what happens to possible duplicates. Review a sample before widening the import, particularly if the list structure is unfamiliar.

Keep a record of accepted rows, exclusions, gaps and changes. That gives your team a way to review the delivery and see what still needs attention.

We can research a list before delivery or improve the records already in your CRM. Tell us what the list contains and what your team needs from it.