Prepare cleaning customer records for CSV import

Clean duplicates and identify the record type before mapping columns. A dry run should reveal what will be created and what needs attention.

A situation to work through
Two rows use different spellings for one customer while three properties share the same billing contact. Resolve the relationships before applying the import.

Work through the decision
Keep an untouched copy of the export. Identify the supported entity type and map its identifiers and required fields. Resolve duplicate customer rows and property relationships before starting a dry run on the prepared file.

Before you hand over the result
A file export is not a live integration with the old system. Keep the original file and verify supported fields before importing.

Worksheet

Source file
____________________________

Record type
____________________________

Unique key
____________________________

Required columns
____________________________

Duplicate decision
____________________________

Relationship check
____________________________

Acceptance check
The import file has a clear identity mapping and an explicit decision for ambiguous or duplicate records.

https://grooovy.madebydima.online/guides/cleaning-csv-import-preparation