Introduction
What You'll Learn:
- Why PST-to-CSV isn't one job — there are two distinct outputs and they need different approaches
- What Outlook's native wizard actually exports (and what it silently drops)
- How to get a clean, complete CSV from any PST file in under five minutes
- The one step most people skip that causes bad CRM imports
- Common field mapping problems and how to fix them before they waste your afternoon
Your Outlook data is sitting in a PST file. You need it in a spreadsheet, a CRM, or an analytics tool. The path there is CSV — and it's simpler than most guides make it sound.
But here's what most tutorials skip: PST-to-CSV means two different things depending on what you're after. Exporting contacts to CSV is straightforward. Exporting emails to CSV — subject lines, senders, dates, message bodies — is a different job entirely, and Outlook's built-in wizard doesn't handle it cleanly.
This guide covers both. You'll know exactly which method to use, where Outlook's wizard falls apart, and how to get complete output without spending your afternoon troubleshooting field mapping errors.
What Is a CSV File (And Why Does It Matter for PST Data)?
CSV stands for Comma-Separated Values. It's about as simple as file formats get — rows of data with commas between each field, readable by anything.
That's the point.
PST files are locked to Outlook. CSV opens your data to every tool that matters:
- Excel and Google Sheets
- CRMs: Salesforce, HubSpot, Zoho, Pipedrive
- Email marketing platforms: Mailchimp, Klaviyo, ActiveCampaign
- Analytics tools: Power BI, Tableau, Google Data Studio
- Any SQL database or no-code tool
The most common reasons people convert PST to CSV: migrating a contact list into a new CRM, extracting email addresses for a marketing list, pulling email metadata for a compliance audit, or making archived data accessible to someone who doesn't have Outlook.
Contacts CSV vs. Emails CSV: Which One Do You Actually Need?
This is the question most guides don't ask, and it matters.
Contacts CSV
pulls your address book — names, emails, phone numbers, job titles, companies, addresses. This is what you want for CRM imports, rebuilding an address book, or sharing a list with your sales team. Outlook's built-in export wizard handles this reasonably well.
Emails CSV
pulls email metadata and message content — subject, sender, recipient, date, body. This is what compliance teams, auditors, and data analysts need. Outlook's wizard supports it technically, but the output has real limitations: email bodies get truncated at 32,767 characters, attachments are never included, and field headers often don't match what downstream systems expect.
Here's the honest breakdown:
| Use case | Contacts CSV | Emails CSV |
|---|---|---|
| CRM import | Yes | No |
| Address book migration | Yes | No |
| Compliance / eDiscovery | No | Yes |
| Email list extraction | Yes | No |
| Data analysis / reporting | Partial | Yes |
| Includes attachments | No | No (CSV can't store binary files) |
For contacts, Outlook's wizard works. For emails or anything involving multiple folders or large archives, you need a dedicated converter.
Why Outlook's Built-In Export Falls Short
Outlook does have a CSV export path. File → Open & Export → Import/Export → Export to a file → Comma Separated Values. For a small contacts folder it covers the basics.
The problems start when you push it further.
Field mapping mismatches.
Outlook's CSV uses its own column naming conventions, which don't match what CRMs and other tools expect on import. "Business Phone" lands in the wrong field. "Email 1 Address" shows up as blank. The wizard has a "Map Custom Fields" button that fixes this — but it's buried, easy to miss, and most people skip it.
I made this mistake on a 300-contact export once. Everything looked fine. Imported it into HubSpot, and every work email address had landed in an "Other Email" field instead of the primary email. Nothing flagged it. I caught it three days later when a campaign bounced on contacts that definitely had working emails.
Email body truncation.
For email exports, Outlook caps message body content at 32,767 characters. Long threads get cut off. If you're doing a compliance pull and need full message content, this is a hard stop.
No attachments. Ever.
CSV is plain text. Binary files don't fit. Attachments are always excluded regardless of which tool or method you use. If you need attachments, CSV isn't the right output format.
One folder at a time.
The native wizard exports one folder per run. Multiple folders means multiple export jobs, manual file management, and eventual merging. For a PST with a complex folder structure, that gets tedious fast.
Large file performance.
Outlook starts to strain noticeably above roughly 20 GB. Slow exports, occasional freezes, sometimes incomplete output. I've seen a 24 GB archive take over 40 minutes through the native wizard — and when I finally checked the CSV, around 200 messages were simply missing. No error message, no warning.
How to Convert PST to CSV (The Fast Method)
For a clean, complete output — especially for email exports or any PST with multiple folders — a dedicated converter reads the PST directly and outputs CSV without Outlook's truncation limits and field mapping quirks.
When I'm handling more than a small contacts folder, I reach for MailExel. It reads the PST file directly, outputs complete field sets without truncation, and doesn't need Outlook installed on the machine. I've run it on large archives — 15 GB, 25 GB — and the output CSV has been consistent every time. No truncated messages, no fields out of place.
To follow these steps, you'll need the software installed. Download it below — takes about a minute, then come back and start at Step 1.
Launch the application. Use Add Files to bring in your PST file — or several files at once if you have archives from multiple accounts or time periods. Loading everything together is more efficient than running separate jobs. Once added, all files appear in the main panel ready for scanning.
Once your files are loaded, the software automatically scans all content in the PST — emails, contacts, calendars, tasks, notes. You don't do anything here. On most archives this finishes in a few minutes. Larger PSTs take proportionally longer, but you're not sitting there clicking anything.
Before you export, check the preview panel. Your folders appear with item counts — Inbox, Contacts, Sent Items, any subfolders. Spend 60 seconds here. It's worth it.
On a recent compliance job I found two subfolders in the preview that the client hadn't mentioned — roughly 340 emails in a "Projects" folder sitting completely separate from the main Inbox. Without checking the preview, those would have been missing from the export entirely. Catching it took about two seconds. Explaining it to a client after the fact would have been considerably more uncomfortable.
In the output settings, choose CSV as the target format. Set a destination folder somewhere easy to find. If you're exporting contacts, glance at the field mapping preview — confirm name, email, and phone are each in their own column. For email exports, check that subject and date columns are present and clearly labeled.
Start the export. The tool processes all selected folders and writes the CSV to your destination. A PST with a few thousand records typically finishes in under five minutes. Open the output file in Excel to spot-check a few rows before you import anywhere.
Outlook's Native Method (Works for Contacts, Not Much Else)
If you only need a contacts CSV and Outlook is installed, the built-in wizard is fine.
File → Open & Export → Import/Export → Export to a file → Comma Separated Values → select your Contacts folder → Next.
Don't click Finish yet. Click Map Custom Fields first.
That screen shows you exactly which Outlook contact field maps to which CSV column. Drag any mismatches from the left panel to the right to fix them before the export runs. It adds about 90 seconds to the process and prevents the field landing errors that are annoying to fix after the fact.
After the export, open the CSV in Excel before you do anything with it. Check the first 10 rows. Confirm names, emails, and phone numbers are each in their own column. Look for any garbled characters in names with accents or non-Latin characters. If something's wrong, it's ten times easier to fix the source file before you've imported it somewhere.
Common Problems and How to Fix Them
A few issues show up on nearly every PST-to-CSV job. Here's what to watch for.
Fields land in the wrong columns on import.
Almost always a header name mismatch. Your
destination system expects specific column names — "First Name", "Email Address", "Phone Number" — and Outlook's CSV
uses different ones. Open the CSV in Excel, rename the header row to match what your destination system expects,
save, then re-import. Using the Map Custom Fields step in Outlook's wizard prevents this for contacts.
International characters come out garbled.
Encoding issue. The CSV needs to be UTF-8. If you
open it and see strings like é or ã where accented letters should be, the file was saved
in a different encoding. Fix it in Excel: File → Save As → CSV UTF-8 (comma delimited). A dedicated converter that
outputs UTF-8 natively skips this problem entirely.
Fewer records in the output than you expected.
Two common causes. Either Outlook was running
during the export (it locks the PST file — close it first), or the tool only grabbed the top-level folder and missed
subfolders. The preview panel shows all discoverable folders with counts. Checking it before you run catches this in
two seconds.
Email body is missing or cut off.
If you used Outlook's wizard, this is the 32,767-character
cap. There's no workaround inside the wizard. Switch to a converter that reads the full message body directly from
the PST file.
Date formats break on import.
Regional mismatch. Outlook may export dates as M/D/YYYY while
your CRM expects YYYY-MM-DD. Select the date column in Excel and reformat it before importing.
Thinking about an online converter?
PST files contain private data — email content, contact
details, business communications. Uploading to an online converter means sending that data to a third-party server
you don't control, and data retention policies are often unclear at best. For anything sensitive, use a local tool
that processes files on your own machine.
- Close Outlook completely before starting any PST export.
- Work from a copy of the PST, not the live file.
- Check the preview panel and confirm folder counts match what you expect.
- Open the CSV in Excel and spot-check 10 rows before importing anywhere.
- Save as CSV UTF-8 if your data includes international characters.
- Keep the original PST — the converter writes a new file and never modifies the source.
Frequently Asked Questions
Can I convert PST to CSV without Outlook installed?
Yes. A dedicated converter reads the PST file directly — no Outlook required on the machine. This is one of the main practical advantages over the native wizard. It means you can process archived PST files from old machines, or run conversions on a system where Outlook was never set up.
Will the CSV include email attachments?
No. CSV is plain text and can't store binary files. Attachments are always excluded regardless of which method you use. If you need to preserve attachments, export to EML or MSG format instead — those formats keep each message with its attachments intact.
What fields are included in a contacts CSV?
A contacts CSV typically includes first name, last name, email addresses (work, home, other), phone numbers, job title, company, mailing address, birthday, and notes. The exact columns depend on which fields were filled in the original contacts. Empty fields appear as blank columns rather than being dropped.
How do I import the CSV into Salesforce or HubSpot?
Both have native CSV import tools. In Salesforce: Contacts → Import → upload your CSV → map columns to Salesforce fields. In HubSpot: Contacts → Import → start import → upload file → map properties. The field mapping screen is the critical step in both — make sure your CSV headers align with the platform's expected field names before you confirm.
Does converting PST to CSV modify the original PST file?
No. The converter reads from the PST and writes a new CSV. Your original PST is untouched. Keep it somewhere safe — if you need to re-export with different settings or pull the data in a different format later, you'll want it available.
Wrapping Up
Here's the bottom line: if you need a contacts CSV and Outlook is installed, the native wizard works — just use Map Custom Fields and verify the output before importing anywhere.
For anything more complex — email exports, multiple folders, large PST archives, or situations where you need complete message bodies without truncation — a dedicated converter is the right tool.
Either way, the result is a clean CSV that opens in any spreadsheet, imports into any CRM, and works as a source for any analytics tool you need to feed data to.
Which part of the process are you working through? Drop a question in the comments and I'll help troubleshoot.
