A CSV is a plain-text table. It does not store a cell's display format, data type, font, or leading-zero rule. When a spreadsheet opens 00184 and displays 184, the spreadsheet has interpreted the text as a number. Saving at that point can make the loss permanent. Date values face a similar problem because different programs and locales interpret the same short text differently.
The safest workflow distinguishes identifiers from quantities, uses unambiguous dates, and checks the raw exported result before import. These habits matter for customer IDs, invoice references, postal codes, account codes, employee numbers, tracking numbers, and any field where the characters themselves carry meaning.
Decide whether a value is an identifier or a number
A number represents a quantity that can be added, averaged, or compared mathematically. An identifier labels a record. You would add invoice amounts, but you would not add invoice numbers. That distinction determines whether leading zeros are expendable.
Values such as 000431, 02108, and 00-194-A should usually be treated as text. Even an all-digit account code may be text if the destination expects an exact width. Write this decision down for each source field instead of relying on what a spreadsheet guesses.
Preserve leading zeros before opening a CSV
If you must use a spreadsheet, import the CSV through its data-import flow rather than double-clicking the file. Set identifier columns to text during import. Different spreadsheet products use different labels for this option, so confirm the preview shows the full original characters before loading the sheet.
Once zeros have been removed and the file has been saved, the CSV usually contains no information about how many zeros existed. Padding every value to a guessed width can create new errors. Restore zeros only from an authoritative rule, such as a documented six-character customer code, or by returning to the untouched source export.
Make dates unambiguous
The value 04/05/2026 is ambiguous. In one locale it means April 5; in another it means May 4. Month names can be readable, but language and abbreviation support vary. Two-digit years add another avoidable decision.
A year-first date such as 2026-05-04 is easy for a person to audit and sorts correctly as text. It is a good normalization target when the destination supports it. Always verify the destination documentation or sample file first. Some systems require a local format or include time and timezone requirements that a date-only conversion cannot satisfy.
Do not normalize an ambiguous value by guessing. If rows contain both 13/04/2026 and 04/05/2026, the first row suggests day-first input, but a mixed-source file may still contain inconsistent conventions. Confirm the source system setting or ask the file owner.
Check timestamps separately
A timestamp is not just a longer date. It may include a clock time, offset, or timezone. Converting 2026-05-04 23:30 without knowing the timezone can move the calendar date. If the destination asks only for a date, establish which business timezone determines that date before discarding time information.
MapMyCSV recognizes and normalizes supported date-like values for its mapped output, but it is not a timezone conversion service. Review date results in the preview and retain the original file for comparison. Unsupported or unclear business rules require manual confirmation.
Inspect the raw CSV, not only the grid
A spreadsheet grid shows its interpretation. A plain-text view shows what will be imported. Inspect a copy of the output with a text editor or a CSV-aware tool. Search for a known leading-zero ID and a known date. Confirm quotes around comma-containing names are balanced and verify the header row has the expected number of columns.
- Keep an untouched copy of the source export.
- Classify IDs, postal codes, and references as text.
- Confirm ambiguous source dates with the file owner or system settings.
- Use the exact date form required by the destination template.
- Inspect raw output values after any spreadsheet save.
- Test a small import and compare created records to the source.
Map without changing unrelated values
Column mapping should be a narrow transformation. Rename and reorder fields to match the target, trim accidental surrounding whitespace, and apply only the date rules the destination needs. Do not strip punctuation, remove zeros, or convert blank cells to numeric zero without a documented requirement.
The CSV column mapping guide explains how to verify source-to-target matches. If the target is a supported QuickBooks workflow, begin with the current sample file and use the QuickBooks CSV import preparation guide.
What MapMyCSV does and does not do
MapMyCSV reads CSV content in the browser, maps source headers to the target headers you provide, preserves leading-zero identifiers as text, and presents a ten-row preview with validation flags. You can correct suggested pairings before export. A one-time $29 payment unlocks the full mapped CSV download, with no subscription or account.
It cannot recover characters already lost from a saved source, determine the meaning of an ambiguous date without context, choose accounting treatment, or guarantee that a third-party system will accept a file. The destination's current rules and your review remain authoritative.
Review a CSV in MapMyCSV