Free - No signup - Your address book stays in your browser

Preflight an Outlook contacts CSV.

Map ordinary spreadsheet columns to Outlook's contact headings, check emails, phones, dates, UTF-8 and delimiters, then export a small test file before the full import.

An Outlook contacts CSV preflight maps source headers to the headings in Microsoft's sample contact file, validates what the file itself can prove, and gates the data download behind a mapping review and a mailbox, backup, and test plan. This private workspace never signs in to Microsoft or sends contact values away from the tab.

01 - How it works

Turn a spreadsheet into a reviewed Outlook import.

Every source column receives an explicit Outlook field or Ignore. The complete file is checked locally before any contact-data download is enabled.

i. load

Open CSV or Excel

Drop a source, paste CSV, or load an imperfect or ready sample. One Excel sheet is converted locally, because Outlook imports CSV rather than multi-sheet workbooks.

ii. map

Choose path and fields

Pick Outlook.com or new Outlook versus classic Outlook, then confirm the Outlook heading for every column, such as E-mail Address or Mobile Phone.

iii. test

Export a small test first

Resolve blockers, acknowledge the mapping and the mailbox plan, then download the first 25 contacts before the normalized full file.

02 - What it checks

Evidence before address-book changes.

The desk validates what the file can prove and labels every Outlook-side uncertainty as a review.

  • 01

    Headings and mapping

    Blank and duplicate headers, one source per Outlook field, ignored data, and English headings from Microsoft's sample file.

  • 02

    File format

    Comma delimiter, valid UTF-8, consistent column counts, exact duplicate rows, and empty contacts.

  • 03

    Contact values

    All three email slots, phone characters, real Birthday and Anniversary dates, and ambiguous day/month order.

  • 04

    Path-specific review

    Classic duplicate options and destination folder, or the Outlook.com and new Outlook import flow with undocumented duplicate handling.

"A clean contact file is not proof that the mailbox, duplicates, or headings are ready."
csvtodashboard.com
Scope and handoff

Know what a local check cannot see.

The preflight never signs in to Microsoft or calls an Outlook API. Mailbox state and import results still require human review.

  • CSV handoff

    Outlook imports comma separated values. Excel and pasted sources are local preparation paths that end in UTF-8 Outlook CSV.

  • No mailbox state

    The signed-in account, existing contacts, Outlook's language, and duplicate matching are not queried.

  • No acceptance guarantee

    Export existing contacts first, import the first 25 contacts, inspect them, then import the rest.

03 - FAQ

Outlook contacts CSV questions.

Can I validate an Outlook contacts CSV before importing it?
Yes. This local preflight maps each source column to an Outlook contact heading, checks headers, delimiters, UTF-8, emails, phones, and dates, and creates a small test file. It cannot see your mailbox or guarantee that Outlook accepts the import.
No. Parsing, mapping, validation, masked evidence, and downloads stay in the current browser tab. Contact values are not sent to Microsoft or csvtodashboard.
Microsoft says Outlook can import comma separated value files but not workbooks with multiple sheets, so save the one sheet you need as CSV. The validator reads one selected sheet locally and writes CSV without uploading the workbook.
Microsoft says Outlook requires column headings in the first row and that they must match Outlook's default language. Microsoft's sample contact CSV uses headings such as First Name, Last Name, E-mail Address, Mobile Phone, Birthday, and Categories.
Microsoft recommends UTF-8 encoding and warns that characters such as Greek, Cyrillic, Arabic, or Japanese can cause problems otherwise. Save as CSV UTF-8 (Comma delimited) and restart the import if the preview looks wrong.
Only classic Outlook documents a choice: Replace duplicates with items imported, Allow duplicates to be created (the default), or Do not import duplicate items. Microsoft's Outlook.com and new Outlook steps do not describe duplicate handling, so inspect results.
Microsoft's sample file writes dates as month/day/year, such as 1/20/1981. The validator accepts that or YYYY-MM-DD, blocks impossible dates, and asks you to confirm slash dates that are valid in either order.
No. A ready verdict means the file passes local checks and both acknowledgments. Mailbox choice, heading language, duplicate behavior, and the final result still need a test import and inspection.