CRM import preparation

Fictional demonstration. All data is invented.

Turn 12 fictional contact rows into 7 prepared rows, hold 4 for decisions, and exclude 1 exact duplicate.

Twelve invented company/contact records. Every supplied email uses the reserved example.com domain. No real person or business data is used.

Before and after

1. What changed

• Preserve source record IDs. Trim outer whitespace and collapse repeated spaces in company/contact names. Preserve spelling and name case.
• Trim email whitespace. Do not change the email local-part or invent a missing email.
• Uppercase supplied country codes. The demo accepts US, GB and CA.
• Use the agreed demo Active/Inactive map. Hold an unmapped status.
• Exclude a row only when every raw business field exactly matches an earlier source row. Source IDs and dataset labels are excluded from duplicate comparison.
• Hold both rows when the same cleaned company/contact name has different email values. Do not infer a merge.
• Keep held and duplicate records outside the ready CSV. Log every changed field and each row disposition.

2. Calculations and checks

• 12 input rows = 7 ready + 4 held + 1 exact duplicate.
• C007 exactly duplicates C006 and is excluded.
• C008 lacks an email. C009 and C010 are an ambiguous pair. C011 has an unmapped status.
• Every source ID occurs in exactly one disposition.
• All nonblank emails use example.com. Ready emails pass a basic syntax check only.
• Ready rows contain all required demo fields, mapped statuses and accepted country codes.
• All formatting changes and exclusions are traceable to source record IDs.

3. Decisions still needed

• C008: provide the missing email.
• C009 and C010: confirm whether there are two contacts or choose the correct email.
• C011: choose how Prospect maps to the target status.

Limits of this example

• Ready means prepared against the demo rules only. No production CRM import has been performed.
• Email deliverability, identities and company facts have not been verified.
• The target CRM field requirements and mapping still need agreement. The ready CSV is a generic review template.
• dataset_label and source_record_id are audit columns. Map or omit them only after the target template is agreed.