CRM Import Checker: Review a CSV Before Importing
A small preflight for a lead import, built around a reproducible six-row example. It flags problems for review; it does not connect to a CRM or change records.
Inputs stay in this tab. No fetch, account connection, telemetry or persistent storage is used. Start with the fictional example; avoid customer data. Reload to clear the tab. Downloads happen only when you choose Export.
1. Understand the rules and limits
Required headers: external_id, email, owner, created_at. Trim and lowercase email only for comparison. A shared normalized email is a review candidate, not proof that two people are the same. Blank IDs, invalid email format and invalid UTC timestamps are rejected. Missing owners and duplicate IDs require review. Ready means these limited rules passed; it does not establish consent, deliverability, identity, permissions or production-import safety.
Download the synthetic example CSV3. Compare the expected example result
6 rows: 1 ready, 3 review, 2 reject. L01 and L02 share a normalized email, L03 has an invalid email, L04 has no owner, L05 has an invalid timestamp, and L06 passes these rules.
Inspect the exact fictional inputs
external_id,email,owner,created_at L01,alex@example.test,Sam,2026-10-01T12:00:00Z L02, ALEX@EXAMPLE.TEST ,Sam,2026-10-02T12:00:00Z L03,not-an-email,Lea,2026-10-03T12:00:00Z L04,jules@example.test,,2026-10-04T12:00:00Z L05,jo@example.test,Sam,not-a-date L06,ren@example.test,Lea,2026-10-06T12:00:00Z
The same functions are used by the published tool and automated regression tests. You can inspect the calculation source. No result is represented as a customer outcome.
4. Decide what to do next
Resolve each flagged row in a copy. Keep the original source, field map and external IDs. Use a separate staging import in your CRM, then reconcile accepted, rejected and queued records. Check ownership, field lengths, enum values and permission behavior there. This tool cannot test vendor-specific limits.