How to Do a Mail Merge Using Excel as Your Data Source
Mail merge is one of those genuinely useful skills that sits at the intersection of spreadsheet data and email communication — and Excel plays a more central role in it than many people realize. Whether you're sending personalized invoices, event invitations, or bulk outreach emails, understanding how the process works from the Excel side will save you significant time and prevent frustrating errors.
What Mail Merge Actually Means (and Where Excel Fits)
Mail merge is the process of combining a template document or email with a list of recipient data to produce personalized copies — one per person. Excel's role is as the data source, not the sending tool. The merge itself typically happens in Microsoft Word (for letters or documents) or through an email client like Outlook, a Gmail-based tool, or a third-party platform.
Your Excel spreadsheet becomes what's called the recipient list or data source file. Every row represents one person. Every column represents a field — first name, last name, email address, company, custom message, order number, and so on.
How to Set Up Your Excel Spreadsheet for Mail Merge
Getting your Excel file structured correctly is the most important step. Problems here cause the majority of mail merge failures.
The rules for a merge-ready spreadsheet:
- Row 1 must be your header row. These column names become your merge field names (e.g.,
FirstName,Email,City). Use clear, single-word labels without spaces where possible. - No blank rows or columns within your data range. A blank row tells the merge tool the data has ended.
- No merged cells in the spreadsheet — they break the data structure.
- Consistent data formatting in each column. If one cell in a "ZIP Code" column is formatted as a number and drops the leading zero, every recipient with a ZIP like
08901will get8901. - Save as
.xlsxor.csv— both are widely compatible with merge tools, though.csvis the most universally accepted format across non-Microsoft platforms.
📋 A clean, flat table with no fancy formatting is always more reliable than a visually styled spreadsheet.
Doing a Mail Merge with Excel and Microsoft Word
This is the most common workflow for document-based merges — letters, labels, envelopes, or printed materials.
Step-by-step overview:
- Build and save your Excel data file.
- Open Microsoft Word and navigate to the Mailings tab.
- Click Start Mail Merge and choose your document type (letters, email messages, labels, etc.).
- Click Select Recipients → Use an Existing List and locate your Excel file.
- If prompted, select the correct sheet within the workbook and confirm the header row option.
- Insert merge fields into your document using Insert Merge Field — these appear as
«FirstName»,«City», etc. - Use Preview Results to verify data is pulling correctly before committing.
- Click Finish & Merge to generate individual documents or send emails directly via Outlook.
The connection between Word and Excel happens through a technology called DDE (Dynamic Data Exchange) or OLE DB, depending on your Office version and settings. In practice, you won't see this directly — but it explains why format issues in Excel (especially with dates and numbers) sometimes appear differently in the merged output.
Doing an Email Mail Merge Directly from Excel
Excel alone cannot send emails. However, several approaches use Excel as the data source with email automation layered on top:
| Method | Tools Required | Technical Skill Needed |
|---|---|---|
| Word + Outlook merge | Microsoft Office suite | Low |
| VBA macro in Excel | Excel with macros enabled | Medium–High |
| Google Sheets + Gmail add-on | Google Workspace | Low–Medium |
| Third-party tools (e.g., Mailchimp, Yet Another Mail Merge) | Account + Excel/CSV import | Low |
| Power Automate flow | Microsoft 365 subscription | Medium |
VBA-based merges give you the most control within the Microsoft ecosystem — you can write a script that loops through each row, constructs a personalized email body, and sends it via Outlook's COM object. This approach works well for internal business workflows but requires comfort with writing or editing code.
Third-party platforms typically accept a .csv export from Excel directly. You upload the file, map your columns to template variables, and the platform handles sending, tracking, and deliverability.
Variables That Affect How Your Merge Performs
The "right" mail merge setup looks different depending on several factors:
- Volume: Outlook-based merges are generally limited to a few hundred emails before hitting sending thresholds. High-volume sends (thousands of recipients) usually require a dedicated email platform.
- Personalization depth: Simple name insertion is straightforward. Conditional content — "if customer is in California, include this paragraph" — requires either Word's IF merge fields, VBA logic, or a platform that supports dynamic content blocks.
- Data complexity: Dates, currency, and percentages stored in Excel often need explicit formatting rules applied in the merge template, or they'll appear as raw serial numbers or unformatted decimals.
- Microsoft 365 vs. standalone Office: Some features in the Mailings tab behave differently depending on your Office version and whether your account is connected to Exchange or a local Outlook profile.
- Mac vs. Windows: Mail merge functionality in Word for Mac has historically had limitations compared to the Windows version, particularly around email sending through Outlook.
Common Issues and What Causes Them
🔍 Numbers losing formatting: ZIP codes, phone numbers, and account numbers stored as plain numbers will drop leading zeros. Format those columns as Text in Excel before building your list.
Dates appearing as numbers: Excel stores dates as serial numbers internally. If your merge output shows 45123 instead of January 5, 2024, you need to apply a date format switch in your Word merge field: @ "MMMM d, yyyy".
Only the first record merges: This usually means a blank row exists somewhere in your data range, or the worksheet wasn't selected correctly during the recipient list setup.
Email field not recognized: The column header must be clearly labeled (e.g., Email or EmailAddress) — some tools look for this specifically.
The technical mechanics of mail merge are learnable and repeatable once the data source is correctly structured. Where outcomes start to diverge is in the specific combination of tools, sending volume, degree of personalization, and the platforms involved — and that combination is different for every person doing this work.