How to use Row Upsert Between Two Datasets
- Paste the base and update tables, or choose a CSV, TSV or XLSX file for each. A chosen file replaces that source's pasted text; XLSX uses its first visible worksheet.
- Enter the exact key heading. Both tables need the same unique headings and keys that are unique and nonblank within each source.
- Check update records before running: every non-key cell replaces the matching base value, including blanks. New keys will append.
- Run the upsert, then download upserted.csv and upsert-actions.csv. Review updated, inserted and unchanged rows before importing the result elsewhere.
Example: Row Upsert Between Two Datasets
Update matching rows and download the complete action list.
Options
- Base table
- Paste the table you want to keep as the starting point. Up to 100,000 data rows, 500 columns and 2,000,000 cells.
- Update table
- The same headings as the base table, in any column order. A blank cell replaces the base value with an empty value on purpose.
- Key column
- The heading present in both tables whose values are unique and nonblank.
- Delimiter
- Read the base and update text tables with the same separator before matching their headings and keys. XLSX sources read saved worksheet cells.
- Protect spreadsheet formulas
- A cell whose first visible character is = + - or @ receives an apostrophe in the downloads. Turn it off to keep the raw value.
Supported inputs and limits
- Each source accepts pasted CSV/TSV or a CSV/TSV/XLSX file, up to 20 MiB, 100,000 rows, 500 columns and 2,000,000 cells.
- XLSX uses its first visible worksheet.
- Tables must have the same unique headings and unique nonblank keys.
- A matching update replaces every non-key value, including blanks.
- New keys append in update order.
More details
No database is contacted.
The CSV and action downloads include every result row; review any formula-prefix changes in your destination application.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
Replacement happens at the record level
An existing key takes its supplied update row, and a new key is appended. Base rows without an update remain in their source order. This makes the update table a complete replacement record for each named key rather than a sparse cell patch.
Check blanks before replacing records
A blank update cell can erase a previously populated value. Review the changed-row report and the downloaded table before importing it elsewhere. The tool creates a new file and does not update a database or overwrite the original export.
Questions about Row Upsert Between Two Datasets
Does an empty update cell keep the old value?
No. The update record replaces all non-key cells for a matching key. An empty cell deliberately clears that value.
Can update headers be in a different order?
Yes, if both tables have the same unique header names. Update cells are aligned to the base header order.
Will this update a database?
No. The result and action record are local downloads. Applying those files to another system is a separate step.