Excel VLOOKUP for Multiple Columns is what Turbo Excel VLookup was built for: match and extract data, without opening the formula bar or worrying about column counting, exact-match arguments, or broken external references.
The sections below cover how the matching process works, what's included, who it tends to fit best, and how it compares to writing the equivalent VLOOKUP formula by hand, so you can decide quickly whether it fits your own spreadsheets.
- Load the file you want to enrich, and the file that holds the reference data.
- Map the two ID columns that should be used to find matching rows.
- Select every column you want brought across in a single pass, not one at a time.
- Run the match across the entire dataset at once.
- Review the session log and export the finished spreadsheet.
Matching still comes down to the same basic idea as a manual VLOOKUP - given an ID in this table, find the related value in another file:
| Employee ID | Name | Department | Salary |
|---|---|---|---|
| E101 | Asha Rao | Marketing | 54000 |
| E102 | Vikram Shah | Finance | 61000 |
| E103 | Priya Nair | Sales | 48000 |
Instead of writing =VLOOKUP("E102", A2:D4, 3, FALSE), the same result comes from picking the Employee ID column in each file from a dropdown and ticking Department as a return column.
- Purpose-built for matching unique identifiers like IDs, SKUs, and codes
- Handles both text-formatted and numeric-formatted identifier columns
- Composite key matching when a single ID field isn't unique on its own
- A match-rate report showing exactly which identifiers didn't find a match
- Works equally well with a few hundred records or several hundred thousand
A natural fit for any spreadsheet organized around a unique identifier - employee IDs, SKUs, customer numbers, or database keys - where the same identifier needs to be matched against a second file.
It handles identifiers stored inconsistently as text in one file and numbers in another, which is a common source of failed matches with a plain formula.
A plain VLOOKUP formula assumes an ID column is formatted identically in both files, which frequently isn't true across systems. Matching logic that normalizes identifier formatting before comparing reduces the number of false non-matches.
Identifier columns are especially prone to invisible formatting differences - leading zeros dropped by Excel, inconsistent hyphenation, or mixed text and numeric storage - so it's worth checking a few known-matching pairs manually first.
If a batch of identifiers consistently fails to match despite looking identical, converting both columns to the same data type before loading the files usually resolves it.
Does it matter if my ID column is stored as text in one file and numbers in another?
No, the matching logic accounts for this common mismatch automatically.
Can I match on a composite identifier, like a code plus a date?
Yes, composite Key Column Pairs support matching on more than one identifying column at once.
Is any coding or macro knowledge required?
No, the entire process is handled through a point-and-click interface with no code involved.
Does this replace VLOOKUP entirely, or work alongside it?
It can be used instead of writing a VLOOKUP formula, or alongside existing formulas in the same workbook - there's no conflict either way.
What file formats are supported?
XLSX, XLS, and CSV files are supported for both input and output.
Does the source file need to stay open while matching runs?
No, both files are loaded directly by the app and don't need to remain open in Excel.
What happens to rows that don't find a match?
Unmatched rows are clearly reported in the match statistics rather than silently left blank or causing an error.
Is a Gumroad license required to use the full feature set?
Yes, a license key activates the full version; activation details are covered on the Support and Activate pages.
Can the same match be re-run later on updated files?
Yes, the same column mapping can be reused any time the source files are refreshed with new data.
Does it work with very large spreadsheets?
Yes, the matching engine is built with parallel processing to handle large files without slowing down.
Can I undo a match if the wrong columns were selected?
Yes, since the original files aren't modified in place, simply reload them and run the match again with corrected column selections.
Ready to stop fighting #N/A errors and match your spreadsheets visually?