How to Import Scanned Business Cards into Outlook (vCard and CSV)

You come back from a conference with sixty cards, and the address book those people need to reach is Outlook — because Outlook is where the calendar invites, the mail merge and the autocomplete live. The search that follows is usually some version of business card scanner that syncs with Outlook, and the honest answer is less exciting and more reliable than a plugin: it is a file.

Here is the whole route, including the four things that break it.

Is there a business-card scanner that plugs into Outlook?

Not this one. BizCardPro.AI has no Outlook integration — no add-in, no plugin, no API connector, no Zapier recipe, and nothing promised on a roadmap here. If a native Outlook add-in is a hard requirement, that is a straight no.

For the job most people actually have, it turns out not to matter much. An event stack is a one-directional load of a few dozen records, a handful of times a year. Outlook has supported importing contacts from a file for as long as it has existed, and a file route has one property a background sync does not: a human sees the data before it lands in the address book everyone emails from. The scanner’s job is not to talk to Outlook. It is to produce a clean file Outlook will accept.

What are the two routes into Outlook?

There are exactly two, and choosing correctly saves most of the work.

vCard (.vcf) is the contact-card format. Outlook opens one natively — the contact form appears pre-filled, with phone numbers already typed as business or mobile, and you save it. No mapping screen, no column names, nothing to prepare. This is the right route for one contact or a handful: the person you met at lunch, the three people worth adding today.

CSV is the table format: one row per person, one column per field. It is the right route for a batch — a dozen cards or more — because a spreadsheet is where you can see all sixty rows at once, spot the two duplicates, fix the company name someone’s OCR read as Acme Gmbh, and delete the four people you have no intention of contacting. That review pass is the actual value of the CSV route, not the import mechanics.

If you want the longer comparison of what each format carries, vCard vs CSV vs Google Contacts CSV covers it. And if you need to hand-build a single .vcf for someone right now, the free in-browser vCard generator does it without a signup.

Which Outlook are you actually using?

This matters more than any other question on this page, because “Outlook” is four different products sharing a name:

• New Outlook for Windows — the rebuilt client Microsoft has been rolling out.
• Classic Outlook for Windows — the long-standing desktop application with the full import/export wizard.
• Outlook on the web — outlook.com and Microsoft 365 in a browser.
• Outlook for Mac — its own application with its own history, and historically the most limited for CSV import.

Their import paths are not the same, and CSV import in particular has moved between versions and builds. So the reliable instruction is a shape rather than a click-path: open the People or Contacts area, and look for the option to import or manage contacts from a file. In classic Outlook for Windows this has long lived in the import/export wizard under the File menu; in the web client it sits in the People area; in others it may sit somewhere else entirely or not exist at all.

Confirm the path in the version in front of you rather than trusting any article’s exact menu names — including this one. Two useful fallbacks when your build will not import a CSV: import into Outlook on the web for the same account and let the contacts sync down, or use the vCard route instead.

What does the export file contain?

Every batch exports as a spreadsheet CSV with these columns:

Column	Holds
ID	Internal record id from the scanner archive
Name (Native)	The name as printed, in its original script
Name (Romanized)	The Latin-script rendering of the same name
Company (Native)	Company name in its original script
Company (Romanized)	Latin-script company name
Job Title (Native)	Title as printed
Job Title (Romanized)	Latin-script title
Email Address	Email from the card
Phone Numbers	Numbers from the card, normalised to international E.164
Website URL	Web address from the card
Address (Native)	Postal address in its original script
Address (Romanized)	Latin-script postal address
Uploaded At	When the card was scanned

Two properties matter more than the column list. Phone numbers are normalised to E.164, so the country code is never missing. And the file is UTF-8 with a byte order mark, which is what keeps Müller from arriving as Müller and 山田太郎 from arriving as 山田太郎.

How do the CSV columns map to Outlook contact fields?

This is the part worth bookmarking. Outlook’s own field labels vary between versions and languages, so read the middle column as the destination to look for, not a literal header string:

BizCardPro.AI CSV column	Typical Outlook contact field	Notes
Name (Romanized)	First Name + Last Name	Must be split into two columns before import — see below
Name (Native)	Nickname, or a custom/user field	Keep it if you want 名刺 names searchable in their own script
Company (Romanized)	Company	Also the field Outlook uses for file-as and sorting by organisation
Company (Native)	Notes, or a custom field	Optional, but useful for Asian suppliers
Job Title (Romanized)	Job Title	Free text; shows in the contact card header
Job Title (Native)	Notes, or a custom field	Optional
Email Address	E-mail Address	Also your best deduplication key
Phone Numbers	Business Phone / Mobile Phone	A card may carry more than one number — decide which column each belongs in
Website URL	Web Page	Usually the company site, not a personal one
Address (Romanized)	Business Address	Split into street, city, postal code and country if you want a structured address
Address (Native)	Notes	Keep it for shipping and for in-country correspondence
ID	Not mapped	Useful as your own reconciliation key against the scanner archive
Uploaded At	Not mapped, or Notes	Worth keeping as a record of when and where you met

How do I import a batch of scanned cards into Outlook?

1. Scan the batch and verify. Photograph the cards — several per photo is fine — and check each field against the card image kept beside it. Seconds now, or a bounced email to a prospect later.

2. Export the spreadsheet CSV for that batch only. Tag the batch by event first, then export the tag — not your whole archive. That way each import adds the people you just met rather than re-adding everyone you have ever scanned.

3. Reshape the file into Outlook’s shape. Split the name column into First Name and Last Name, decide which phone column each number belongs in, split the address if you want it structured, and drop what Outlook has no home for.

4. Find the import path in your own Outlook. People or Contacts, then the option to import or manage contacts from a file. Confirm it in your version rather than following a click-path.

5. Import a five-row test file. Include a CJK name and a compound surname among the five if you have them. Mapping mistakes are cheap to find on five contacts and expensive on two hundred.

6. Check the test contacts, then import the rest. Names in the right fields, accents and CJK characters intact, phone numbers still carrying their plus. Only then run the remaining rows.

What actually goes wrong?

One name column, two Outlook fields. Outlook’s CSV import generally expects First Name and Last Name as separate columns; a single Name column lands wrong, and every sort and search after that is wrong with it. Splitting on the last space works for Anna Bergmann and fails for van der Meer, Garcia Lopez, Kim Min-jun and every surname-first CJK name, where the family name comes first and a naive split hands Outlook a given name as the surname. Because the scanner detects name order per card, romanized names come out in the correct order to split — but eyeball the CJK and compound-surname rows before importing, not after.

Encoding. The export’s UTF-8 byte order mark exists precisely so that a double-click on a Windows machine renders CJK and umlauts correctly instead of falling back to the system code page. The destructive move is opening the CSV in Excel and re-saving it with the default plain-CSV option, which rewrites the file in that legacy code page and replaces every character it cannot hold with a question mark — permanently. Import the exported file as it came. If you must edit it, open it via Data → From Text/CSV and save as CSV UTF-8; the full diagnosis and fix is here.

The semicolon delimiter. The European version of the same trap. Excel in a German, French or similar locale uses the semicolon as its list separator, so a round trip through Excel can turn a comma-separated file into a semicolon-separated one. An importer expecting commas then reads each row as a single field, and you get one column of nonsense. Re-export rather than repair.

The leading plus. E.164 numbers start with +, and a spreadsheet will strip it the moment it decides the column is numeric — or render the number as 8.13123E+11. Keep phone columns formatted as text.

Duplicates. Import a whole event’s batch into an address book that already has half those people and you get two of each, with the older card’s stale mobile number sitting alongside the new one. Sort by email address in the spreadsheet and collapse the obvious repeats before importing, and treat any duplicate detection on the Outlook side as a safety net rather than the plan.

Multi-contact vCards. Some Outlook versions import only the first card from a .vcf holding many. If your file has forty people in it and one contact appears, that is the quirk — switch to the CSV route.

Which route should I choose?

Situation	Route
One person you just met	vCard (.vcf) — open, save, done
Three or four contacts	vCard, one file each
A dozen or more from an event	CSV, after a review pass in a spreadsheet
CJK or compound surnames in the batch	CSV — you need to see the name split before it lands
Outlook for Mac, or a build with no CSV import	vCard, or import via Outlook on the web
Contacts also headed for a CRM or mail merge	CSV — one file serves both

Where the scanner fits

BizCardPro.AI’s part of this is narrow and worth stating plainly: it turns a stack of paper into verified, structured rows — native script and romanization side by side, phone numbers in E.164, the original card photo kept beside every record — and exports them as CSV, Google Contacts CSV or vCard. It does not talk to Outlook, and no add-in exists or is claimed. Outlook is the destination; the scanner is the capture layer that stops sixty cards becoming an evening of typing. It runs in the browser, so there is nothing to install on the machine Outlook is running on.

Which also means this is a snapshot, not a sync. Change a phone number in Outlook and the scanner archive will not know, and the reverse is equally true. For cards collected at an event that is a fair trade — the cards do not change after the event either — but it is worth deciding early which side is your system of record. Most people should pick Outlook, and keep the archive as the capture log with the photos and the follow-up reminders.

If your destination is a spreadsheet or Google Contacts rather than Outlook, the shorter route is scanning business cards into Excel, CSV or Google Contacts.

Test the mapping with your own cards before the next event — the first 30 scans are free, and every export format is included from the first one.