Northvault Digital · GUIDE

CSV before CRM import: a practical preflight

A CRM import can fail before the first row is accepted. A short preflight catches structural problems early and gives the operator a safer test-import plan.

1. Preserve a working copy

Keep the original export unchanged. Work on a dated copy and record the source, destination CRM, owner, and intended import date.

2. Check identifiers

Look for repeated record IDs, repeated email addresses, missing required identifiers, and inconsistent headers. Decide which field is the stable match key before merging anything.

3. Check field semantics

Review email syntax, phone formatting, dates, status values, owner names, and follow-up fields. Flag blanks for review instead of silently inventing values.

4. Test safely

Back up the destination, use a small sample, confirm how the CRM handles duplicates, and verify a few records after the test import.

5. Record what remains unknown

A preflight identifies risk; it does not certify consent, deliverability, identity, or a successful import.

Run the free browser-local precheck See the USD 19 kit

Synthetic examples only. No CRM connection, file upload, or protected-data processing is provided by this guide.