Remapping CSV columns for import is the job of putting each source field under the exact header, order, and value shape a destination template requires. A source may call a field Cust ID while the import template calls the same value account_id. The labels differ. The meaning does not. Make that pairing explicit before any rows hit the importer.
Start from the destination template
The destination template is the contract. Download its current sample import file or copy the documented header row before you touch the source. Do not begin by cleaning the export into a file that merely looks tidy. Begin with the exact required target headers, including capitalization only when the destination documentation says capitalization matters.
Separate required columns from optional columns. A required customer name may block an import when empty. An optional memo should not. Also note fields with controlled values, such as an account type, tax code, status, or currency. Remapping puts values under the right heading. It cannot invent valid business choices that are absent from the source.
Do not invent a destination header list from memory or from another company's sample. Use the template attached to the import you will run. Destination-specific header packs belong on their own URLs. For a QuickBooks import type, use the sibling QuickBooks CSV import format guide.
Map columns by meaning
Exact labels are the easiest matches. Next, consider common abbreviations and business synonyms: Order Total may map to amount, and E-mail Addr. may map to email. Never accept a close label on wording alone. Review several values beneath it. A column named Account might contain an account number, an account name, or an account category.
- Confirm every required target column has one source.
- Check that one source was not assigned to unrelated targets by mistake.
- Read sample values from the beginning, middle, and end of the file.
- Keep unknown mappings visibly unresolved instead of guessing.
- Document any constant values you must add in the destination system.
Remap and reorder without changing values
Renaming headers and reordering columns are the low-risk remaps. Trimming accidental spaces is usually reasonable. Date formatting can be appropriate when the destination specifies one form. More aggressive cleanup needs a business rule. Do not remove punctuation from references, coerce blank cells to zero, or merge names merely because another file used that convention.
A remap should preserve source meaning and make every change reviewable. MapMyCSV maps headers, presents a ten-row preview, flags missing values and malformed dates, and lets you correct pairings. It does not connect to QuickBooks, a CRM, or payroll software, and it does not submit the import for you.
Preview ten rows and keep a mapping pack
The free preview shows the first ten mapped rows plus validation flags for missing values and malformed dates. Use that preview to confirm required columns are populated, identifiers still look like identifiers, and dates match the destination form.
After a successful map, download a mapping pack (a small .map.json file). It stores header names, source-to-target pairs, and date rules, never row contents. On the next payroll, bank, or CRM export, drop the new file and that pack. MapMyCSV reapplies the saved pairs and the same date rules, then highlights renamed or missing source columns instead of guessing.
Protect dates and leading zeros
Treat identifiers that look like numbers as text. Customer code 00184 is not the number 184. Postal codes, invoice references, and account codes follow the same rule. Date formatting is appropriate only when the destination specifies one form.
Do not invent cleanup rules here. For the full workflow on ambiguous dates and leading zeros, use the sibling CSV dates and leading zeros guide.
Validate the exported CSV before importing
Compare the output header row with the destination template character for character. Count output rows and reconcile that count to the source, excluding any intentionally removed totals or notes. Search required columns for blanks. Spot-check quoted names, negative amounts, non-ASCII characters, dates near month boundaries, and the longest identifiers.
Run a small test import when the destination supports it. Read the import report rather than treating a successful upload as proof that every field landed correctly. If the system rejects the file, save the exact error and connect it to a target column or row. Correct the mapping rule, regenerate the file, and repeat the checks.
When remapping is the wrong tool
Column remapping fixes header names, order, and reviewable remaps. Do not use it when the problem is not column structure.
- You need transaction matching or payout-to-bank reconciliation. That is ReconcileCSV, not column remapping.
- You need the tool to invent missing controlled values, choose ledger accounts, or deduplicate customers. Mapping cannot decide business truth.
- The destination requires an API sync or a live connector. MapMyCSV does not connect to the destination system or submit the import for you.
- You want aggressive cleanup that strips punctuation from references, coerces blanks to zero, or merges names without a rule. That creates import risk the mapper should not hide.
If headers already match and values are already typed correctly, skip the remap and import.
Remap CSV columns in the browser for $29 once
A browser-local remap is useful when you receive recurring exports with mismatched headers and need a reviewable output without uploading client files. Drop the spreadsheet rather than saving it as CSV first if that is how the file arrives. Mapping, preview, validation, and export run in the browser. There is no account and no subscription.
The free preview shows the first ten mapped rows. A one-time $29 payment unlocks the full mapped CSV and a reusable mapping pack. Pay $29 once.
FAQ
What is the difference between source headers and destination headers?
Source headers are the column names in the export you received. Destination headers are the exact names the import template requires. The business meaning can be the same while the labels differ - for example Cust ID versus account_id. Mapping makes that relationship explicit before any rows are imported. Start from the destination template, not from a cleaned-up source that merely looks tidy.
Should I match columns by label wording or by the values underneath?
Exact labels are the easiest matches. After that, use common synonyms only when sample values confirm the meaning. A column named Account might hold an account number, account name, or account category. Review values from the beginning, middle, and end of the file. Leave unknown mappings unresolved instead of guessing from wording alone.
What does a saved mapping pack store, and what does it not store?
After a successful map, download a mapping pack (a small .map.json file). It stores header names, source-to-target pairs, and date rules, never row contents. On the next export, drop the new file and that pack. MapMyCSV reapplies the saved pairs and the same date rules, then highlights renamed or missing source columns instead of guessing.
How does this guide relate to QuickBooks-specific CSV imports?
This page is the process hub: destination template first, meaning over labels, validate before import. For QuickBooks, use the sibling guide on QuickBooks CSV import format for the exact import type and template headers you run. Keep this page generic so destination-specific rules stay on their own URLs.
How do I protect leading zeros and ambiguous dates during mapping?
Treat identifiers that look like numbers as text - customer code 00184 is not the number 184. Postal codes, invoice references, and account codes follow the same rule. Date formatting is appropriate only when the destination specifies one form. For the full workflow on dates and leading zeros, use the sibling guide on CSV dates and leading zeros rather than inventing cleanup rules here.
What does the $29 unlock include?
The free preview shows the first ten mapped rows plus validation flags for missing values and malformed dates. A one-time $29 payment unlocks the full CSV download and a reusable mapping pack. There is no subscription or account. Mapping, preview, validation, and export run in the browser. MapMyCSV does not connect to the destination system or submit the import for you.
Do my CSV files leave the browser in MapMyCSV?
No. Mapping, preview, validation, and export process in the browser. That matters when exports contain client or payroll data you do not want uploaded to a remapping service. Drop the spreadsheet rather than saving it as CSV first if that is how the file arrives. The mapping pack stores headers, pairs, and date rules only, not row data.
What should I validate before importing the mapped file?
Compare the output header row with the destination template character for character. Reconcile output row count to the source, excluding intentional removals such as totals. Search required columns for blanks. Spot-check quoted names, negative amounts, non-ASCII characters, dates near month boundaries, and the longest identifiers. Prefer a small test import when the destination supports it, and read the import report rather than treating upload success as field-level proof.
What problems does column mapping not solve?
Column mapping fixes structural differences: header names, order, and reviewable remaps. It does not reconcile transactions, choose ledger accounts, deduplicate customers, invent missing controlled values, or verify that a business value is correct. Aggressive cleanup - stripping punctuation from references, coercing blanks to zero, merging names without a rule - creates import risk the mapper should not hide.