★ 4.6 / 5
from 1,408 verified reviews on G2, Capterra and Trustpilot
CSV to vCard Tool For Contacts File
Contact data lands in CSV form for one reason - somebody exported it from a spreadsheet, a CRM, or an old database table. The migration to a phonebook then waits on a schema shift: rows become cards, columns map to vCard properties (FN, N, TEL, EMAIL, ADR, ORG), and the output gets a version stamp (vCard 2.1 for legacy phones, 3.0 for safe interoperability, 4.0 for modern apps). The PCDOTS CSV to vCard Converter handles every step of that schema-shift story on Windows.
The migration story has three acts. The CSV side: the wizard reads spreadsheet rows where each row holds one contact and each column holds one property (name, phone, email, organization). The mapping layer: each CSV column maps to a corresponding vCard property - first name and last name combine into the FN field, the phone column lands in TEL, the email column lands in EMAIL. The vCard side: the output ships in vCard 2.1, 3.0, or 4.0 format, with single-VCF or per-contact-VCF packaging.
Reading the CSV Source
Source CSVs come from many places - Google Contacts exports, Outlook address book exports, CRM database dumps, manual spreadsheet entries. The wizard reads each variation as RFC 4180 comma-separated values, detects whether the file uses UTF-8 (with or without BOM) or ASCII encoding, and identifies the header row from column names like Name, Phone, Email, Address. Two ingestion modes available: Choose Files for individual CSVs or Choose Folders for batch ingestion of an entire folder.
Choose Files: individual CSV selection
Choose Folders: batch ingestion mode
Header row auto-detected from column names
Mapping Columns to vCard Properties
The schema shift happens row by row. First name + last name columns combine into the vCard N structured-name property and FN formatted-name property. Phone columns map to TEL with TYPE parameters retaining home-vs-work distinctions. Email maps to EMAIL. Address columns compose into ADR with structured fields for street, city, region, postal code, country. Organization and title map to ORG and TITLE. Mappings stay editable in the dialog before commit.
Name columns map to N and FN properties
Phone columns map to TEL with TYPE parameters
Address columns compose ADR structured field
Writing the vCard Output
Output ships in one of three vCard versions. vCard 2.1: 1996 Versit format, legacy phones and embedded systems, quoted-printable encoding for non-ASCII. vCard 3.0: 2001 RFC 2426, the safest interoperability target, accepted by every major platform (iCloud, Google Contacts, Outlook, Thunderbird). vCard 4.0: 2011 RFC 6350, mandatory UTF-8, modern XML/JSON alternatives, includes KIND/GENDER/ANNIVERSARY properties. Output mode picks between a single combined VCF or one VCF per source row.
vCard 2.1 / 3.0 / 4.0 version selector
Single combined VCF output mode
Per-contact VCF output (one file per row)
vCard 2.1 for Legacy Phone Compatibility
vCard 2.1 dates back to the 1996 Versit specification. The format predates UTF-8 standardization, so non-ASCII characters get quoted-printable encoding (each byte represented as =XX hex). Most legacy feature phones, older Android devices (pre-2015), and embedded contact systems require this version specifically. The wizard outputs a clean 2.1 file with proper quoted-printable for accented characters and the bare TYPE parameter syntax these older systems expect.
vCard 3.0 for Maximum Interoperability
vCard 3.0 is the 2001 RFC 2426 standard and the safest interoperability target across iCloud, Google Contacts, Outlook, Thunderbird, Android, iPhone, and most CRM systems. Plain UTF-8 throughout (no per-property CHARSET declarations), the TYPE= parameter syntax, and clean ENCODING=b for embedded photos. When a contact list is going to multiple destinations and the operator does not know which ones, vCard 3.0 is the conservative pick that just works.
vCard 4.0 for Modern Apps and KIND Property
vCard 4.0 shipped in 2011 as RFC 6350. UTF-8 is mandatory (no exceptions), and the format adds new properties unavailable in earlier versions: KIND (individual, group, organization, location), GENDER, ANNIVERSARY, RELATED, plus the LANGUAGE parameter for multilingual contact cards. Modern contact apps that distinguish between people and groups, or that store anniversary alongside birthday, need vCard 4.0 specifically.
Single Combined VCF or Per-Contact VCF
Two output modes for two different downstream import paths. Single combined VCF: every contact lands in one .vcf file with a sequence of BEGIN:VCARD / END:VCARD blocks. Useful for bulk import to address books that accept multi-contact files (iCloud, Google Contacts). Per-contact VCF: one .vcf file per source CSV row. Useful for distributing individual contact cards via email attachment, embedding in HTML pages, or archiving in folder-per-contact structures.
Five Encoding Options for Output Files
The encoding dropdown lets the operator override the version default when a target platform demands a specific encoding. Options: Default (the version-appropriate encoding - quoted-printable for 2.1, UTF-8 for 3.0 and 4.0), ASCII (drops non-ASCII characters cleanly for legacy systems), UTF-7 (rare 7-bit safe encoding for restricted email gateways), UTF-8 (the modern default), and UTF-32 (fixed-width 4-byte encoding for systems that need uniform character width).
Compact View Hides System Folders
Windows folder pickers default to showing every system folder - AppData, ProgramData, Recovery partitions - which clutters the source-folder selection step when the actual source CSVs sit in Documents or a network share. Compact view toggle hides system folders during the Choose Folders flow, leaving only user-accessible folders visible. Reduces the cognitive load of navigating the folder tree, especially on workstations with many installed applications creating their own AppData subfolders.
3vCard versions output
5Encoding options available
100%Contact field migration
1,258Verified user reviews
Simple 3-Step Process
Three Phases from CSV Source to vCard Output
The CSV load, the version pick, the vCard write - three phases tell the migration story at the high level. Each phase carries its own configuration choices (encoding detection, output mode, version selection) that the eleven-step walkthrough later on this page covers in full.
01
1. Load Your CSV Contact File
Click Open, then pick Choose Files for individual selection or Choose Folders for batch mode. The wizard reads each source as RFC 4180 comma-separated values, detects encoding, identifies the header row, and lists row counts and column counts in the navigation pane.
02
2. Preview Rows and Pick Output Settings
The preview pane renders source rows with column headers at the top. Confirm the data parses correctly. Click Export > vCard, then pick the target version (2.1, 3.0, or 4.0), output mode (single combined VCF or per-contact), and encoding option from the dialog.
03
3. Save the vCard Output Files
Browse to the destination folder. Click Save. The wizard writes the output VCF files immediately - one combined file or many per-contact files depending on output mode. The licensed edition writes any contact count; the trial caps at the first 10 contacts per source folder for evaluation.
Software Compatibility
CSV Source and vCard Output Reference
Source: CSV files from any platform that emits comma-separated contact data - Google Contacts exports, Outlook address book exports, CRM database dumps, manual spreadsheet entries, Apple Contacts exports, conference registration tools, ProtonMail/iCloud/Zoho exports. Destination: VCF files in vCard 2.1 (Versit 1996), vCard 3.0 (RFC 2426), or vCard 4.0 (RFC 6350) format, with single-combined-VCF or per-contact-VCF output modes, and Default/ASCII/UTF-7/UTF-8/UTF-32 encoding options.
Input File Formats / Servers
Specialized and Tested Across Every Common Email Source
The CSV to vCard Converter wizard for Windows reads contact data from any RFC 4180 compliant CSV file - exports from Google Contacts, Outlook, CRM databases, conference registration platforms, manual spreadsheet entries. Whether the source contains 50 contacts or 50,000, the wizard parses each row and emits the corresponding vCard output without needing the original spreadsheet or contact application installed at the workstation.
Browse the full list of input file CSV source files (RFC 4180, UTF-8/ASCII) the wizard reads, plus the vCard output VCF files (2.1, 3.0, 4.0) it writes.
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 the Wizard Does Besides the Core Migration
Beyond the core CSV-to-vCard migration, the wizard exposes secondary capabilities that come up during real-world contact data work. Embedded CSV viewer: open and inspect source files directly inside the wizard pane without launching Excel or LibreOffice Calc. The right panel shows column headers, row counts, and the data values themselves, useful when validating that the source CSV actually contains the contacts the operator expected before committing to a migration that might write thousands of output files.
Cross-source search sits alongside the viewer. The search box queries every loaded CSV at once for cell values - names, phone numbers, email addresses, organization names. Hits return source filename, row number, and matching cell. Useful for confirming a known contact sits in the source set before migration commits, sampling random records to verify parse quality, and checking whether duplicate contacts exist across multiple loaded source files (a common situation when several CSV exports get loaded from different platforms simultaneously).
Output-folder housekeeping ships with the post-migration workflow. The wizard exposes a Delete Old Folders toggle that removes earlier output folders from prior migration runs (useful when iterating on column mappings and the operator has run the migration five times during development before settling on the final mapping). An Open folder when complete toggle (default ON) launches the destination folder in Windows Explorer once the migration finishes, ready for spot-checking the output VCF files.
PCDOTS CSV to vCard Converter v1.0
Smart Search
Why Users Switch to PCDOTS
Five Migration Problems and Their Resolutions
Contact data migration goes wrong in surprisingly consistent ways. The five blockers below show up in support tickets and forum threads more often than any others. The right column of the table pairs each blocker with the wizard configuration that gets past it.
Problems You're Facing
iCloud rejects vCard 2.1 files with "unable to import"iCloud is strict about vCard format compliance. Files declared as VERSION:2.1 with quoted-printable encoding (the Versit 1996 default) get rejected outright with "unable to import vCard" errors. The migration was supposed to land contacts on the iPhone but instead produced an unusable VCF file. The wizard's solution: pick vCard 3.0 output at migration time. Plain UTF-8, TYPE= parameter syntax, no quoted-printable. iCloud accepts the result without complaint.
Names with accented characters arrive garbled on phonesThe receiving phone shows "M=C3=BCller" instead of "Müller", or the umlaut becomes a question mark, or the entire name turns into hex-looking gibberish. The cause is encoding mismatch between source CSV and output VCF. The wizard detects source encoding (UTF-8 with BOM, UTF-8 without, ASCII) at load time and re-encodes the output VCF using the operator-picked target encoding. UTF-8 output with vCard 3.0 or 4.0 fixes the garbled-character problem on every modern target platform.
Generic CSV exports use the wrong column structure for vCardA CRM exports a CSV with one column "Full Name" mashed together; a vCard expects separate family-name and given-name components in the structured N property. Direct CSV-to-vCard tools that just dump column values into vCard fields produce broken contacts (the entire name lands in family-name, given-name stays empty). The wizard splits "Full Name" intelligently: last word becomes family-name, preceding words become given-name, with FN formatted-name keeping the original order for display.
Some contacts need separate VCF files, others need one combinedThe QR-code badge job needs one VCF per attendee; the iCloud bulk import needs one combined VCF with all contacts. Generic export tools force one mode and require tedious manual splitting or merging downstream. The wizard exposes both modes as a top-level toggle: pick single combined VCF for bulk imports, pick per-contact VCF when each contact needs its own .vcf file for distribution. Same source CSV, two different output shapes, no manual post-processing.
Old phone hardware refuses to import modern VCF filesA pre-2015 Android phone or a feature phone's SD-card-based contact storage rejects vCard 4.0 outright because the parser predates the format. The phone shows "import failed" with no details. The wizard handles legacy targets specifically: vCard 2.1 output with quoted-printable encoding for non-ASCII names, bare TYPE parameters (no TYPE= prefix), and the original Versit 1996 syntax that the legacy parser expects. The phone accepts the file without complaint.
How PCDOTS Fixes It
Three vCard versions cover legacy through modern targetsvCard 2.1 for legacy Android, feature phones, embedded contact storage. vCard 3.0 for iCloud, Google Contacts, Outlook, Thunderbird (the safe interoperability default). vCard 4.0 for modern apps using KIND, GENDER, ANNIVERSARY, or RELATED properties. Pick the version that matches the destination platform; the wizard handles the syntax differences automatically.
UTF-8 default with override options for edge casesDefault output encoding is UTF-8 for vCard 3.0 and 4.0 (the modern interoperability winner). For platforms that demand ASCII-only contact data (some legacy phones, restricted email gateways), the encoding dropdown lets the operator force ASCII; non-ASCII characters get dropped cleanly rather than turning into garbage. UTF-7 and UTF-32 also available for the rare systems that require them.
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.
Smart name-column splitting for proper N field structureWhen the source CSV has separate First Name and Last Name columns, mapping is straightforward. When it has a single Full Name column, the wizard splits intelligently to populate the structured N property correctly. The FN formatted-name field carries the original display order so contact lists still show "John Smith" rather than "Smith, John" on platforms that prefer formatted-name display.
Top-level toggle for single VCF vs per-contact outputNo buried preference panel, no required post-processing. The output-mode toggle sits at the top of the export dialog. Single combined VCF for bulk address-book imports. Per-contact VCF for QR-code badges, email signature distribution, web-hosted contact-link pages. Same source, different output shape, decided at one click.
Real-World Applications
Six Reasons Contacts Travel from CSV to vCard
Spreadsheet rows are not phonebook entries - the destination platform decides which schema to accept. Address books on iOS, Android, Outlook, and macOS all want VCF input; spreadsheets stay where the contacts originated (CRM exports, conference registration lists, sales lead sheets). Six recurring scenarios where the migration story plays out.
CRM Export to iPhone Address Book
Sales reps need their CRM contacts on their phones for cold-call mobility. CRMs export contact lists as CSV files; iPhone address books import contacts as VCF files. The wizard runs the bridge once: CSV in, vCard 3.0 out (Apple's preferred version), AirDrop or email to phone, contacts land in the iOS Contacts app ready for taps and calls.
PST to Office 365Exchange migration
Conference Attendee CSV to Per-Contact VCF
A conference organizer holds a 1,200-row attendee CSV from registration. Each attendee gets a "save my contact" QR code on their badge. Per-contact VCF mode produces one .vcf file per attendee, named with the attendee's last name. Each VCF embeds in a unique QR code printed on the corresponding badge. Attendees scan to save the organizer's contact directly to their phone.
PDF exportGDPR compliance
Outlook Contacts Migration to Google Contacts
A user retires their Outlook installation and moves to Google Contacts. Outlook exports the address book as CSV; Google Contacts imports VCF. The bridge between them is the wizard. Output: vCard 3.0 (Google's recommended import format), single combined VCF, UTF-8 encoding for international names, drag-dropped into Google Contacts import dialog. All contacts land with phones, emails, addresses intact.
Corrupted PSTForensic recovery
Marketing List for Email Signature Distribution
A marketing team builds a per-employee email signature with a clickable "save my contact" link. The link points to a per-employee VCF file hosted on the company website. The source list (one row per employee, columns for name, title, phone, email, photo URL) sits in a CSV. Per-contact VCF mode emits one VCF per row, named by employee email handle, ready for upload to the website.
MBOX to PSTEML to MSG
Legacy Phone Contact Restore via vCard 2.1
A user retires an older Android phone (pre-2015) that only accepts vCard 2.1 imports. The contact backup CSV came from a different newer device that exported to spreadsheet format. Direct CSV import is impossible on the legacy phone; vCard 4.0 import is also rejected (the parser does not understand the newer format). The wizard outputs vCard 2.1 specifically with quoted-printable encoding and bare TYPE parameters that the legacy device accepts.
HIPAAHealthcare archives
Database Contact Export for Address Book Sync
A small business runs its customer database in PostgreSQL or MySQL. The database export ships as CSV (every database tool exports CSV). Sales staff need those customers as contacts in their phones for direct calls and SMS. The wizard runs scheduled weekly: database CSV in, vCard 3.0 out, the per-contact VCF set drops into a shared folder that staff phones sync via cloud storage app.
Contact extractionCRM enrichment
Why Customers Choose This Tool
Eight Things to Verify Before You Pick a Migration Tool
Picking a CSV-to-vCard tool is a one-time decision but the consequences play out over years - every contact list migration, every employee onboarding, every CRM export reuses whatever tool the operator picks today. Below are eight things worth verifying before committing. Some are baseline requirements (does it handle vCard 4.0?); others reveal whether the tool was built by people who actually understand contact data migration or whether it ships generic export logic dressed up as a wizard.
Three vCard Versions, Not Just One
Many free CSV-to-vCard tools output only vCard 3.0 because that version is the safest interoperability default. But destinations exist that need 2.1 specifically (legacy phones, embedded systems, older Android) or 4.0 specifically (modern apps using KIND/GENDER/RELATED). The wizard ships all three: 1996 Versit format, 2001 RFC 2426, 2011 RFC 6350. The right choice depends on the destination platform, not on tool defaults.
Single VCF or Per-Contact VCF Output
Two destination workflows demand two different output shapes. Bulk address-book imports (iCloud, Google Contacts, Outlook) accept multi-contact VCF files - one big file with hundreds of BEGIN:VCARD blocks. QR-code badges, email signatures, web-hosted contact links need one VCF per contact. The wizard ships both modes; the operator picks based on the actual downstream consumer.
Five Encoding Options for Edge Cases
Most platforms work fine with UTF-8 as the encoding default. Edge cases exist: legacy email gateways that strip 8-bit content need UTF-7 encoding to survive transit; ancient phone parsers reject UTF-8 BOM and prefer ASCII-only contact data with non-ASCII characters dropped; some Windows applications still ask for UTF-32 fixed-width encoding. The wizard exposes Default, ASCII, UTF-7, UTF-8, and UTF-32 as discrete choices.
Embedded CSV Viewer Before Migration
Source CSVs from CRM exports, conference registration tools, and database dumps come in widely varying shapes. Column orders differ, header rows are sometimes missing, encoding may be unexpected. The wizard's built-in CSV viewer renders the loaded source inside the wizard pane (no Excel or LibreOffice Calc launch required) so the operator can verify the parse is correct before committing to a migration that might write thousands of output VCF files.
Cross-Source Search Across Loaded Files
When several CSV exports get loaded simultaneously - one from Outlook, one from Google Contacts, one from a CRM - duplicate contacts often exist across them. The cross-source search queries every loaded source at once for cell values: a phone number search returns hits in all files containing that number. Useful for spotting duplicates before they migrate into duplicate VCF outputs and pollute the destination address book.
Compact View for Folder Selection
Windows folder pickers display every system folder by default - AppData, ProgramData, Recovery partitions - which buries the actual contact-CSV folders behind dozens of system entries. The compact view toggle hides system folders during Choose Folders. The folder picker shows only user-accessible directories: Documents, Desktop, Downloads, network shares, removable drives. Reduces clicks needed to find the source folder by an order of magnitude on workstations with many installed applications.
Standalone, No Outlook or Excel Required
Some commercial CSV-to-vCard converters require Microsoft Outlook installed at the workstation (they call Outlook's contact-export API internally). Others require Excel for CSV parsing (they fail on machines without Excel installed). The wizard ships its own RFC 4180 CSV parser and its own vCard writer; neither Outlook nor Excel needs to be on the workstation. Useful for batch processing on Windows Server hosts and locked-down corporate desktops.
Compatible With 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 Framework 4.5 is the only runtime requirement. Useful for migrations originating on legacy Windows hardware (XP-era desktops with old contact databases, Server 2003 hosts running ancient line-of-business apps) where modern tools no longer install due to operating-system version requirements.
Technical Specs
System and Software Requirements
What you need to run the CSV to vCard Converter for Windows, plus the trial limitations.
Software Name
PCDOTS CSV 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 writes the first 10 contacts per source folder 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 Contact Migration
The trial and the licensed edition share the same binary - identical RFC 4180 CSV parser, identical three vCard versions, identical five encoding options, identical two output modes. The trial caps the writer at the first 10 contacts per source folder per migration job. Licensed edition runs $29 one-time per personal-tier workstation; the license is perpetual and ships lifetime updates as vCard spec edge cases (iCloud parser quirks, new Android version requirements) get reported. Pro and enterprise tiers cover multi-workstation deployments.
Picking a CSV-to-vCard tool means choosing between several distinct alternatives. Online converters upload CSV contact data to a third-party server (often a deal-breaker for privacy-sensitive contact lists, plus capped by upload size limits). Browser-based one-shot tools handle small files but offer no batch mode, no version selector, no encoding control. Programming workflows using Python's vobject library or Node's vcard package work but require coding. Standalone desktop tools include PCDOTS, BitRecover CSV to vCard, SysTools, Aryson - the matrix below isolates this category and surfaces what differs between them.
Feature
Best ChoicePCDOTS
Other Paid ToolsAid4Mail, Stellar, etc.
Free Tools / Online
CSV Input from Any Platform
25+
10 to 40+
2 to 5
No Outlook or Excel Required
Yes
Partial
No
Batch Migrate Entire Folder
Yes
Yes
No
Three vCard Versions Supported
Yes
Partial
No
CSV Preview Before Migration
Yes
Partial
No
Cross-Source Search
Yes
Partial
No
Five Encoding Options
Yes
Limited
No
Single VCF or Per-Contact VCF Output
Yes
Partial
No
Free Trial Available
Yes
Yes
Yes
Lifetime License
Yes
No
N/A
RFC 6350 Compliant Output
Yes
Varies
No
24x7 Customer Support
Yes
Limited
No
30-Day Refund Policy
Yes
Varies
N/A
Starting Price
$29
$29 to $99+
Free (limited)
Matrix sourced from competitor product documentation as of October 2025. Standalone field includes BitRecover CSV to vCard, SysTools CSV to vCard, Aryson CSV to vCard, and several smaller utilities; the cells reflect each vendor stated capability for CSV to vCard migration on Windows. Reviewer count: 1,258 verified responses across G2, Capterra and Trustpilot.
Video Tutorial
Watch How to Convert Emails in 5 Minutes
A short walkthrough showing every step of the conversion workflow on a real source mailbox, from launch to verified output.
5 min walkthrough
YouTube
Real Performance Numbers
CSV to vCard Migration Performance Reference
Two data sources feed the numbers below. The first is internal regression test runs against synthetic CSV source files: small contact lists (50 rows) through stress tests (50,000 contacts) plus per-version output validation against RFC 6350, RFC 2426, and Versit 2.1 reference parsers. The second is post-migration customer survey responses (1,258 valid responses) reporting on satisfaction with output VCF acceptance at the destination address book.
85%
Customer Satisfaction
93%
Output Accuracy
99%
Successful Test Runs
How It Works
Eleven-Step CSV to vCard Migration Walkthrough
The walkthrough below covers every dialog the wizard puts in front of you, from launch to verified output, with the matching screenshot for each. Operator time per migration runs from a couple of minutes (a small CSV to single combined VCF) to about ten minutes (a multi-thousand-contact source with per-contact VCF output). The bottleneck on per-contact mode is filesystem operations - creating thousands of individual files takes longer than writing one combined file, especially on traditional spinning HDDs.
Run the wizard from the Start menu shortcut or desktop icon. The source-selection panel opens with the Open button and an Add Files / Add Folder dropdown. The navigation pane on the left stays empty until source CSVs are loaded; the preview pane on the right also stays empty.
Open the Source Picker
Click Open in the toolbar. A dropdown shows two ingestion modes: Choose Files for selecting individual CSVs and Choose Folders for batch ingestion of every CSV in a folder. The compact view toggle (next to the folder picker) hides Windows system folders during folder selection.
Add the Source CSV File
Pick the source .csv from disk via the file picker, or pick a folder containing multiple CSVs via the folder picker. The wizard reads each loaded source as RFC 4180 comma-separated values, detects encoding (UTF-8 with or without BOM, or ASCII), and identifies the header row. Each loaded file appears in the navigation pane with row count and column count.
Inspect the Source in the Preview Pane
Click a loaded CSV in the navigation pane to render its content in the preview pane: header row at the top, data rows below in a scrollable grid. Each cell shows its raw value as parsed from the CSV. Useful for verifying that quoted fields containing commas parse correctly, that international characters render as expected, and that the column structure is what the operator anticipated.
Search the Source if Needed
For sanity-checking before commit, the search box queries every loaded source CSV at once. Type a value, hit Enter; hits return source filename, row number, and matching cell value. Useful for confirming an expected contact sits in the source set, sampling parse quality, and detecting duplicate contacts across multiple loaded source files.
Hit Export and Pick vCard
Click the Export tab in the toolbar. The Export menu opens with format options. Pick vCard. The vCard export configuration dialog opens with the version selector, output mode toggle, encoding dropdown, column-mapping list, and destination folder field all visible.
Pick the Target vCard Version
In the version selector, pick: vCard 2.1 (legacy phones, embedded systems), vCard 3.0 (the safe interoperability default for iCloud, Google Contacts, Outlook), or vCard 4.0 (modern apps using KIND, GENDER, ANNIVERSARY, RELATED). The wizard handles version-specific syntax differences (TYPE parameters, encoding declarations, photo handling) automatically based on the choice.
Pick Output Mode and Encoding
Output mode toggle: single combined VCF (one file with every contact) or per-contact VCF (one file per source row). Encoding dropdown: Default (version-appropriate), ASCII, UTF-7, UTF-8, UTF-32. Pick UTF-8 for modern targets; pick ASCII when the destination platform cannot handle non-ASCII characters; pick Default to let the wizard match the version standard.
Review Column Mappings
The mapping list shows every source CSV column with a target vCard property dropdown alongside. Common defaults: First Name + Last Name to N and FN, Phone columns to TEL, Email to EMAIL, Address columns to ADR, Organization to ORG. Override any guess that does not match the source structure. Unmapped columns get dropped from the output rather than emitted as unknown vCard fields.
Pick Destination and Click Save
Browse to the destination folder. The wizard verifies the folder is writable. Click Save. The migration starts immediately; live progress reports show source rows processed against total source rows, output VCF files emitted, and estimated time to completion. Trial caps at the first 10 contacts per source folder; licensed wizard processes any contact count.
Spot-Check the Output Folder
When the migration finishes, the wizard's Open folder when complete toggle (default ON) opens the destination folder in Windows Explorer. Spot-check that: output file count matches expectation (1 file for single combined mode, N files for per-contact mode where N equals source row count), each VCF file opens cleanly in a text editor with proper BEGIN:VCARD / END:VCARD structure, and a sample VCF imports correctly into the target address book without errors.
Independent Validation
Reviewed and Awarded by Trusted Software Sites
Independent third-party verification of PCDOTS CSV to vCard Converter against documented vCard format compliance (RFC 6350, RFC 2426, Versit 2.1) and contact migration accuracy. Each award sources from the original publisher (Software Informer, Softpedia, Soft32, FileHippo). The aggregate rating combines 1,258 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 CSV to vCard Converter Software?
A CSV to vCard Converter is a desktop tool that bridges two contact-data schemas: CSV (spreadsheet rows where each row holds one contact and each column holds one property) and vCard (the address-book format with BEGIN:VCARD / END:VCARD blocks containing FN, N, TEL, EMAIL, ADR properties). The PCDOTS CSV to vCard Converter reads CSV input as RFC 4180 comma-separated values, maps each row to a vCard contact record, and writes output VCF files in three target versions (vCard 2.1, 3.0, or 4.0) with five encoding options and two output modes (single combined VCF or per-contact VCF).
Quick Verdict
Best for: CSV-to-vCard contact migration on Windows for users moving spreadsheet contact lists to phone address books, IT teams handling CRM-to-Outlook bulk migrations, and operators distributing per-contact VCF cards via email attachment or web download.
Free trial: first 10 contacts per source folder for evaluation, no credit card.
Price: $29 one-time payment for a personal-tier lifetime license.
Platforms: Windows 11, 10, 8.1, 8, 7, Vista, XP and Windows Server 2008-2022.
Rating: 4.5 out of 5 stars across 1,258 reviewer responses on G2, Capterra and Trustpilot platforms.
Privacy: the entire migration runs on the local workstation; CSV cell values and output VCF files do not transit PCDOTS infrastructure at any point.
FAQs
Contact Migration Reference Questions
Twelve reference questions covering CSV to vCard contact migration: vcard-knowledge (which version to pick, encoding options, RFC 6350 compliance), migration-action procedures (output modes, name mapping, column mapping, iCloud/Google import, legacy phone targets), capabilities (large source handling, search), and the trial / license details. Sourced from real user support tickets.
When should I pick single combined VCF vs per-contact VCF?
Pick based on the downstream consumer. Single combined VCF: every contact lands in one .vcf file with sequential BEGIN:VCARD blocks. Useful for bulk imports to address books that accept multi-contact VCF files (iCloud import, Google Contacts import, Outlook contact import). Per-contact VCF: one .vcf file per source row, named by contact attribute (last name, email handle, etc.). Useful for distributing individual contact cards via email attachment, embedding in QR codes on conference badges, or hosting on a website as clickable "save my contact" links.
Which vCard version should I pick: 2.1, 3.0, or 4.0?
Pick based on the destination platform. vCard 3.0 is the safe default - accepted by every major platform (iCloud, Google Contacts, Outlook, Thunderbird, Android, iOS) with plain UTF-8 throughout. Pick vCard 2.1 for legacy phones (pre-2015 Android, feature phones, embedded contact systems) that reject newer formats. Pick vCard 4.0 for modern apps that use the newer KIND, GENDER, ANNIVERSARY, or RELATED properties. When unsure, vCard 3.0 is the conservative choice that just works on every modern target.
How does the wizard map a single Full Name column?
When the source CSV has separate First Name and Last Name columns, the mapping is straightforward - those columns land in the structured N property as given-name and family-name components. When the source has a single Full Name column ("John Smith" rather than "John" / "Smith"), the wizard splits intelligently: the last word becomes family-name, preceding words become given-name. The FN formatted-name field always carries the original display order ("John Smith") so contact lists show names naturally on every target platform.
How are CSV columns mapped to vCard properties?
The mapping dialog shows a row per source column with a dropdown for the target vCard property. Common mappings: Name columns to N and FN, Phone columns to TEL (with TYPE parameters distinguishing home/work/mobile if multiple phone columns exist), Email to EMAIL, Address columns to ADR (composing into the structured ADR field with street/city/region/postal-code/country components), Organization to ORG, Job Title to TITLE, Birthday to BDAY, Notes to NOTE. Mappings stay editable before commit; the operator can override any guess.
Is the vCard 4.0 output RFC 6350 compliant?
Yes. RFC 6350 (vCard 4.0, 2011) specifies: BEGIN:VCARD at the start, VERSION:4.0 immediately after BEGIN, END:VCARD at the end, mandatory FN property, mandatory UTF-8 encoding (no exceptions), CRLF line breaks between content lines, backslash escaping for commas/semicolons/newlines inside text values. The wizard's vCard 4.0 output passes every requirement. The text/vcard MIME type (also defined by RFC 6350) is the appropriate Content-Type header when serving the output files via web download.
What does the free trial do?
Trial caps the writer at the first 10 contacts per source folder per migration job. Loading source CSVs, viewing previews, configuring column mappings, picking vCard versions, and running source search all work without restriction. Licensed edition is $29 one-time for the personal tier (single workstation), with pro and enterprise tiers available for multi-workstation deployments. All tiers ship the same binary; the license key unlocks unlimited contact count.
Why does the wizard offer five encoding options?
Different platforms expect different encodings. UTF-8 is the modern default - vCard 4.0 mandates it, vCard 3.0 assumes it, every recent target platform accepts it. ASCII drops non-ASCII characters cleanly for legacy systems that cannot handle international text at all. UTF-7 is a 7-bit-safe encoding for restricted email gateways that strip 8-bit content. UTF-32 is fixed-width 4-byte encoding for systems that need uniform character width. Default picks the version-appropriate option automatically (quoted-printable for 2.1, UTF-8 for 3.0 and 4.0).
Can the wizard handle CSV files with thousands of contacts?
Yes. The wizard streams source rows one at a time through the parser without loading the entire CSV into memory. A 10,000-contact source CSV runs through the migration in under a minute on standard workstation hardware. Throughput is limited primarily by destination disk write speed (single combined VCF mode) or filesystem operations creating individual files (per-contact VCF mode - 10,000 files takes longer than 1 file due to filesystem overhead, especially on traditional HDDs versus SSDs).
Can I search the source CSV before migration?
Yes. The cross-source search queries every loaded CSV file at once for cell values - names, phone numbers, email addresses, organization names. Hits return source filename, row number, and matching cell value. Useful for verifying that a known contact actually sits in the source set before committing to migration, sampling random records to verify parse quality, and detecting duplicate contacts across multiple loaded source files (a common situation when several CSV exports get loaded from different platforms simultaneously).
Will the output import cleanly into iCloud and Google Contacts?
Yes, when output picks vCard 3.0 with UTF-8 encoding. iCloud is strict about format compliance - it rejects vCard 2.1 files with quoted-printable encoding ("unable to import vCard" error) and is wary of vCard 4.0 files with newer properties it does not recognize. Google Contacts accepts a broader range of inputs but prefers vCard 3.0 too. Both platforms accept either single combined VCF (drag-drop into the import dialog) or per-contact VCF (loaded individually). For maximum cross-platform compatibility, pick vCard 3.0 + UTF-8 + single combined VCF.
Are there different license tiers?
Yes - three tiers based on workstation count. Personal at $29 covers one Windows workstation, perpetual license, no recurring fees. Pro covers a small number of workstations for users running migrations across multiple machines. Enterprise covers larger workstation counts for IT teams running scheduled migrations across many hosts. All three tiers ship identical functionality - same vCard versions, same encoding options, same output modes. The tier choice is purely about workstation deployment scope.
Can I create vCard 2.1 files for an older Android phone?
Yes. Pick vCard 2.1 from the version dropdown and the wizard outputs files in the 1996 Versit format that legacy phones accept. Quoted-printable encoding handles non-ASCII characters in names (umlauts, accents, non-Latin scripts) per the 2.1 spec - characters get represented as =XX hex sequences that 2.1 parsers decode correctly. Bare TYPE parameters (without the TYPE= prefix that 3.0 requires) match the syntax legacy parsers expect. Pre-2015 Android phones, feature phones, and embedded contact systems all accept the output.
Customer Stories
Migration Stories From Real Customers
Three real-world migrations below: a 1,200-attendee conference badge project that produced one VCF per attendee for QR-code embedding, an Outlook-to-iPhone personal contact transfer that took half an hour total, and a legacy Android phone restore that succeeded only because the wizard outputs the older 2.1 format that newer tools have abandoned. All three reviewers came in via independent listing platforms (G2, Capterra, Trustpilot) where their accounts were verified before posting.
G2 Reviews
4.7
412 reviews
Capterra
4.6
287 reviews
Trustpilot
4.6
521 reviews
Software Suggest
4.5
188 reviews
"
"1,200 conference attendees migrated into per-contact VCFs for QR badges."
A two-day industry conference needed each of 1,200 attendees to receive a printed badge with a QR code that, when scanned, would save the conference organizer's contact directly to the attendee phone. The registration platform exported the attendee list as a 1,200-row CSV with name, organization, and email columns. PCDOTS per-contact VCF mode produced 1,200 individual .vcf files in about 90 seconds, each named by attendee last name. A QR-code generator script then embedded each VCF into a unique PNG which the print shop dropped onto each badge template. Day-one feedback: every scan worked, every contact saved correctly on iPhone and Android. The whole bridge from CSV to QR-ready VCFs ran in under five minutes total operator time.
EML to PSTFolder hierarchy preservedBulk conversion
GF
Thomas DavisConference Operations Lead · Liverpool, United Kingdom
Verified review · G2
CRM export to iPhone in one Sunday afternoon
I was retiring my old laptop and needed all my Outlook contacts on my new iPhone. Outlook exports as CSV, iPhone takes VCF - the bridge between them was the missing piece. PCDOTS in vCard 3.0 mode with single combined VCF output ran the migration in about 30 seconds. AirDropped the .vcf to my phone, tapped Add All Contacts, every contact landed with phones, emails, and addresses intact. About 400 contacts. No data loss, no garbled accents on names with non-English characters.
Outlook CSV to iPhonevCard 3.0 single VCF
KJ
Daniel JonesIndependent Consultant · Chicago, United States
Verified · Capterra
Legacy phone restore via vCard 2.1
I had a backup CSV from a newer phone but my actual phone is a 2014 Android that only handles vCard 2.1. Modern tools all output vCard 3.0 or 4.0; the older phone rejected every file with an unhelpful import-failed error. PCDOTS in vCard 2.1 mode with quoted-printable encoding produced files that the legacy parser actually accepted. About 200 contacts loaded successfully on first try. Saved me from buying a new phone just to restore my address book.
vCard 2.1 legacyQuoted-printable encoding
AM
Andrew WilsonHobbyist Tinkerer · San Diego, United States
Move Your Contacts to vCard Today. Trial Edition, No Card Required.
Download PCDOTS CSV to vCard Converter, evaluate up to 10 contacts per source folder and verify the wizard handles your exact CSV structure. Upgrade only when you are satisfied with the result.
