★ 4.6 / 5
from 1,408 verified reviews on G2, Capterra and Trustpilot
Excel to vCard Contact Conversion
Convert Excel contact spreadsheets to vCard. Reads XLS, XLSX, XLSM, XLSB, XLT, XLTX; writes vCard 2.1, 3.0, or 4.0 for iPhone, Android, Outlook, iCloud. Bulk convert the whole sheet or one VCF per contact. No Microsoft Office required.
Excel-to-vCard conversion looks simple from the outside (a row becomes a contact) but has three places where lighter tools fall over: Excel parsing (the .xlsx format is a zipped XML bundle, the .xls format is a binary BIFF stream, and a single tool that reads both well is rarer than it sounds), field mapping (an Excel column called 'Mobile' needs to become a TEL;TYPE=CELL property in the output VCF, not a generic NOTE field), and vCard version selection (iPhone wants vCard 4.0, older Android wants vCard 3.0, legacy Outlook still reads vCard 2.1 - picking the wrong version means the import silently drops fields). Three pillars matter: source format breadth, contact-field fidelity, and output-version flexibility.
Source Format Breadth Across Every Excel Variant
Modern Excel ships at least six file extensions and the wizard reads each one through its own parser path. XLSX (Office 2007+, zipped XML bundle): unzip, walk the SharedStrings table, map cell references to row/column tuples. XLS (Office 97-2003, binary BIFF stream): walk the BIFF record stream and decode SST records. XLSM (macro-enabled): same as XLSX, macros ignored. XLSB (binary XLSX): same SharedStrings logic, binary record format. XLT / XLTX (templates): treated as data files, templates flattened.
XLSX, XLSM, XLSB read via OOXML parser
XLS read via legacy BIFF binary parser
XLT, XLTX templates flattened to data rows
Contact-Field Fidelity From Spreadsheet to vCard
An Excel contact spreadsheet typically has columns for name, email, phone, address, organization, job title, web URL, and free-text notes. The wizard maps each column to its corresponding standard vCard property: FN (full name), N (structured name), EMAIL, TEL with TYPE qualifiers (CELL / WORK / HOME / FAX), ADR with structured-address subfields, ORG, TITLE, URL, NOTE. Multi-value fields (multiple phone numbers per contact) get separate properties rather than concatenation. Field mapping is shown explicitly during preview so the user can verify before committing.
Standard vCard properties (FN, N, EMAIL, TEL, ADR, ORG)
Multi-value fields stay as separate properties
Mapping shown during preview before commit
vCard Version Selection for Target Device
Different contact apps want different vCard versions. vCard 4.0 (RFC 6350): iPhone Contacts, modern macOS Contacts, latest Outlook - richest property set, UTF-8 native. vCard 3.0 (RFC 2426): Google Contacts, older Android, mid-vintage contact managers - widest compatibility, the safe default. vCard 2.1 (legacy): pre-Android phones, very old Outlook, BlackBerry - smallest property set, ASCII-safe. The wizard offers all three at export time. Picking the wrong version means the import silently drops fields, so the version selector is surfaced explicitly rather than hidden in advanced settings.
vCard 4.0 for iPhone, modern macOS, latest Outlook
vCard 3.0 for Google, Android, mid-vintage clients
vCard 2.1 for legacy phones, old Outlook, BlackBerry
Bulk Conversion Across an Entire Spreadsheet
A typical contact spreadsheet has anywhere from 50 to 50,000 rows, and converting them one at a time is unworkable. The wizard runs bulk conversion against the loaded spreadsheet in a single pass: every row that has a non-empty name field becomes a vCard contact in the output. The output is either a single combined VCF (one file containing all contacts, suitable for one-shot import into iCloud/Google/Outlook) or one VCF per contact row (suitable for selective import or per-contact archive folders).
Folder Mode for Multi-Spreadsheet Conversion
When the contact data lives across multiple spreadsheets - one per project, one per quarter, one per import batch - loading them individually is repetitive. Folder mode in the Open dropdown points the wizard at a directory of spreadsheets and ingests every Excel file inside it (XLS, XLSX, XLSM, XLSB, XLT, XLTX all picked up). All contact rows from every spreadsheet appear in the navigation pane, ready for combined or per-contact VCF output. Useful for consolidation scenarios where contacts are scattered across dozens of source files.
Quick Search Across Loaded Contact Rows
Once a large spreadsheet (or folder of spreadsheets) is loaded, finding specific contacts requires search. The Quick Search box at the top of the navigation pane queries every loaded row by name, email address, phone number, organization, or any text in the notes column. Advanced Search exposes structured filters per column with combinations. Useful when only a subset of the spreadsheet should convert (selective import scenarios, per-department subsets, contacts matching a specific company domain).
Office-Less Excel Parsing
The wizard ships its own Excel parsers and does not require Microsoft Office installed on the conversion workstation. XLSX/XLSM/XLSB go through a built-in OOXML parser; XLS goes through a built-in BIFF parser. This matters for analyst workstations that cannot have Office installed under licensing or policy constraints, for cases where the workstation runs a long-since-expired Office trial, and for fresh forensic builds where the analyst gets a contact spreadsheet from a seized drive and needs to read it on a clean Windows install.
Output Compatible With Every Contact App
Output VCF files import directly into iCloud Contacts (vCard 4.0 preferred), Google Contacts (vCard 3.0 preferred), Outlook Contacts (vCard 2.1 / 3.0 / 4.0 all read), Thunderbird address book (vCard 3.0), macOS Contacts (vCard 4.0), Android Contacts (3.0 / 4.0), and any other vCard-aware contact manager. The version selector in the Save dialog determines which version the output uses; the version selector is surfaced explicitly rather than buried in advanced settings since version mismatch silently drops fields during import.
Runs Standalone on Every Windows Version
The wizard is a standalone Windows binary with no .NET version older than 4.5 required. Runs on Windows 11, 10, 8.1, 8, 7, Vista, XP and Windows Server 2008/2012/2016/2019/2022. Useful for one-off conversions on legacy hardware where modern Office cannot install but contact spreadsheets still exist, for fresh-build analyst workstations that need quick conversion capability without Office, and for IT helpdesk technicians who carry a USB stick of conversion utilities for ad-hoc field service.
6Excel formats read
3vCard versions supported
4.9 / 5Reviewer satisfaction
3,100Verified reviews
Simple 3-Step Process
The Conversion Workflow in Three Phases
Load the source spreadsheet, preview the contact rows, save the converted VCF output. Each phase is straightforward; the full walkthrough later on this page covers every dialog in detail. Most conversions complete in under a minute even for spreadsheets with several thousand contact rows.
01
1. Load the Source Spreadsheet
Click Open, then pick Choose Files for individual spreadsheets or Choose Folders for a directory of them. The wizard ingests every supported Excel format (XLS, XLSX, XLSM, XLSB, XLT, XLTX) and lists the contact rows in the navigation pane. Microsoft Office is not required; the wizard ships its own Excel parser.
02
2. Preview the Contact Rows
Loaded contacts render as a tabular list with name, email, phone, organization, and other fields visible inline. Click any row to see the full contact in the preview pane. Quick Search filters the list by name, email, phone, or any text content - useful when only a subset of the spreadsheet should convert. Tick the checkboxes for selective conversion or leave them all checked for bulk.
03
3. Save as vCard
Click Export, pick vCard format, then in the Save dialog pick the vCard version (2.1, 3.0, or 4.0) for the target contact app, the output mode (single combined VCF or one VCF per contact), and the destination folder. Click Save. The wizard writes the output and reports completion with a count of converted contacts.
Software Compatibility
Source and Output Format Reference
Sources: six Excel file formats read through native parsers (XLSX, XLSM, XLSB via OOXML parser; XLS via BIFF parser; XLT, XLTX templates flattened to data rows). Microsoft Office not required on the conversion workstation. Outputs: three vCard versions (2.1 for legacy, 3.0 for cross-platform, 4.0 for modern Apple/Outlook), in two output modes (single combined VCF or per-contact VCF). Output VCF imports cleanly into iCloud, Google Contacts, Outlook, Thunderbird, Android Contacts, macOS Contacts, and any other vCard-aware contact manager.
Input File Formats / Servers
Specialized and Tested Across Every Common Email Source
The Excel to vCard Converter reads contact data from XLS, XLSX, XLSM, XLSB, XLT, XLTX spreadsheets through native OOXML and BIFF parsers. Microsoft Office is not required on the conversion workstation. Output writes to standard vCard format (2.1, 3.0, or 4.0) importable into iCloud, Google Contacts, Outlook, Thunderbird, Android Contacts, macOS Contacts, and any other vCard-aware contact manager.
Browse the full list of input file Excel file formats the converter reads, plus the three vCard output versions and target contact apps the converted output imports into.
Email File Formats8 formats
Format
Full Name
Type
Description
PSTInput & Output
Personal Storage Table
Microsoft Outlook
Primary Outlook data file containing emails, contacts, calendar, tasks, and notes.
OSTInput
Offline Storage Table
Microsoft Outlook
Offline cached copy of Exchange mailbox data. Supports inaccessible or orphaned OST files.
MBOXInput & Output
Mailbox Format
Thunderbird, Apple Mail, Eudora
Universal text-based mailbox format used by dozens of email clients and servers (see IETF RFC 4155 specification).
EMLInput & Output
Email Message
Multiple clients
Individual RFC 822 email message files. Widely supported by Windows Mail, Outlook Express, and others.
MSGInput & Output
Outlook Message
Microsoft Outlook
Single Outlook email message in Compound Document File format. Preserves all metadata.
OFTInput
Outlook File Template
Microsoft Outlook
Outlook email template files. PCDOTS converts OFT templates to any supported format.
OLMInput
Outlook for Mac Archive
Mac Outlook
Native archive format for Outlook on macOS. Contains emails, contacts, and calendar data.
DBXInput
Outlook Express Mailbox
Outlook Express
Legacy email storage format used by Microsoft Outlook Express (discontinued in 2006).
Desktop Email Clients9 clients
Email Client
Platform
Storage Format
Conversion Support
Microsoft Outlook
Windows / Mac
PST, OST, OLM
Full: emails, contacts, calendar, tasks, notes, attachments
Mozilla Thunderbird
Windows / Mac / Linux
MBOX
Full: all folders, subfolders, attachments, filters
Mailbird
Windows
Local profile store
Full: all mailbox data including multiple accounts
eM Client
Windows / Mac
Local database file
Full: messages, contacts, calendar, attachments
Mailspring
Windows / Mac / Linux
Local profile store
Full: all email data and account configurations
Postbox
Windows / Mac
MBOX
Full: Thunderbird-compatible MBOX format
Windows Live Mail
Windows
EML + WLMX
Full: all message folders and account data
Eudora
Windows / Mac
MBX (MBOX variant)
Full: legacy Eudora mailbox files
IceWarp
Windows / Linux
Proprietary
Full: direct IceWarp server data export
Cloud & Webmail Services7 services
Service
Type
Direction
Auth Method
Gmail / Google Workspace
Cloud Webmail
Input & Output
OAuth 2.0 / App Password
Microsoft Office 365
Cloud Business
Input & Output
OAuth 2.0 / Modern Auth
Yahoo Mail
Cloud Webmail
Input & Output
App-specific Password
iCloud Mail
Cloud Webmail
Input & Output
App-specific Password
Hotmail / Outlook.com
Cloud Webmail
Input & Output
OAuth 2.0
Google Takeout
Export Archive
Input
Takeout ZIP / MBOX
Any IMAP Server
Universal Protocol
Input & Output
IMAP / SSL / TLS
Email Servers5 servers
Server
Type
Storage Format
Notes
Zimbra
Open Source Server
Zimbra TGZ
Supports Zimbra Community & Enterprise editions
MDaemon
Windows Mail Server
MDaemon MAI
Direct MDaemon user folder access, no export needed
Kerio Connect
Business Mail Server
Kerio IMAP Store
Converts Kerio data stores directly without server access
Communigate Pro
Enterprise Server
Communigate CGP
Supports all Communigate mailbox folder structures
Lotus Notes / HCL
IBM/HCL Platform
NSF
Via intermediary conversion. Contact support for enterprise plans.
Output Destinations13 outputs
Output Format
Category
Best Used For
PST
Email File
Importing into Microsoft Outlook on any Windows PC
MBOX
Email File
Thunderbird, Apple Mail, Postbox, or any MBOX-compatible client
EML
Email File
Windows Mail, individual email archiving, or web uploads
MSG
Email File
Saving individual Outlook messages with full metadata
PDF
Document
Legal archiving, compliance, sharing non-editable email records
HTML
Document
Web-based email viewing, readable in any browser
CSV
Spreadsheet
Extracting email data for analysis in Excel or Google Sheets
vCard (VCF)
Contacts
Exporting contacts to any address book or CRM
ICS
Calendar
Exporting calendar events to Google Calendar, Apple Calendar
TXT
Plain Text
Simple archiving, text analysis, or importing into databases
Gmail
Cloud Service
Direct migration. Emails appear in Gmail inbox immediately
Office 365
Cloud Service
Direct migration to Microsoft 365 business mailboxes
IMAP Server
Protocol
Any IMAP-compatible server: Dovecot, Postfix, Exchange, etc.
Advanced Filters
What Else Conversion Surfaces Beyond Format Translation
Spreadsheets in the wild are messy. Real contact data ships with blank rows between record clusters, merged cells in the name column where someone accidentally clicked Merge, inconsistent column orders across sibling spreadsheets, and UTF-8 names that get mangled if the parser assumes Windows-1252. The wizard handles all four: blank rows skip silently, merged cells split back to component cells, column-order detection runs per-file (the parser reads the header row first to identify which column carries email vs phone vs address rather than assuming a fixed order), and UTF-8 stays UTF-8 throughout the read-parse-write pipeline.
vCard format selection has consequences that are not always obvious at conversion time. vCard 4.0 supports a richer property set (multiple LANG values per name, RELATED properties for spouse/manager/assistant relationships, GENDER, KIND for distinguishing person from organization), but importing 4.0 into older Outlook silently drops the rich properties. vCard 3.0 is the safe default for cross-platform import - every modern contact manager reads it. vCard 2.1 is for very old phones and legacy Outlook only. The version selector lives in the export dialog and is required, not optional.
Output mode matters as much as version. Single-VCF output puts every converted contact into one combined .vcf file - convenient for one-shot import into a contact app, but unwieldy for selective use. Per-contact-VCF output writes one .vcf per row to a destination folder - more files to manage, but each contact stays as a discrete unit (useful for archival systems, per-contact attachment to client records, or staged import where the analyst wants to spot-check before bulk import). The Save dialog asks for output mode explicitly.
PCDOTS Excel to vCard Converter v1.0
Smart Search
Why Users Switch to PCDOTS
Five Excel-to-vCard Problems and How the Wizard Solves Them
Excel-to-vCard conversion runs into specific problems that other spreadsheet workflows do not. The CSV round-trip mangles UTF-8 names. Outlook contact import refuses non-fixed column orders. Imports silently drop fields when vCard versions mismatch. Five problems that show up across conversion tickets and how this wizard handles each.
Problems You're Facing
CSV round-trip mangles UTF-8 namesImprovised conversion via Save-As CSV from Excel + free CSV-to-VCF tools loses non-ASCII characters during the CSV write. Names like Garcia, Muller, Lofgren come out garbled in the destination contact app. The wizard reads the Excel source directly in UTF-8 throughout the parse-write pipeline. Excel cell values stay byte-identical from spreadsheet through vCard output - non-ASCII names land cleanly in iCloud, Google, Outlook regardless of locale.
Outlook contact import refuses non-fixed column orderOutlook's built-in contact import requires a specific column order in the source spreadsheet (First Name, Last Name, Email, etc.) and refuses files where the columns are arranged differently. Real contact spreadsheets rarely match that fixed layout. The wizard does per-file column-order detection by reading the header row first to identify which column carries which property, then maps to standard vCard fields regardless of source column position.
Imports silently drop fields when vCard versions mismatchWhen the converter outputs vCard 4.0 but the target is older Outlook (which expects 2.1 or 3.0), the import succeeds but quietly drops 4.0-only properties (RELATED relationships, GENDER, KIND). The contact appears in the address book missing fields that were in the source spreadsheet. The wizard surfaces the version selector explicitly in the Save dialog with notes on which target apps prefer which version, so version mismatch becomes a deliberate choice rather than a silent loss.
Multiple spreadsheets need to consolidate into one VCFContact data scattered across multiple spreadsheets - one per region, quarter, or import batch - is a recurring consolidation request. Loading each spreadsheet individually and running separate conversions then merging the VCF outputs in a text editor is fragile and error-prone. Folder mode in the wizard's Open dropdown ingests an entire directory of spreadsheets in one load, combines all contact rows into a unified pane, and exports one combined VCF or per-contact VCFs in a single operation.
Field mapping ends up as generic notes blobCheap CSV-to-VCF converters dump every spreadsheet column into the vCard NOTE property as a comma-separated string. The destination contact app shows one giant note blob instead of structured fields. Sorting by phone, searching by company, calling from caller-ID becomes useless. The wizard does structured property mapping: each Excel column maps to its corresponding standard vCard property (FN, N, EMAIL, TEL with TYPE qualifiers, ADR with subfields, ORG, TITLE, URL). Output is structured contact records.
How PCDOTS Fixes It
Native Excel parsing without Office requiredWizard ships its own OOXML parser for XLSX/XLSM/XLSB and its own BIFF parser for legacy XLS. Office is never required on the conversion workstation. UTF-8 stays UTF-8 throughout the parse-write pipeline. Useful for analyst workstations under licensing constraints that forbid Office, for fresh forensic builds where Office is intentionally absent, and for one-off conversions on machines that never had Office installed.
Header-row detection across varied column ordersWizard reads the header row of each loaded spreadsheet to identify which column carries name, which carries email, which carries each phone-number type. Column order does not need to match a fixed layout. Sibling spreadsheets with different column orders all map to the same standard vCard properties. Useful for consolidation projects where contact data has fragmented across years of separate tracking files with their own conventions.
Direct MBOX to Gmail migration in a single click.Connect your Gmail account inside the converter. PCDOTS pushes the messages straight into your inbox without a download and re-upload step.
Explicit vCard version selector in the Save dialogvCard 4.0 for iPhone Contacts, modern macOS Contacts, latest Outlook. vCard 3.0 for Google Contacts, Android, mid-vintage clients - the safe cross-platform default. vCard 2.1 for legacy phones, very old Outlook, BlackBerry. The selector lives in the export dialog with descriptive labels indicating which target apps prefer which version. Picking the right version up front prevents silent field-drop on import.
Folder mode handles multi-spreadsheet consolidationOpen > Choose Folders points the wizard at a directory of contact spreadsheets and ingests every Excel file inside it (XLS, XLSX, XLSM, XLSB, XLT, XLTX). All contact rows from every spreadsheet appear in a unified navigation pane. Quick Search filters across the combined corpus. Export produces one combined VCF or one VCF per contact - whichever shape the destination import workflow wants.
Real-World Applications
Six Scenarios Where Excel-to-vCard Conversion Matters
Contact data tends to live in spreadsheets longer than it should, then someone needs it in an actual contact app and the conversion problem surfaces. Sales teams with prospect lists, HR teams with employee directories, event teams with attendee rosters, IT helpdesks with department phone books, and analysts fetching contact data out of forensic exports - six scenarios that recur across the support ticket queue.
Sales Team Imports Prospect Lists Into CRM
A sales team gets a fresh prospect spreadsheet from marketing - 2,000 leads with name, email, phone, company, job title columns. The CRM (Salesforce, HubSpot, Pipedrive) accepts vCard import for contact entry. The wizard converts the entire 2,000-row spreadsheet to a single combined VCF in one pass, the sales lead drags the VCF into the CRM contact import dialog, and every prospect lands in the system with all fields populated.
PST to Office 365Exchange migration
HR Migrates Employee Directory to Outlook Contacts
HR maintains the company directory in an Excel sheet (employee name, work email, work phone, department, office location, manager). When the directory needs to land in everyone's Outlook Global Address List or in individual employee Outlook contact folders, the wizard converts the spreadsheet to one VCF per employee in a destination folder. Outlook contact import dialog points at the folder and ingests the entire directory in one operation.
PDF exportGDPR compliance
Event Team Pushes Attendee List to Phone Contacts
An event organizer has the attendee roster in Excel - 500 attendees with name, email, phone, badge category. The lead organizer wants every attendee saved to their iPhone contacts before the event so caller ID works for incoming questions. The wizard converts the spreadsheet to a vCard 4.0 single combined file, the organizer emails the .vcf to themselves, opens it in iOS Mail, and iOS imports all 500 contacts in a single tap.
Corrupted PSTForensic recovery
IT Helpdesk Pushes Phone Book to Android Devices
A helpdesk maintains the on-call rotation phone book in Excel (engineer name, mobile, role, escalation tier). When new on-call engineers join, IT needs the full phone book on their Android work phone. The wizard converts the spreadsheet to vCard 3.0 (best Android compatibility), pushes the .vcf via MDM or shared drive, and the engineer imports it into Android Contacts - now everyone in the rotation appears with caller ID enabled.
MBOX to PSTEML to MSG
Forensic Analyst Extracts Contacts From Seized Spreadsheet
A seized workstation contains a contact spreadsheet relevant to a case - employee directory, client list, vendor contacts. The analyst needs a structured contact-database copy for case-management systems that consume vCard, not loose Excel rows. The wizard reads the spreadsheet on a clean forensic build (no Office installed), converts to per-contact VCF files, and the analyst attaches each VCF to the relevant case-management record as discrete contact evidence.
HIPAAHealthcare archives
Multi-Source Spreadsheet Consolidation
Contact data scattered across multiple spreadsheets - one per region, one per quarter, one per data source. Folder mode in the Open dropdown ingests the entire directory of spreadsheets in a single load, the wizard combines all contact rows into a unified navigation pane, and a single export produces one combined VCF (or one VCF per contact, depending on the target import workflow). Useful for consolidation projects where the contact data has fragmented across years of separate tracking files.
Contact extractionCRM enrichment
Why Customers Choose This Tool
Why This Wizard Beats Improvised Conversion Workflows
Excel-to-vCard conversion attempts split across three improvised workflows that fall short. Save-As CSV from Excel + free CSV-to-VCF converter loses field-mapping precision (everything becomes generic NOTE properties). Outlook contact import from Excel requires Office installed and only handles a fixed column layout. Manual one-by-one VCF authoring is unworkable past 20 contacts. Eight architectural decisions that distinguish a proper Excel-to-vCard tool from these improvised paths.
Direct Excel Parsing With No Office Required
Improvised Save-As CSV from Excel requires Office installed on the conversion workstation, requires the user to manually open each spreadsheet, and silently truncates UTF-8 characters in the CSV stream. The wizard ships its own OOXML parser for XLSX/XLSM/XLSB and its own BIFF parser for legacy XLS. Office is never required. UTF-8 stays UTF-8 throughout. The user points the wizard at the source Excel file directly without a Save-As round-trip.
Six Excel Formats Read Through Native Parsers
Excel ships at least six file extensions in active use across the install base: XLSX (Office 2007+), XLSM (macro-enabled XLSX), XLSB (binary XLSX), XLS (legacy Office 97-2003), XLT (legacy template), XLTX (modern template). The wizard reads all six. Templates flatten to data rows. Macro content gets ignored (security-safe). Binary XLSB is parsed natively rather than refused. One tool for every spreadsheet variant in the wild.
Three vCard Versions Surfaced Explicitly
Improvised converters often pick a single vCard output version and hide the choice. The wizard surfaces vCard 4.0 / 3.0 / 2.1 explicitly in the Save dialog because version mismatch silently drops fields during import. vCard 4.0 for iPhone, modern macOS, latest Outlook. vCard 3.0 for Google, Android, mid-vintage clients (the safe cross-platform default). vCard 2.1 for legacy phones, old Outlook, BlackBerry. The version selector is required, not optional.
Field-Level Mapping, Not Generic NOTE Dump
Cheap CSV-to-VCF converters take every Excel column and dump it into the vCard NOTE property as a single comma-separated string. The wizard does structured field mapping: name columns → FN/N, email → EMAIL, phone columns → TEL with TYPE qualifiers (CELL, WORK, HOME, FAX), address → ADR with subfields (street, city, region, postal code, country), organization → ORG, job title → TITLE, web URL → URL, free-text only → NOTE. Importing the output into a contact app produces structured contacts, not blob records.
Two Output Modes for Different Import Targets
Different import workflows want different output shapes. Single combined VCF puts every contact into one .vcf file - convenient for one-shot import into iCloud, Google Contacts, or Outlook contact import dialogs. Per-contact VCF writes one .vcf per contact row to a destination folder - useful for archive systems, per-contact attachment to client records, or staged import where the analyst spot-checks before bulk import. The Save dialog picks output mode at export time.
Preview Before Conversion Catches Bad Source Data
Real-world contact spreadsheets contain blank rows between record clusters, merged cells in the name column from someone clicking Merge by mistake, inconsistent column orders across sibling files, duplicate rows from prior imports. The wizard's preview pane surfaces every loaded contact in tabular form before the user commits to conversion. Bad rows show up immediately - the user can either fix the source spreadsheet, exclude bad rows via checkbox selection, or proceed and accept the noise. Preview prevents bad output.
Quick Search Across Loaded Contact Corpus
Spreadsheets with thousands of contact rows make manual scrolling impractical. Quick Search at the top of the navigation pane filters loaded rows by name, email, phone, organization, or any text match. Advanced Search exposes per-column structured filters with combinations. Useful for selective conversion (only contacts matching a company domain, only contacts with a phone number, only contacts in a specific region) rather than bulk conversion of the entire spreadsheet.
Compatible Windows 7 Through Windows 11
Wizard runs on Windows 11, 10, 8.1, 8, 7, Vista, XP and Windows Server 2008/2012/2016/2019/2022. .NET 4.5 is the only runtime requirement. Useful for one-off conversions on legacy hardware where modern Office cannot install but contact spreadsheets still exist, for analyst lab workstations running older Windows builds for tool compatibility, and for IT field service technicians carrying conversion utilities on a USB stick for on-site work.
Technical Specs
System and Software Requirements
What you need to run the Excel to vCard Converter for Windows, plus the trial limitations.
Software Name
PCDOTS Excel to vCard Converter
Current Version
3.4
Processor
Pentium-class or higher
RAM
Minimum 2 GB
Hard Drive Space
100 MB free space
Operating System
Windows 11, 10, 8.1, 8, 7, Vista, XP. Server 2019, 2016, 2012, 2008, 2003 and earlier.
Trial limitation: the demo edition converts up to 10 contacts per spreadsheet file; all Excel formats and vCard versions work without restriction during evaluation so you can verify accuracy on real data before purchasing. The full edition has no limits and ships with a lifetime license.
Trial vs Full
Trial vs Licensed Edition for Conversion Work
Trial and licensed editions ship the same binary - identical Excel parsing across all six formats, identical vCard output across all three versions, identical field-mapping logic, identical preview pane and Quick Search. Trial caps conversion at 10 contacts per spreadsheet file for evaluation; everything else works without restriction so the analyst can verify the wizard handles the specific Excel layout, that the chosen vCard version imports cleanly into the target app, and that field mapping picks the right columns. Licensed edition is $29 one-time per workstation, perpetual, includes lifetime updates and 24x7 support. Multi-seat business licenses available on request for sales teams running conversion across multiple workstations.
Excel-to-vCard tools split across three improvised paths and one proper category. Save-As CSV + free CSV-to-VCF converter mangles UTF-8 and dumps fields into NOTE properties. Outlook contact import from Excel requires Office installed plus a fixed column layout. Manual one-by-one VCF authoring is unworkable past 20 contacts. Standalone Excel-to-vCard tools include PCDOTS plus a few smaller utilities - the matrix below isolates this category and surfaces capability differences.
Feature
Best ChoicePCDOTS
Other Paid ToolsAid4Mail, Stellar, etc.
Free Tools / Online
Six Excel Formats Read Natively
25+
10 to 40+
2 to 5
No Microsoft Office Required
Yes
Partial
No
Bulk Convert Entire Spreadsheet
Yes
Yes
No
Output to iCloud, Google, Outlook, Android
Yes
Partial
No
Contact Preview Before Conversion
Yes
Partial
No
Three vCard Versions (2.1 / 3.0 / 4.0)
Yes
Partial
No
Quick Search and Advanced Filters
Yes
Limited
No
Structured Field Mapping (Not Notes Blob)
Yes
Partial
No
Free Trial Available
Yes
Yes
Yes
Lifetime License
Yes
No
N/A
UTF-8 Names Stay Intact
Yes
Varies
No
24x7 Customer Support
Yes
Limited
No
30-Day Refund Policy
Yes
Varies
N/A
Starting Price
$29
$29 to $149+
Free (limited)
Matrix sourced from competitor product documentation as of October 2025. Standalone field includes the few proper Excel-to-vCard utilities published as commercial Windows desktop tools; cells reflect each vendor's stated capability. Improvised paths (Save-As CSV + free CSV-to-VCF, Outlook contact import from Excel, manual one-by-one VCF authoring) excluded since they are not standalone products. Reviewer count: 3,100 verified responses across G2, Capterra and Trustpilot.
Video Tutorial
See the Conversion Workflow in Action
A short walkthrough of the Excel-to-vCard conversion workflow: loading a source spreadsheet through the OOXML parser, previewing contact rows in the navigation pane, picking the vCard version (2.1/3.0/4.0) and output mode (single combined or per-contact), and saving the converted VCF output to a destination folder.
5 min walkthrough
YouTube
Real Performance Numbers
Excel-to-vCard Conversion Performance Reference
Two data sources feed the numbers below. The first is internal regression test runs against synthetic contact spreadsheets across all six Excel formats, with import-success verification against iCloud, Google Contacts, Outlook, and Thunderbird as target contact apps. Field-mapping correctness measured against ground-truth column-to-property reference. The second is post-conversion operator survey responses (3,100 valid responses) reporting on field-population accuracy and target-app import success against actual conversion tickets.
85%
Customer Satisfaction
93%
Output Accuracy
99%
Successful Test Runs
How It Works
Eleven-Step Excel-to-vCard Conversion Walkthrough
The walkthrough below covers every dialog the wizard puts in front of the operator from launch through verified VCF output, with the matching screenshot for each step. Total time per conversion ranges from a few seconds (small spreadsheet, single source) to a couple of minutes (10,000-row spreadsheet, folder mode across multiple sources, with Quick Search filtering).
Launch the Excel to vCard Converter
Run the wizard from the Start menu shortcut or desktop icon. The application opens with the source-selection panel and the Open button at the top of the toolbar. Navigation pane on the left stays empty until a spreadsheet is loaded; preview pane on the right also stays empty.
Pick Files or Folders From the Open Menu
Click Open. The dropdown offers two options: Choose Files for individual spreadsheets (file picker accepts XLS, XLSX, XLSM, XLSB, XLT, XLTX) or Choose Folders for a directory of spreadsheets (every Excel file inside the directory ingests in one operation). Folder mode is the right pick for multi-source consolidation; Choose Files is right for a single source.
Browse to the Source Spreadsheet
File picker (or folder picker for folder mode) opens. Browse to the source location, select the file(s) or folder, click Open. The wizard reads the spreadsheet through its built-in OOXML parser (XLSX/XLSM/XLSB) or BIFF parser (legacy XLS) - Microsoft Office is not required. Header row is detected automatically; column-to-property mapping is established at this stage.
Preview the Loaded Contact Rows
Loaded contacts render in the navigation pane as a tabular list with name, email, phone, organization, and other fields visible inline. Click any row to see the full contact in the preview pane with all fields rendered. Field mapping (which Excel column became which vCard property) is shown explicitly so the user can verify before committing to conversion.
Run Quick Search Across the Loaded Corpus
Quick Search at the top of the navigation pane filters the loaded contact rows by name, email, phone, organization, or any text content. Useful for finding specific contacts in a large spreadsheet. Advanced Search exposes per-column structured filters with combinations - useful for selective conversion (only contacts matching a company domain, only contacts with a phone number, only contacts in a specific region).
Tick the Checkboxes for Selective Conversion
Each contact row carries a checkbox in the navigation pane. Default state: all rows checked (full bulk conversion). For selective conversion, untick the rows that should not convert, or use Quick Search/Advanced Search to filter to a subset and tick only the matching rows. Conversion only processes checked rows. Useful when the source spreadsheet has rows that should not land in the target contact app.
Click Export and Pick vCard
Click Export in the toolbar. Dropdown lists output formats. Pick vCard. The Save dialog opens with the vCard-specific options: vCard version selector (2.1 / 3.0 / 4.0), output mode selector (single combined VCF or one VCF per contact), destination folder picker, and file naming options for per-contact mode (default: contact name as filename).
Pick the vCard Version for the Target App
Version selector in the Save dialog. vCard 4.0 for iPhone Contacts, modern macOS Contacts, latest Outlook (richest property set). vCard 3.0 for Google Contacts, Android, Thunderbird, mid-vintage clients (the safe cross-platform default). vCard 2.1 for legacy phones, very old Outlook, BlackBerry (smallest property set, ASCII-safe). Picking the wrong version causes silent field-drop on import - the dialog shows descriptive labels for each version's typical target app.
Pick Output Mode and Browse Destination
Single combined VCF (every contact in one .vcf file - convenient for one-shot import) or per-contact VCF (one .vcf per row to a destination folder - useful for archive systems or staged import). Browse to the destination folder. For per-contact mode, the file-naming option determines how each .vcf gets named (default: contact's full name; alternatives: row number, email address, employee ID).
Click Save to Begin Conversion
Click Save. The wizard begins writing converted vCards to the destination. Live progress report shows contacts converted, files written, time remaining. Trial edition caps at 10 contacts per source file; licensed wizard converts unlimited counts. Conversion typically completes in seconds for spreadsheets with up to a thousand contacts; larger spreadsheets (10,000+ rows) may take a minute or two.
Verify the VCF Output in the Target App
When conversion finishes, the wizard's Open folder when complete toggle (default ON) opens the destination in Windows Explorer. Verify the output: file count matches converted-contact count for per-contact mode, single combined VCF size looks reasonable for combined mode. Test-import one contact into the target app (iCloud, Google, Outlook) to confirm fields populate correctly. If anything looks off, rerun the wizard against the same source with a different vCard version - source spreadsheet stays untouched.
Independent Validation
Reviewed and Awarded by Trusted Software Sites
Independent third-party verification of PCDOTS Excel to vCard Converter against documented contact-conversion criteria - Excel format coverage breadth, vCard version flexibility, field-mapping fidelity, and import success rate against major target contact apps (iCloud, Google Contacts, Outlook, Thunderbird, Android). Each award sources from the original publisher (Software Informer, Softpedia, Soft32, FileHippo). The aggregate 4.9-star rating combines 3,100 verified reviewer responses since the most recent major release.
4.6
Average across all reviews
1,408
Verified user reviews
4
Editor's Choice awards
Editor's Pick
5.0
Software Informer
"100% Clean Award for error-free and virus-free email conversion across formats and sources."
100% Clean Award
5-Star Rated
5.0
Softpedia
"Earns a 5-star rating for ease of operation and smooth email conversion."
100% Free Award
Top Rated
4.5
Soft32
"4.5 stars: an all-in-one solution for converting email files to multiple output formats."
Editor's Review
Verified Safe
5.0
FileHippo
"100% Clean Award for secure and safe email conversion."
Safety Verified
100% authentic. Every award above is verified directly from the issuing publisher's site. PCDOTS does not pay for placement, reviews or ratings.
Quick Definition
What Is the Excel to vCard Converter?
Excel to vCard Converter is a desktop tool that reads contact data from Microsoft Excel spreadsheets and writes the contacts as standard vCard (VCF) files importable into iCloud, Google Contacts, Outlook, Thunderbird, Android Contacts, and any other vCard-aware contact manager. PCDOTS Excel to vCard Converter reads six Excel formats (XLS, XLSX, XLSM, XLSB, XLT, XLTX) through native OOXML and BIFF parsers without requiring Microsoft Office installed. Output writes in vCard 2.1, 3.0, or 4.0 format depending on the target contact app, with structured field mapping (FN, N, EMAIL, TEL with TYPE qualifiers, ADR with subfields, ORG, TITLE, URL, NOTE) rather than generic notes-blob dumping.
Quick Verdict
Best for: Bulk Excel-to-vCard contact conversion on Windows for sales teams importing prospect lists into CRM contact apps, IT helpdesks migrating user contact lists from spreadsheet to Outlook/Google, and analysts consolidating multi-source contact data into a single VCF for archive or staged import.
Free trial: converts 10 contacts per spreadsheet file; all Excel formats and vCard versions unrestricted during evaluation.
Price: $29 one-time payment for a lifetime license; multi-seat business licenses available on request.
Platforms: Windows 11, 10, 8.1, 8, 7, Vista, XP and Windows Server 2008-2022.
Rating: 4.9 out of 5 from 3,100 verified reviews on G2, Capterra and Trustpilot.
Privacy: all conversion runs locally; spreadsheet content does not transit PCDOTS infrastructure at any point during conversion.
FAQs
Excel-to-vCard Conversion Reference Questions
Twelve reference questions covering Excel-to-vCard conversion: vCard knowledge (what is a vCard, version differences, version selection by target app, supported Excel formats), conversion procedures (bulk, multi-spreadsheet, selective rows), capabilities (no-Office requirement, output modes, field mapping), and the trial / pricing details. Sourced from real conversion-ticket support requests.
Which Excel file formats does the wizard read?
Six Excel formats read through native parsers: XLSX (Office 2007 and later, zipped XML bundle - the modern default), XLSM (macro-enabled XLSX, macros ignored for security), XLSB (binary XLSX, faster for very large spreadsheets), XLS (legacy Office 97-2003, binary BIFF stream), XLT (legacy template, flattened to data), XLTX (modern template, flattened to data). Microsoft Office is not required on the conversion workstation - the wizard ships its own OOXML and BIFF parsers and reads each format directly.
What is a vCard and what's it used for?
A vCard (.vcf file) is the standard contact-data interchange format that every modern contact app reads. iPhone Contacts, Google Contacts, Outlook, Thunderbird, Android Contacts all import vCards directly. A single VCF file contains one or more contact records with structured fields: full name, email address, phone numbers (mobile, work, home, fax), postal address, organization, job title, web URL, photo, notes. Email a VCF to someone and their contact app imports it on tap; drag a VCF into the contact app's import dialog and the contacts land in their address book.
How do I bulk convert an entire spreadsheet?
Click Open, pick Choose Files, browse to the source spreadsheet, click Open. The wizard parses the spreadsheet and lists every contact row in the navigation pane. Click Export, pick vCard format, in the Save dialog pick the vCard version (2.1, 3.0, or 4.0) for the target contact app, pick output mode (single combined VCF or per-contact VCFs), browse to the destination folder, click Save. The wizard converts every checked row in one pass and reports the converted-contact count when complete.
How do I convert multiple spreadsheets at once?
Use folder mode. Click Open, pick Choose Folders, point the wizard at a directory containing the source spreadsheets. Every supported Excel file inside the directory (XLS, XLSX, XLSM, XLSB, XLT, XLTX) gets ingested in one operation. All contact rows from every spreadsheet appear in a unified navigation pane. Quick Search filters across the combined corpus. Export produces one combined VCF (every contact across every source spreadsheet) or one VCF per contact, depending on the destination import workflow's preferred shape.
Which vCard version should I pick for my target app?
iPhone Contacts: pick 4.0 (best fidelity) or 3.0 (safe). Google Contacts: pick 3.0 (preferred). Android Contacts: pick 3.0 or 4.0 (both read cleanly on modern Android; 2.1 only for very old devices). Outlook: 3.0 is the safe default; 4.0 reads on latest Outlook but older Outlook drops 4.0-only fields silently. Thunderbird address book: 3.0 preferred. Cross-platform unknown target: pick 3.0 - widest compatibility, no version-specific field loss. The wizard surfaces all three in the Save dialog with descriptive labels.
What does the free trial convert?
Trial edition converts 10 contacts per spreadsheet file - enough to verify the wizard handles your specific Excel layout successfully, that the field mapping picks the right columns, that the chosen vCard version imports cleanly into the target contact app. All Excel formats read in the trial. All vCard output versions (2.1, 3.0, 4.0) work in the trial. Both output modes (single combined VCF, per-contact VCFs) work in the trial. Quick Search and Advanced Search work without restriction. The 10-contact-per-file cap is the only restriction.
What's the difference between vCard 2.1, 3.0, and 4.0?
Three published versions of the vCard standard exist. vCard 2.1 (1996): smallest property set, ASCII-safe, used by very old phones, legacy Outlook, BlackBerry. vCard 3.0 (RFC 2426, 1998): adds UTF-8, used by Google Contacts, Android, mid-vintage contact managers - the widest cross-platform compatibility. vCard 4.0 (RFC 6350, 2011): richest property set (RELATED relationships, GENDER, KIND, multiple LANG values), used by iPhone Contacts, modern macOS, latest Outlook. Newer is not always better - importing 4.0 into older Outlook silently drops the rich properties.
Single combined VCF or one VCF per contact?
Both modes ship; pick at export time based on target import workflow. Single combined VCF writes every converted contact into one .vcf file - convenient for one-shot import into iCloud, Google Contacts, or Outlook contact import dialogs (one drag-and-drop, every contact lands). Per-contact VCF writes one .vcf per row to a destination folder - more files to manage, but each contact stays as a discrete unit (useful for archive systems, per-contact attachment to client records, or staged imports where the analyst spot-checks before bulk import).
Does the converter keep all my contact fields?
Yes, with structured field mapping not generic notes-blob dumping. Each Excel column maps to its corresponding standard vCard property: name → FN/N, email → EMAIL, phone columns → TEL with TYPE qualifiers (CELL, WORK, HOME, FAX), address → ADR with structured subfields (street, city, region, postal code, country), organization → ORG, job title → TITLE, web URL → URL, free-text only → NOTE. Multi-value fields (multiple phone numbers per contact) get separate TEL properties rather than concatenation. Field mapping is shown explicitly during preview before commit.
How do I convert only specific rows from a spreadsheet?
Two approaches. Quick Search at the top of the navigation pane filters loaded rows by name, email, phone, organization, or any text content. Advanced Search exposes per-column structured filters with AND/OR combinations. Once filtered, only the matching rows appear in the navigation pane. Tick the checkboxes for rows that should convert (or click Select All within the filtered view), click Export, and the conversion only processes the checked rows. Useful for selective import scenarios where only a subset of the spreadsheet should land in the target contact app.
How much does the licensed edition cost?
Licensed edition is $29 one-time, perpetual, single workstation, no recurring subscription fees. License covers lifetime updates and 24x7 support. Multi-seat business licenses available on request for sales teams running conversion across multiple workstations, with corresponding volume pricing. Refund policy is 30 days, no questions asked. Wizard runs on Windows only - 32-bit and 64-bit, Windows 7 through Windows 11, plus Windows Server 2008/2012/2016/2019/2022 for server-side conversion work. macOS and Linux are not supported.
Do I need Microsoft Office installed?
No. The wizard ships its own Excel parsers and reads XLS/XLSX/XLSM/XLSB/XLT/XLTX directly without Office on the workstation. The OOXML parser handles XLSX/XLSM/XLSB (zipped XML bundle, SharedStrings table, cell-reference resolution); the BIFF parser handles legacy XLS (binary record stream, SST records, sheet metadata). Useful for analyst workstations under licensing constraints that forbid Office, for fresh forensic builds where Office is intentionally absent, and for one-off conversions on workstations that never had Office installed.
Customer Stories
Three Conversion Outcomes From the Field
Three accounts from operators running Excel-to-vCard conversion in different scenarios: a 2,400-row prospect spreadsheet pushed into a CRM in 15 minutes, a 500-attendee conference roster on iPhones via single-tap import, a 12-year-old legacy XLS contact list rescued from an XP-era workstation during decommissioning. Reviewer accounts hosted independently on G2, Capterra, and Trustpilot.
G2 Reviews
4.7
412 reviews
Capterra
4.6
287 reviews
Trustpilot
4.6
521 reviews
Software Suggest
4.5
188 reviews
"
"Pushed 2,400 leads from spreadsheet to CRM in fifteen minutes."
Marketing handed us a 2,400-row prospect spreadsheet on a Friday afternoon - 15 columns of contact data per row, mixed XLSX and XLS files from three different campaign sources. Sales lead wanted everyone in our HubSpot CRM by Monday morning standup. Tried the obvious paths first: Save-As CSV from Excel mangled half the German and Spanish names, Outlook contact import refused our column order, the free CSV-to-VCF converter we tried put every field into a single notes blob. Switched to PCDOTS Excel to vCard. Folder mode ingested all three source spreadsheets in one operation. Field mapping auto-detected from header rows and put each Excel column into the right vCard property. Picked vCard 3.0 for HubSpot compatibility, single combined VCF output, dragged the .vcf into HubSpot's contact import. Every prospect landed with name, email, phone, company, title, and notes populated correctly. Total time from spreadsheet to imported CRM contacts: about fifteen minutes.
vCard 3.0 to HubSpot2,400 contacts convertedFolder mode 3 sources
GF
Marisa OkaforSales Operations Lead · Lagos, Nigeria
Verified review · G2
Pushed event roster to 500 iPhone contacts in one tap
Annual conference, 500 attendees, lead organizer wanted everyone's contact in their iPhone before opening keynote so caller ID would work for incoming questions. Source was an Excel registration export with 22 columns per attendee. Converted to vCard 4.0 single combined file via PCDOTS, emailed the .vcf to my iPhone, opened it in iOS Mail, hit Add All Contacts. All 500 attendees landed in iPhone Contacts with name, email, phone, company, badge category populated. Done in about three minutes.
500 attendeesvCard 4.0 to iPhone
KJ
Pierre CaronConference Organizer · Lyon, France
Verified · Capterra
Salvaged contact spreadsheet from XP-era workstation
We were decommissioning a Windows XP workstation that had a 12-year-old Excel 2003 .xls file with our entire vendor contact list - the only authoritative source. Modern Office could not open the file (legacy encryption flag). PCDOTS Excel to vCard read the legacy XLS through its BIFF parser without trouble, converted 380 vendor contacts to vCard 3.0, imported cleanly into our current Outlook on Windows 11. Vendor list preserved, XP workstation safely decommissioned.
Convert Your Excel Contacts to vCard Today. Trial Edition, No Card Required.
Download PCDOTS Excel to vCard Converter, convert up to 10 contacts per spreadsheet file and verify the wizard handles your exact column layout successfully. Upgrade only when you are satisfied with the result.
