If two CSV files describe the same fields with different names or column order, import them into Numbers on your Mac, identify equivalent columns, and place their data under one consistent set of headers. Numbers can import delimited text and adjust delimiter, text qualifier, and encoding settings, but Apple’s documented import controls do not describe automatic matching of different header names. For a small batch, reconcile columns deliberately in a new table and check the result before exporting.

First decide which headers mean the same thing

Before moving data, make a short mapping from each source header to the name you want in the combined file. For example: Client and Customer Name might map to Customer; Order Date and Date might map to Date. Treat these as equivalent only if the values represent the same information. A field such as Invoice Date should not be merged with Due Date just because both contain dates.

Also note fields that appear in only one file, repeated headers, and differences in units or formats. A column named Amount could contain dollars in one file and cents in another; putting both under one header without conversion would make the combined data misleading. Keep the original CSV files unchanged so you can refer back to them.

Import and inspect each CSV in Numbers

Open Numbers, then drag a CSV file onto the Numbers icon in the Dock or choose File > Open and select it. If the columns do not split correctly, select the imported table and choose Format > Table > Adjust Import Settings. In the Delimited settings, choose the delimiter, text qualifier, or encoding that matches the file, then click Update Table. Apple notes that you cannot adjust these import settings after editing the imported table, so fix parsing first. Apple’s Numbers guide explains text-file import and these settings.

Check that the first row contains the expected headers and that sample values are in the correct columns. A value such as 00127 may be an identifier rather than a number: preserve it as text if its leading zeros matter. If the file has odd characters or shifted columns, review the encoding and delimiter before reconciling headers; a mapping cannot repair a wrongly parsed row.

Build a consistent table and map the columns

Create a new Numbers sheet or table for the combined result. Put your chosen standardized headers across its first row, one column per field. For each source file, use this sequence:

  1. Find each source column by its header and confirm the values make sense for the target field.
  2. Copy that whole data column, excluding its header, into the matching target column beneath the standardized header.
  3. If a source lacks a target field, leave those cells blank; do not shift later columns left to fill the gap.
  4. Repeat for the next file, placing its records below the previous file’s records in the same target columns.
  5. If a field needs a clear, agreed conversion, convert it consistently before appending and record the rule in a note alongside your working file.

For example, if one export has Email, Name, Signup Date and another has Customer, Joined, Email Address, your target might be Name, Email, Signup Date. Copy the first file’s Name, Email, and Signup Date columns into those destinations. For the second, copy Customer into Name, Email Address into Email, and Joined into Signup Date. This explicit mapping preserves meaning even when the source order differs.

This is a manual workflow: Numbers’ documented import settings control how text is parsed, not a rule that automatically equates Email with Email Address. If you have many recurring files, consider a repeatable data transformation tool, but confirm its Mac version and exact controls in that product’s current documentation before relying on it.

Check the result and export a new CSV

Before export, compare several records against their original files, including the first and last rows of each batch. Check that every value stayed with the intended header, that no columns were accidentally omitted, and that blank cells reflect missing data rather than a copy offset. If the source files have different date or number conventions, verify those values separately.

When the reconciled table is ready, choose File > Export To > CSV. Numbers exports cell contents as comma-separated values and offers options including exporting each table as a separate file or combining tables, plus text-encoding settings. Export to a new filename and location so the source files remain intact. Apple’s export guide documents the CSV options. Open the exported file again in Numbers to confirm the headers and a sample of the data still appear in the intended columns.

When files need to be combined repeatedly

For a one-time or small reconciliation, the manual column map is transparent and easy to inspect. If you receive many files on a schedule, automation can save repeated copying, but it needs a defined mapping and checks for new, missing, or renamed fields. Microsoft documents Power Query’s folder-combine workflow for listed Windows Excel editions and says those files should have consistent column names and schemas; the article does not list Excel for Mac. Do not assume that exact folder workflow is available in your Mac installation. Microsoft’s folder import documentation lists the applicable editions and requirements.

The essential safeguard is to map by what each value means, not by where a column happens to appear. Keep the original files, use one clear target header row, and verify the exported copy before using or sharing it.

Sources