Keep the original
Retain an untouched source copy. Record its filename, export time, source system, and record count. Work on a separate copy and note each transformation.
Profile the fileA reusable checklist for moving CSV records into a CRM, database, or business application. Preserve the original values, test the mapping, and account for what changed after the import.
Use the download to record Pass, Fail, or N/A with evidence in Notes. Resolve failures before approval. The tools help inspect a file; your destination's import rules determine whether it is ready.
Retain an untouched source copy. Record its filename, export time, source system, and record count. Work on a separate copy and note each transformation.
Profile the fileConfirm the destination accepts the encoding and delimiter. Inspect accented text, embedded line breaks, and quoted commas. Count parsed records, since a record can span several text lines.
See a test caseDocument the source column, destination field, expected type, required status, and blank-value behavior. Review extra, missing, or repeated headers before mapping.
Inspect missing valuesTreat identifiers as text. Confirm the matching key is complete and unique for this import. Decide whether the operation creates, updates, or upserts records before using a key to match them.
Check key candidatesKeep raw amounts and dates as text during review. Specify currency, decimal separator, date order, and time zone where relevant; preview any approved conversion before applying it.
Review date formatsCheck exact duplicate keys separately from similar names or records. Confirm whether each candidate is a repeat or a distinct record. Record the decision before merging or deleting anything.
Find near duplicatesUse a sandbox or documented preview mode. Include blank values, quoted text, long IDs, duplicate keys, and ambiguous dates. Verify rejection behavior and a recovery method before approval.
Review the go-live checksSave the import log and post-import export. Explain created, updated, skipped, and rejected records under the destination's rules. Compare matched records by key and inspect unexpected field changes.
Compare CSV exportsThese invented values are test cases, not customer data. Include comparable edge cases from your own import contract in a small test file.
001 and 1 are different text identifiers. Opening and saving a file with automatic numeric conversion can remove that distinction. Set the identifier field to text and confirm it survives the test import.
In a comma-delimited CSV, "Acme, Test" is one quoted field. Verify that the importer keeps the company name together instead of shifting the remaining values into the wrong columns.
03/04/2026 does not establish whether March or April is intended. Confirm the source's date convention, document the conversion, and verify the resulting date in the destination.
A successful upload is only one part of the check. Decide what success means before you modify production records.
Name the reviewer and import owner. Record the target environment, file version, mapping, create/update rules, test findings, and accepted exceptions. Make it clear which exact file and settings were approved.
Export the affected records and retain the identifiers needed to find new records. Check whether the system supports reversing this operation, restoring field values, or recovering a backup. Confirm the recovery method in the test environment.
Check how the importer defines each outcome; some categories overlap. For exclusive outcomes, accepted plus rejected plus skipped should account for the submitted records. With updates, the destination's total record count may stay the same.
The CSV has five columns: step, check, pass_condition, status, and notes. The Markdown version includes a place for the file, mapping, owner, approval, and recovery details. Adapt the checks to your destination.
Data Workbench compares two CSV exports by the identifiers and fields you choose. The offline Browser Workbench includes saved settings and CSV/JSON reports; the Reconciliation Kit provides a JavaScript engine and command-line runner. Each edition is a separate $49 one-time purchase.