Airtable CSV merge: choose a key and reconcile updates

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Choose update semantics before importing

Use this workflow when a recurring supplier file should update existing rows. Airtable’s CSV import extension supports merging on a selected field. Matching is case-sensitive, ignores surrounding whitespace and creates records for unmatched keys. Availability and permission requirements belong to the extension, so check access before promising a repeatable import to a colleague.

Build a reconciliation fixture

Consider an illustrative stock list with existing keys SKU-A and SKU-B. A file contains SKU-A with quantity 9, SKU-C with quantity 4 and one row with an empty key. The desired business outcome is one update, one intentional addition and one rejected source row. Reject the empty key in your preparation sheet rather than importing it and hoping it will match. Keep the raw file unchanged for comparison.

Rehearse the merge

1. Take a base snapshot and work first with disposable sample records.
2. Check uniqueness of the chosen key in both files. Investigate duplicates instead of choosing the first conveniently available column.
3. Select the destination table, enable merge and map the identity and quantity fields explicitly.
4. Choose whether incoming blanks should clear existing information; review the skip-blank setting against that decision.
5. Compare the preview’s updated, unchanged and created counts with the fixture. Stop if the extra row is not explained.

Approve values as well as row counts

After the sample import, inspect SKU-A’s quantity, SKU-B’s unchanged values and SKU-C’s identity. Record source rows accepted, rejected and deferred. A matching total is insufficient if quantities landed in the wrong field. Preserve an exception sheet for capitalization differences and missing keys, and obtain a corrected file before the larger merge.

When to use another approach

A recurring CSV procedure is appropriate when someone can review each batch. A continuously refreshed cross-base dataset needs a separately designed sync workflow. This checklist does not demonstrate throughput or guarantee rollback of downstream automations; review actions that react to changed rows before running a production import.

Continue with Airtable sync: assign ownership before sharing a source view when that next step matches your workflow.