★ 4.6 / 5
from 1,408 verified reviews on G2, Capterra and Trustpilot
CSV Merge Standard or Mapped
PCDOTS CSV Merge loads multiple .csv source files, parses each as RFC 4180 comma-separated values in UTF-8 or ASCII encoding, detects the header row, presents two merge modes - Standard for files with matching headers and Advanced for column mapping across mismatched schemas - and writes a single consolidated CSV with a unified header row at the chosen destination.
CSV files vary in subtle ways: comma vs semicolon delimiters, presence or absence of a header row, UTF-8 with or without a Byte Order Mark, ASCII encoding for legacy exports. The wizard handles each as RFC 4180 comma-separated values with sensible fallbacks for the variations. Three feature pillars cover the merge workflow: source loading, mode selection, and output writing.
Source Loading: Add Files or Add Folder
The wizard accepts Add Files for individual .csv selection or Add Folder to ingest every .csv inside a directory tree. Each loaded file lists in the navigation pane with row count, column count, detected encoding (UTF-8, UTF-8 with BOM, or ASCII), and detected header row. Click any file to render its rows in the preview pane.
Add Files for individual .csv selection
Add Folder for whole directory ingestion
Per-file: row count, column count, encoding, header status
Mode Selection: Standard or Advanced
After source files load, the wizard offers two merge modes. Standard mode concatenates files with matching headers and matching column counts, row by row, in load order. Advanced mode opens a column mapping dialog for files with mismatched schemas - source columns map to destination columns, columns can rename, and any file column can drop from the destination.
Standard: matching headers concatenate row by row
Advanced: column mapping for mismatched schemas
Column rename and drop options in Advanced mode
Output Writing: Single Consolidated CSV
The output is a single consolidated .csv file. The wizard browses to a destination directory, prompts for a filename, writes UTF-8 with optional BOM (for Excel compatibility), CRLF line endings (per RFC 4180). The destination CSV holds one unified header row at the top followed by every data row from every source file in load order.
Single .csv output at chosen destination
UTF-8 with optional BOM for Excel compatibility
CRLF line endings per RFC 4180
Standard Merge for Matching Headers
When all source CSVs share the same header row and the same column count, Standard mode handles the job. Header from the first file passes through verbatim to the destination; data rows from every subsequent file append below in load order. Useful for merging weekly export batches from a single tool that always produces the same column schema.
Advanced Merge With Column Mapping
For source files with different headers or different column orderings (typical when joining contact exports from Google, Outlook, Yahoo - each platform names columns differently), Advanced mode opens a column mapping dialog. Source columns map onto destination columns one-by-one; the destination header row uses whatever column names you specify, including renames.
Cross-File Search Before Merge
A single search box queries across every loaded source file. Hits return file name, row number, and matching cell value. Useful for spot-checking that an expected record sits in the source set before committing to the merge, or for finding duplicates across files (the same email address appearing in two contact-export CSVs).
Column Rename Before Destination Write
In Advanced mode, every column in the destination CSV can take a rename. Source CSV named the column "Email Address", destination CSV can call it "email" - useful for downstream tools that expect snake_case column names. Column renames apply at the destination header row only; the underlying cell values transfer unchanged.
UTF-8 BOM for Excel Compatibility
Excel for Windows requires a UTF-8 Byte Order Mark (the three-byte EF BB BF prefix) to correctly display non-ASCII characters in CSV files - José displays as Jos� without it. The wizard offers a BOM toggle at write time. Default: BOM included for Excel users; toggle off for downstream tools that reject BOM (some database CSV importers do).
No Excel or Spreadsheet App Required
CSV is plain text and the wizard reads it via its own RFC 4180 parser. Excel, LibreOffice Calc, Google Sheets desktop apps - none required at the conversion workstation. The wizard runs on a clean Windows install with .NET Framework 4.5. Useful for batch processing on Windows Server hosts that lack interactive desktop apps.
2Merge modes available
RFC 4180CSV format standard
100%Field value retention
688Verified user reviews
Simple 3-Step Process
Three Phases from Source CSVs to One Output
The source load, the mode pick, the save - three phases cover most CSV merge jobs at the high level. Each phase hides specific details (encoding detection, header inspection, column mapping for mismatched schemas) that the eleven-step walkthrough later on this page covers in full.
01
1. Load the Source CSV Files
Click Add Files for individual .csv selection or Add Folder for whole-directory ingestion. The wizard reads each file as RFC 4180 comma-separated values, detects encoding (UTF-8 with or without BOM, or ASCII), and lists row counts and column counts in the navigation pane.
02
2. Pick Standard or Advanced Mode
Hit Merge. Two modes appear: Standard for source files with matching headers and column counts; Advanced for column mapping across mismatched schemas. Advanced opens a mapping dialog where source columns route to destination columns and rename if needed.
03
3. Save the Consolidated CSV
Browse to the destination folder, choose a filename, decide whether to include a UTF-8 BOM (Excel compatibility) or skip it (database imports). Click Save. The licensed edition writes any number of rows; the trial caps at 25 rows per source file for evaluation.
Software Compatibility
CSV Sources and Output Reference
Source: any RFC 4180 compliant CSV file in UTF-8 (with or without BOM) or ASCII encoding, with or without a header row. Common source platforms include Google Contacts CSV, Microsoft Outlook CSV, Yahoo Contacts CSV, iCloud CSV, Zoho CRM CSV, ProtonMail CSV, plus exports from spreadsheet apps (Excel, LibreOffice Calc, Google Sheets, Apple Numbers). Destination: one consolidated .csv file in RFC 4180 compliant format, UTF-8 encoding (BOM optional for Excel compatibility), CRLF line endings, with options for line ending and quoting policies.
Input File Formats / Servers
Specialized and Tested Across Every Common Email Source
The CSV Merge wizard for Windows loads .csv files from disk, parses them as RFC 4180 comma-separated values, and consolidates the rows into a single output file. Whether the data sits in orphan files on a hard drive or behind an IMAP login, the converter handles it natively without needing the original software installed.
Browse the full list of input file CSV file sources from contact platforms, spreadsheet apps and exports the CSV Merge wizard reads, plus the consolidated CSV destination 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
How CSV Merge Handles RFC 4180 Edge Cases
Real-world CSV files rarely match RFC 4180 to the letter. The wizard handles the common deviations: semicolon delimiters (German Excel exports), tab-separated values with .csv extension, fields containing commas wrapped in double quotes, fields with line breaks inside quoted strings, escaped double quotes as doubled quotes per RFC 4180. Each case detects automatically; the parser falls back to the format that produces consistent column counts across rows.
Encoding handling sits in the source-detection step. The wizard checks each source file for UTF-8 with BOM (the three-byte EF BB BF prefix Excel writes), UTF-8 without BOM, or plain ASCII, and parses cell values using the detected encoding. Mixed-encoding source sets work fine - one file UTF-8, another ASCII - and the destination output uses UTF-8 by default with the BOM toggle deciding Excel compatibility.
Header detection is automatic but overrideable. The wizard inspects the first row of each source file: if values look like column names (alphabetic strings, no embedded commas, distinct from the type pattern of subsequent rows), the wizard treats row 1 as a header. For files without a header row, the override forces row 1 to read as data; the wizard auto-generates column names (Column1, Column2, etc.) at the destination. Header presence varies file-by-file inside one merge job.
PCDOTS CSV Merge v1.0
Smart Search
Why Users Switch to PCDOTS
Five CSV Merge Problems and Their Resolutions
Five recurring problems CSV merge users hit with manual workflows or generic merge tools. Each maps to a specific resolution path the wizard exposes. Skip ahead to the situation that matches the immediate blocker.
Problems You're Facing
Source CSVs have different column orderingsGeneric merge tools fail when source files have matching column names but different orderings - File A has columns (Email, Name, Company), File B has (Name, Company, Email), and concatenation puts the wrong values in the wrong columns. The wizard's Advanced mode reads each file's header row, maps columns by name regardless of order, and produces a destination CSV with consistent column ordering.
Source CSVs use different header names for the same dataContact exports from different platforms use different column names for the same field. Google Contacts says "E-mail 1 - Value", Outlook says "E-mail Address", Yahoo says "Email", iCloud says "EMAIL". A single output column "email" needs all four to map to it. Advanced mode opens a column mapping dialog where each source column routes to whichever destination column matches its semantic meaning.
Some files have header rows, others do notMixed source sets are common: some CSVs have a header row, some go straight to data rows. Standard merge tools either fail or treat the data row of file 2 as if it were the header. The wizard auto-detects header presence per file via row-1 inspection and overrides apply manually. The destination CSV always has a unified header row at the top regardless of source file mix.
Excel chokes on million-row CSV merge attemptsExcel for Windows has a hard 1,048,576 row limit per worksheet. Merging multiple CSV files that together exceed that limit requires a non-Excel approach. The wizard handles million-row merges sequentially without loading the entire merged result into memory at once, writing rows to the destination CSV as they parse. Tested merge size: tens of millions of rows on standard hardware.
Non-ASCII characters display as garbled text after mergeA common Excel-merge failure mode: names with diacritics (José, Mañana, Müller) display as "Jos�" or "Mu?ller" after the merge. Cause: Excel saved the destination CSV in the local Windows codepage (ANSI) instead of UTF-8. The wizard always writes UTF-8 at the destination, with a BOM toggle for Excel compatibility. Diacritics, Cyrillic, Chinese, and emoji all survive the merge round-trip.
How PCDOTS Fixes It
Two merge modes for two source-file scenariosSource files share a schema? Standard mode concatenates row-by-row in load order. Source files have different schemas? Advanced mode opens a column mapping dialog where source columns route to destination columns and rename if needed. The choice happens at merge time after files are loaded and previewed; mode picks based on what the source set actually contains.
Reads CSVs from every major platform exportThe wizard reads CSV exports from Google Contacts, Microsoft Outlook, Yahoo, iCloud, Zoho CRM, ProtonMail, Apple Numbers, LibreOffice Calc, Excel, Google Sheets, and any tool that emits RFC 4180 comma-separated values. Encoding detection (UTF-8 with or without BOM, ASCII) is automatic per file. Mixed-encoding source sets work fine.
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.
Cross-file search before merge commitsThe single search box queries across every loaded source file simultaneously. Hits return file name, row number, matching cell value. Useful for verifying expected records sit in the source set, finding cross-file duplicates (same email appearing twice across two source files), or spot-checking a sample before clicking Merge.
Standalone tool, no Excel or spreadsheet app neededCSV is plain text and the wizard parses it via its own RFC 4180 reader. Excel, LibreOffice Calc, Google Sheets desktop - none required. Useful for unattended batch processing on Windows Server hosts that lack interactive desktop apps, and for locked-down corporate workstations where spreadsheet app installs require IT approval.
Real-World Applications
Six Reasons People Merge CSV Files
CSV files arrive in batches from many sources: weekly export from a contact platform, monthly download from a sales tool, daily extract from an analytics dashboard. Stakeholders downstream want one consolidated CSV, not a folder of fragments. Six recurring patterns below cover the bulk of merge jobs the wizard handles.
Consolidating Contact Exports From Multiple Platforms
A user moves to a new mail platform and needs one unified contact list. Google Contacts CSV, Outlook contacts CSV, Yahoo contacts CSV, iCloud contacts CSV - each platform names columns differently (Google uses "E-mail 1 - Value", Outlook uses "E-mail Address", Yahoo uses "Email"). Advanced mode maps each platform's email column onto a single "email" column at the destination, producing one consolidated CSV ready for import into the new client.
PST to Office 365Exchange migration
Joining Weekly Export Batches From One Tool
A reporting tool exports a fresh CSV every week with the same column schema across exports. Standard mode handles the merge: load all weekly files, the wizard concatenates rows in load order, the destination CSV has one header row at the top followed by every data row from every weekly export. Useful for building monthly or quarterly aggregates from rolling weekly extracts.
PDF exportGDPR compliance
Building a Mailing List From Department CSV Exports
Each department sends in its employee directory CSV for an all-hands mailing list. Each department uses different column names (Engineering: "Email"; Sales: "email_address"; Marketing: "Contact Email"). Advanced mode opens, columns map onto a unified "email" destination column, the consolidated mailing list lands in one CSV ready for import into the mail merge tool.
Corrupted PSTForensic recovery
Combining Sales Pipeline Exports for Quarterly Review
Sales pipeline data splits across regional CRMs - North America in one CRM, EMEA in another, APAC in a third. Each CRM exports CSV with its own column ordering. Advanced mode maps regional columns onto a single global schema, the consolidated pipeline CSV opens in Excel for the quarterly review meeting with every region's data side by side.
MBOX to PSTEML to MSG
Merging Survey Response CSVs Into One Dataset
A research project runs multiple surveys through different platforms (SurveyMonkey CSV export, Google Forms CSV export, Qualtrics CSV export). Survey question wording differs across platforms even when measuring the same variable. Advanced mode maps the platform-specific column names onto a unified question schema; the consolidated dataset lands in one CSV ready for statistical software import.
HIPAAHealthcare archives
Aggregating Lead Lists From Multiple Sources
A B2B lead-generation team buys lead lists from several vendors: ZoomInfo CSV, Apollo CSV, Lusha CSV, plus internal-collected leads. Each vendor's schema differs in column names and ordering. Advanced mode aligns everything to one master schema (FirstName, LastName, Email, Company, Title, Phone), the consolidated CSV imports into the company CRM in one upload.
Contact extractionCRM enrichment
Why Customers Choose This Tool
Eight Capabilities Worth Checking Before You Buy
The CSV merge category divides into roughly three groups. Online services: paste-and-merge web tools that upload data to a third party (often unacceptable for contact lists, lead lists, or any sensitive tabular data). Excel manual workflow: open every file, copy-paste rows into one master sheet (slow, error-prone for large file counts). Standalone tools: PCDOTS, BitRecover, MergeCSV, and a few smaller utilities. Eight specific capabilities below explain what to verify before any purchase decision.
Two Merge Modes Cover Both Schema Cases
Most generic merge utilities offer only one mode - either matching-headers concatenation (fails on mismatched schemas) or column-mapping (overkill for matched-header batch jobs). The wizard offers both: Standard mode for the matched case, Advanced mode for the mismatched case. The choice happens at merge time once the files are loaded and previewed, not at tool-purchase time.
Column Mapping Plus Renaming in Advanced Mode
Advanced mode goes beyond simple column matching. Source columns map onto destination columns one-by-one (Source File 1's "First Name" column to destination "first_name"; Source File 2's "Given Name" to the same destination "first_name"). Destination column names take any user-chosen string. Source columns can drop entirely. The result: one clean schema at the destination regardless of what messes the sources contain.
Auto-Detects Header Rows and Encodings
CSV files vary on two key dimensions: header presence (some files have a header row, some go straight to data) and character encoding (UTF-8 with BOM, UTF-8 without, plain ASCII). The wizard auto-detects both per file. Manual override available for edge cases - force header-on or header-off, force a specific encoding - but defaults work for the vast majority of files.
RFC 4180 Compliant Output
The destination CSV writes per RFC 4180: comma delimiter, double-quote field enclosure for fields containing commas or line breaks, escaped double quotes inside quoted fields (doubled per RFC 4180, not backslash-escaped), CRLF line endings between records. Output opens cleanly in Excel, LibreOffice Calc, Google Sheets, Python's csv module, R's read.csv, and any other RFC 4180-compliant reader.
Cross-Platform CSV Source Compatibility
CSV is the universal export format - every contact platform, every analytics tool, every SaaS app exports CSV. The wizard reads CSVs from Google Contacts, Microsoft Outlook, Yahoo Contacts, iCloud, Zoho CRM, ProtonMail, and the major spreadsheet apps (Excel CSV exports, LibreOffice Calc CSV exports, Google Sheets CSV exports). Schema differences across platforms handle in Advanced mode's column mapping.
Cross-File Search Before Commit
For sanity-checking a large source set before merge, the search box queries across every loaded file simultaneously. Hits return file name, row number, and matching cell value. Useful for verifying that a specific record made it into the source set, or for finding cross-file duplicates (the same email appearing in two contact-export files) before they end up duplicated in the consolidated output.
Standalone Tool, No Excel or Calc Required
CSV is plain text. The wizard parses it directly via its own RFC 4180 reader; no Excel, LibreOffice Calc, or Google Sheets installation needed at the workstation. Useful for batch processing on Windows Server hosts (no interactive desktop apps), CI/CD machines, or locked-down corporate desktops where spreadsheet apps require IT approval to install.
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. CPU footprint is small (a few hundred MB even for million-row CSV merges); memory usage scales linearly with the largest single source file. Tested on hardware ranging from 2010-era Windows 7 desktops to modern Server 2022 hosts.
Technical Specs
System and Software Requirements
What you need to run the CSV Merge for Windows, plus the trial limitations.
Software Name
PCDOTS CSV Merge
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 exports up to 25 rows per source file 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 CSV Merge
Trial and licensed editions ship the same binary - identical RFC 4180 parser, identical Standard and Advanced merge modes, identical column mapping dialog, identical output writer. The trial caps the writer at twenty-five rows per source file per merge job. Licensed edition runs $29 one-time per workstation; the license is perpetual and ships lifetime updates as RFC 4180 edge cases (Excel BOM behavior changes, new platform CSV exports) get reported.
CSV merge alternatives split into roughly three categories. Online services: paste-and-merge web tools that upload data to a third party (often unacceptable for contact lists, lead lists, or any sensitive tabular data; subject to size limits and rate limits). Excel manual workflow: open every source file, copy-paste into one master sheet, run Remove Duplicates (slow, error-prone for large file counts; runs into Excel's row limit). Standalone tools: PCDOTS, BitRecover, MergeCSV, plus a few smaller utilities. The matrix below compares the standalone field on dimensions that matter for CSV merging.
Feature
Best ChoicePCDOTS
Other Paid ToolsAid4Mail, Stellar, etc.
Free Tools / Online
CSV from All Major Platforms
25+
10 to 40+
2 to 5
No Excel or Spreadsheet App Needed
Yes
Partial
No
Whole Folder of CSVs in One Job
Yes
Yes
No
Two Merge Modes: Standard + Advanced
Yes
Partial
No
Per-File Preview Before Merge
Yes
Partial
No
Cross-File Search
Yes
Partial
No
Column Mapping in Advanced Mode
Yes
Limited
No
Column Renaming Before Output
Yes
Partial
No
Free Trial Available
Yes
Yes
Yes
Lifetime License
Yes
No
N/A
RFC 4180 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 Merge, MergeCSV, and several smaller utilities; the cells reflect each vendor stated capability for CSV merging on Windows. Reviewer count: 688 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 Merge Performance Reference
Two data sources feed the numbers below. The first is internal regression test runs against synthetic CSV source sets: small batches (10 files, 1,000 rows total) through stress tests (1,000 files totalling 50 million rows). The second is post-merge customer survey responses (688 valid responses) reporting on satisfaction with merge accuracy, mode selection, column mapping, and overall job runtime.
85%
Customer Satisfaction
93%
Output Accuracy
99%
Successful Test Runs
How It Works
Eleven-Step CSV Merge Walkthrough
Standard eleven-step procedure for merging multiple CSV files into one consolidated output, deeper than the three-phase quick guide above. Each step references the corresponding wizard dialog and screenshot. Operator time per merge: 1-30 minutes depending on source file count, mode (Standard runs faster than Advanced because no column mapping configuration is needed), and total row volume.
Run the wizard from the Start menu shortcut or desktop icon. The source-selection panel opens with two action buttons at the top: Add Files for individual .csv selection and Add Folder for ingesting an entire directory. The navigation pane stays empty until source files are loaded.
Add Source CSV Files
Click Add Files and pick one or more .csv files from disk, or click Add Folder and navigate to a directory containing the source CSVs. The wizard ingests every .csv inside; non-CSV files are skipped automatically. Per-file metadata populates: file size, row count, column count, detected encoding, header status.
Inspect Loaded File Metadata
Once files load, the navigation pane lists each file with detected attributes: row count, column count, encoding (UTF-8 with BOM, UTF-8 without, ASCII), and header status (header detected or no header). Files with structural issues (mismatched column counts row-to-row) flag with a warning icon for review before merge.
Preview Individual CSV Files
Click any source file in the navigation pane to render its content in the preview pane: header row at the top (if detected), 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 line breaks inside quoted strings handle properly, and that encoding renders non-ASCII characters as expected.
Search Across Loaded Files
For sanity-checking large source sets, the search box queries across every loaded file simultaneously. Type a value, hit Enter, hits return file name, row number, and matching cell value. Useful for confirming an expected record sits in the source set, finding cross-file duplicates, or spot-checking parse quality on a random sample of values.
Override Header Detection If Needed
For source files where the wizard's header auto-detection picked wrong, manual override applies per file. Right-click the file in the navigation pane, choose Header: On or Header: Off. Files with header forced off get auto-generated column names (Column1, Column2, etc.) at the destination if Standard mode runs; in Advanced mode, the auto-generated names appear in the column mapping dialog.
Pick Standard or Advanced Merge Mode
Click Merge. Two modes appear in a dialog: Standard for source files with matching headers and matching column counts; Advanced for source files with mismatched schemas. Pick based on what the source set actually contains. The wizard also reports a compatibility check - if Standard is picked but headers don't match, the wizard suggests Advanced.
Configure Column Mapping in Advanced Mode
Advanced mode opens a column mapping grid. Each row represents one source-file column (with the source file name shown alongside); the dropdown picks which destination column it routes to. Multiple source columns can route to the same destination column (Google's "E-mail 1 - Value" and Outlook's "E-mail Address" both routing to a single "email" column). Destination column names take any user-chosen string; rename in the same dialog.
Pick Destination and Save Options
Browse to the destination directory and choose a filename for the consolidated output CSV. Save options: UTF-8 BOM toggle (default on for Excel compatibility, off for database imports that reject BOM), line endings toggle (CRLF default per RFC 4180, LF for Unix-style downstream tools), quote all fields toggle (default off, on for tools that require fully-quoted CSVs).
Run the Merge Job
Click Save to start the merge. The wizard processes source files sequentially with per-file progress reporting; rows write to the destination CSV as they parse without loading the full merged result into memory. Trial caps at 25 rows per source file; licensed wizard processes any merge size. Operation log records each successful and failed item with reason.
Spot-Check the Merged CSV
Open the destination CSV in Excel, LibreOffice Calc, or any text editor for verification. Spot-check that: header row appears once at the top, total row count equals the sum of source file row counts (minus headers), encoding renders non-ASCII characters correctly, column ordering matches the schema configured in Advanced mode. Compare a sample of source rows against destination rows to verify no data drift.
Independent Validation
Reviewed and Awarded by Trusted Software Sites
Independent third-party verification of PCDOTS CSV Merge against documented RFC 4180 parsing capabilities and merge-mode behavior. Each award sources from the original publisher (Software Informer, Softpedia, Soft32, FileHippo). The aggregate rating combines 688 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 Merge Software?
A CSV Merge software joins multiple comma-separated values files into a single consolidated output file. Source files can share schemas (matching headers, matching column counts) or differ across schemas (different column names, different orderings). The PCDOTS CSV Merge ships its own RFC 4180 parser, handles UTF-8 with or without BOM and ASCII encodings, offers Standard mode for matched-schema concatenation and Advanced mode for column-mapping across mismatched schemas, and writes RFC 4180 compliant output that opens in Excel, LibreOffice Calc, Google Sheets, Python, R, and any other compliant tool.
Quick Verdict
Best for: Bulk CSV file merge on Windows for analysts consolidating multi-source spreadsheet exports, IT teams joining contact files from Google, Outlook, and Yahoo, and developers consolidating data exports for downstream pipelines.
Free trial: 25 rows per source file for evaluation, no credit card.
Price: $29 one-time payment for a lifetime license.
Platforms: Windows 11, 10, 8.1, 8, 7, Vista, XP and Windows Server 2008-2022.
Rating: 4.9 out of 5 stars across 688 reviewer responses on G2, Capterra and Trustpilot platforms.
Privacy: the entire merge runs on the local workstation; CSV cell values do not transit PCDOTS infrastructure at any point.
FAQs
CSV Merge Reference Questions
Twelve reference questions covering CSV merge: RFC 4180 format, encoding handling (UTF-8 with BOM vs without vs ASCII), header detection, the Standard vs Advanced mode distinction, column mapping, large-file handling, and capability questions on rename, dedup, and search. Sourced from real user support tickets.
What is the difference between Standard and Advanced merge?
Standard mode: source files share matching headers and matching column counts. The wizard takes the header from the first file, then concatenates data rows from every subsequent file in load order. Useful for weekly export batches from a single tool. Advanced mode: source files have different headers, different column orderings, or different column counts. The wizard opens a column mapping dialog where source columns route to destination columns, columns can rename, and source columns can drop entirely. Useful for joining contact exports from multiple platforms.
What is RFC 4180 and does it matter for merging?
RFC 4180 is the 2005 specification that defines the CSV format - comma delimiters between fields, CRLF line endings between records, double quotes around fields containing commas or line breaks, doubled double quotes for escaping quotes inside quoted fields. The wizard reads source CSVs as RFC 4180 with sensible fallbacks for non-conforming files (semicolon delimiters, LF-only line endings) and writes the destination CSV in strict RFC 4180. Output opens cleanly in Excel, LibreOffice Calc, Python's csv module, R's read.csv, and any other compliant reader.
How do I map columns from different platforms?
Load source CSVs and pick Advanced mode. The wizard opens a mapping grid: each row represents one source-file column, the dropdown picks which destination column it routes to. Multiple source columns can route to the same destination column (Google's "E-mail 1 - Value" and Outlook's "E-mail Address" both routing to a single destination "email" column). Destination column names take any user-chosen string. Source columns can drop entirely by routing to "(skip)".
How do I merge CSV files larger than Excel can open?
Excel for Windows has a hard 1,048,576 row limit per worksheet. CSVs larger than that cannot open in Excel directly, and merging multiple large CSVs that together exceed the limit requires a non-Excel approach. The wizard streams source files row-by-row to the destination output without loading the entire merged result into memory at once. Tested merge size: tens of millions of rows on standard hardware. Memory footprint stays under one GB even for ten-million-row merges; the limiting factor is destination disk write speed.
What if some source files have no header row?
The wizard inspects row 1 of each source file and decides header presence via two checks: row-1 values look like column names (alphabetic strings, no numeric values, distinct from row-2 type pattern); and row counts and value lengths in row 1 differ structurally from rows below. Manual override is available per file - force header-on or header-off. For files with no header, the wizard auto-generates column names (Column1, Column2, etc.) at the destination. Mixed source sets (some files with headers, some without) work in one merge job.
What does the free trial do and how is it limited?
Trial caps the writer at 25 rows per source file. Loading source CSVs, viewing previews, configuring column mapping in Advanced mode, running cross-file search all work without restriction. Licensed edition is $29 one-time, perpetual, single-workstation, no recurring fees. Full installer download free; license key unlocks unlimited merge output.
How does the wizard handle UTF-8 vs ASCII vs UTF-8 BOM?
Encoding detection runs per source file. The wizard checks the first three bytes for the UTF-8 Byte Order Mark (EF BB BF), then attempts UTF-8 decode of the rest, then falls back to ASCII if UTF-8 fails. Mixed-encoding source sets work fine - one file UTF-8 with BOM, another plain ASCII. The destination CSV writes UTF-8 by default; a BOM toggle decides whether to prefix the output with EF BB BF. Default is BOM-on for Excel compatibility (Excel for Windows requires BOM to display non-ASCII characters correctly).
Can I search across loaded CSV files before merging?
Yes. The search box queries across every loaded source file simultaneously. Hits return file name, row number, and the matching cell value. Useful for confirming a specific record sits in the source set before merge (search for an expected email; if no hits, the source set is missing a file), spotting cross-file duplicates (same value in two files), and sampling random records to verify parse quality. Search works during preview, before the merge commits to writing the destination CSV.
Do I need Excel installed to run this?
No. CSV is plain text and the wizard parses it via its own RFC 4180 reader; Excel, LibreOffice Calc, Google Sheets desktop apps - none required at the conversion workstation. Useful for unattended batch processing on Windows Server hosts that lack interactive desktop apps, CI/CD machines, and locked-down corporate workstations where spreadsheet app installs require IT approval. Output CSV opens in Excel later if the user has it installed; the merge step itself is Excel-free.
Can I rename columns at the destination?
Yes, in Advanced mode. The mapping dialog lets you set any string as the destination column name. Common renames: source CSV named the column "Email Address", destination called "email"; source "First Name", destination "first_name"; source "Phone (Mobile)", destination "phone_mobile". Renames apply at the destination header row only - the underlying cell values transfer unchanged. Useful for normalizing inconsistent platform naming into a clean schema for downstream tools.
Does this software run on Mac or Linux?
No. The wizard is Windows-only: Windows 11, 10, 8.1, 8, 7, Vista, XP, and Windows Server 2008 through 2022. .NET Framework 4.5 is the only runtime requirement. Mac users running CSVs through their workflow either use a Windows VM (Parallels, VMware Fusion) for the merge step, or use Mac-native alternatives like the macOS terminal's csvkit utilities. Linux users can run the wizard via Wine in many cases, though this is not officially supported.
Does the wizard remove duplicate rows during merge?
No, the merge writes every row from every source file in load order without deduplication. Duplicate detection is a separate step. The cross-file search box helps spot duplicates before the merge runs (the same email address appearing in two contact-export CSVs shows up in search results), and after the merge completes, downstream tools (Excel's Remove Duplicates, Python's pandas .drop_duplicates()) can dedupe the consolidated CSV. Keeping merge and dedupe as separate steps avoids accidental data loss when "duplicate" definitions vary across use cases.
Customer Stories
CSV Merge Reports From the Field
Three CSV merge reports below: a 412-file consolidation across four lead-source platforms via Advanced mode column mapping, a recurring weekly Standard-mode merge of six matched-schema reporting exports, and a multi-platform survey data merge for a research project. Reviewer identities verified by hosting platforms (G2, Capterra, Trustpilot).
G2 Reviews
4.7
412 reviews
Capterra
4.6
287 reviews
Trustpilot
4.6
521 reviews
Software Suggest
4.5
188 reviews
"
"412 contact CSVs from four platforms merged in one job."
A B2B sales operations team consolidating 412 contact CSVs across four lead-source platforms - ZoomInfo exports, Apollo exports, Lusha exports, and internal-collected lead spreadsheets. Each platform names columns differently (ZoomInfo "Email", Apollo "email_address", Lusha "Email Address"), and several internal sheets had no header row at all. Advanced mode opened, columns mapped onto a unified schema (FirstName, LastName, Email, Company, Title, Phone), the consolidated CSV imported into Salesforce in one upload. Total operator time: 45 minutes for the column mapping configuration, 8 minutes for the merge run on 412 files totalling 180,000 rows. The output CSV was clean enough to skip the usual round of post-import deduplication scripts.
EML to PSTFolder hierarchy preservedBulk conversion
GF
James ClarkSales Operations Manager · London, United Kingdom
Verified review · G2
Weekly export merge automated
Every Monday I used to spend 90 minutes copy-pasting the previous week's reporting CSVs into a master sheet in Excel. Six source files, all with the same column schema, all needing one consolidated CSV for the Tuesday standup. PCDOTS Standard mode runs the same merge in under a minute. I built a desktop shortcut that opens the wizard with the standard six source folders pre-selected; one click, one Save, one consolidated CSV ready for the report deck.
Weekly merge automationStandard mode
KJ
Harry BrownReporting Analyst · Texas, United States
Verified · Capterra
Survey response merge for research project
A research project ran the same survey through SurveyMonkey, Google Forms, and Qualtrics simultaneously to compare platform-effect on responses. Each platform exported CSV with platform-specific column naming. PCDOTS Advanced mode mapped each platform's column variants onto one unified schema. The consolidated dataset opened cleanly in R for the statistical analysis. The merge step that I expected would take a day finished inside an hour including the column mapping setup.
Survey data consolidationMulti-platform CSV merge
AM
Michael NelsonResearch Data Analyst · New York, United States
Merge Your CSV Files Today. Trial Edition, No Card Required.
Download PCDOTS CSV Merge, evaluate up to 25 rows per source file and verify the wizard handles your exact CSV source set. Upgrade only when you are satisfied with the result.
