Merge Two Spreadsheets by a Common Column — Without VLOOKUP
You have two spreadsheets: orders in one, customer details in another. You need the customer's name, email, and region next to each order. In Excel that means VLOOKUP (or XLOOKUP / INDEX-MATCH) — and a familiar set of headaches: the lookup value has to be in the leftmost column, the column index breaks the moment someone inserts a column, and you redo the whole thing every time a new file arrives.
There's a cleaner way to merge two spreadsheets by a common column that you build once and re-run on every future file.
Why VLOOKUP is the wrong tool for recurring files
- It breaks. Column positions shift; the formula silently returns the wrong column or #N/A.
- It's one row at a time. Drag-fill across 100k rows and Excel crawls.
- It's not repeatable. Next month's export means rebuilding the lookup from scratch.
- Duplicates surprise you. VLOOKUP grabs the first match — fine, until you forget that.
The repeatable way: a “merge” step
The mental model is simpler than VLOOKUP: pick the key that links the two files, and choose which columns to bring across.
- Open your main file (e.g.
orders.csv). - Add a Merge from another file step and choose the second file (
customers.csv). - Match
orders.CustomerIDtocustomers.ID. - Pick the columns to pull in: Name, Email, Region.
- Choose keep all rows (unmatched get blanks) or only matches.
Do it in one click with Kramata
Kramata is a free desktop app for exactly this. Merge is a step in a recipe — save it, and next month load the new file and click once. No formulas, no broken references, and your files never leave your computer.
- Reproducible: same files + same recipe = identical output.
- Batch: apply the merge across a whole folder of files at once.
- Big files: powered by an in-process database, not row-by-row formulas.
Related guides
Merge multiple CSV files into one · A simple Power Query alternative · Clean a messy CSV the same way every time
FAQ
Can I match on more than one column? Single-key matching today; multi-key is on the way.
What if the other file changes? Re-running the recipe re-reads it — your merge stays current.
Is it faster than VLOOKUP on big files? Yes — it matches through an in-process database, not a formula dragged down 100k rows, so large files stay fast.
Is it like Power Query's Merge Queries? Same idea, in plain language, built for non-technical users.