Mail Merge
A Mail Merge in Salesforce is a feature that produces personalized Microsoft Word documents, such as letters, contracts, and proposals, by inserting record data into a prepared template.
Definition
A Mail Merge in Salesforce is a feature that produces personalized Microsoft Word documents, such as letters, contracts, and proposals, by inserting record data into a prepared template. The template holds merge fields like {!Account.Name}, and Salesforce swaps each one for the matching field value from the record you choose. The result is a finished Word document tied to that record's data.
Mail Merge is a legacy, Classic-era feature, so it carries an important split. The original Standard Mail Merge, which ran through the Connect for Office Word add-in on the user's desktop, was retired by Salesforce on March 4, 2017. Its successor, Extended Mail Merge, runs server-side and still works today. Even so, most modern orgs reach for AppExchange tools or native document generation instead, because Mail Merge lives only in Salesforce Classic and outputs Word files.
How Mail Merge actually generates a document
Standard Mail Merge and why it was retired
Standard Mail Merge was the original version, and it depended on a desktop component. Users installed the Connect for Office Word add-in, which placed an ActiveX plug-in inside Internet Explorer. The merge ran on the user's own machine, so it only worked on Windows with a supported Internet Explorer and Microsoft Office 2003 or 2007. When you generated a document, Word opened it automatically on your computer. That client-side design became a liability. Standard Mail Merge and the Word add-in were only supported on Microsoft Windows Vista, which cannot be configured for TLS 1.1 or higher. Once Salesforce disabled the older TLS 1.0 protocol for security reasons, the add-in could no longer connect. Salesforce retired both Standard Mail Merge and the Connect for Office Word add-in on March 4, 2017, with a final compatible release (Connect for Office v1.8.1.6) that customers had to install by February 24, 2017 to keep working until the cutoff. After retirement, the drag-and-drop field picker was gone, and merge fields had to be typed into templates by hand.
Extended Mail Merge, the server-side successor
Extended Mail Merge replaced the retired Standard version and moved the work to Salesforce servers. Nothing installs on the user's desktop, so it does not need ActiveX or Internet Explorer. It runs on any supported browser, on any Windows version, and on Apple Mac OS X. The template document still needs to be saved in the older Word 97-2003 DOC format, but the merge itself happens in the cloud. Delivery changed too. Because the document is produced server-side, Extended Mail Merge emails the finished Word file to the user who started the merge, and it can also copy the document into your org's Documents tab for later access. The feature carries defined limits: a single run can process up to 1,000 records, each Mail Merge template can be up to 1 MB, and a mass merge operation is capped around 50 MB in total. Extended Mail Merge has been enabled by default for most orgs since Summer '17, so the feature is usually available without a support request.
Single versus mass document generation
Mail Merge supports two patterns, and the choice depends on how many records you are working with. A single Mail Merge document is generated from one record. You open a contact, lead, or other supported record, pick a Mail Merge template, and Salesforce fills the merge fields with that record's values. This suits one-off letters or a single contract where the content is specific to one person or account. Mass Mail Merge generates documents for many records at once. From a list view of leads or contacts, you select multiple records, choose a template, and Extended Mail Merge produces a batch in one operation. This is how teams create form letters, mailing labels, and matching envelopes across a whole segment. The 1,000-record ceiling and 50 MB total size apply here, so very large mailings may need to be split into multiple runs. In both patterns the output stays in Word format, which is the main reason the feature feels dated next to PDF-capable tools.
Templates and merge fields
Every Mail Merge run starts from a Mail Merge template, which is a Word document with merge fields embedded in the body. A merge field uses the {!Object.Field} pattern, for example {!Contact.FirstName} or {!Account.BillingCity}. When the merge runs, Salesforce reads the chosen record and replaces each token with the live field value, so one template can serve thousands of personalized documents. Admins manage these templates from Setup, where they upload the prepared DOC files so users can select them during a merge. Building a good template takes care. The fields referenced in the document must exist on the object the merge runs against, and the file has to follow the Word 97-2003 DOC format that Extended Mail Merge expects. Salesforce also publishes sample templates and formatting guidelines to help admins get the layout, spacing, and field syntax right before users depend on them. A small typo in a merge field name is a common reason a generated document comes out with a blank or unreplaced token.
Classic only, and the Lightning gap
The biggest practical constraint is that Mail Merge is a Salesforce Classic feature. It does not have a native Lightning Experience interface, so users who have moved fully to Lightning cannot launch a classic Mail Merge from the modern record page in the usual way. For an org that standardized on Lightning, this alone often rules the feature out, because asking users to drop back into Classic for document generation is awkward and inconsistent. This gap is a large part of why the AppExchange document-generation market grew. Tools like Conga Composer, S-Docs, and Docusign Gen offer Lightning-native buttons, output to PDF and Excel as well as Word, support conditional content, and handle batch generation with more control than the legacy feature. Salesforce itself now offers native options, including the Document Template Designer used in several Industries clouds and OmniStudio Document Generation, which create documents from standard or custom objects with data tokens and conditional logic.
When Mail Merge still fits, and what to choose instead
Mail Merge can still earn its place in a narrow set of situations. If an org remains on Salesforce Classic, only needs simple Word letters, and has low volume, Extended Mail Merge is built in and costs nothing extra. A team sending occasional form letters to a list of contacts can get value from it without buying or installing anything. For that profile, the feature does exactly what it was designed to do. Outside that profile, the better choice is usually a modern document-generation approach. Pick an AppExchange package when you need PDF output, multiple formats, complex layouts, or e-signature routing through a tool like Docusign Gen. Reach for native Salesforce options, such as OmniStudio Document Generation or the Document Template Designer, when you want to stay inside the Salesforce trust boundary and generate from any object. The decision usually comes down to output format, volume, and whether your users live in Lightning or Classic.
How to turn on and use Extended Mail Merge
Extended Mail Merge is the supported, server-side version and is enabled by default for most orgs since Summer '17. If it is not already on, a System Administrator can activate it in Salesforce Classic Setup. These steps cover turning the feature on so users can run single and mass merges.
- Open the Extended Mail Merge setting
In Salesforce Classic, go to Setup, then User Interface. Under the Advanced area, look for the Activate Extended Mail Merge option.
- Turn the feature on
Select Activate Extended Mail Merge and save. If the option is missing and the feature is not already active, open a case with Salesforce Support from an authorized admin to have it enabled.
- Upload Mail Merge templates
Prepare Word templates in 97-2003 DOC format with merge fields, then upload them in Setup so users can pick them during a merge.
- Generate a document
From a supported record or a list view, choose a Mail Merge template and run the merge. The finished Word file is emailed to you and can be saved to the Documents tab.
The setting in Classic Setup under User Interface that switches the org from the retired Standard version to the server-side Extended Mail Merge.
Word 97-2003 DOC files uploaded in Setup that hold the merge fields; users select one of these when generating a document.
Extended Mail Merge emails the finished Word file to the user who runs the merge and can also store it on the Documents tab.
- Mail Merge has no native Lightning Experience UI; users generally run it from Salesforce Classic.
- Output is Word only. If you need PDF, you must convert manually or use an AppExchange tool or native document generation.
- A single run is limited to 1,000 records, templates to 1 MB, and a mass merge to roughly 50 MB total.
- Templates must be saved in the older Word 97-2003 DOC format, and merge field names must exactly match fields on the object.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Mail Merge.
- Managing Mail Merge TemplatesSalesforce
- Generate Mass Mail Merge DocumentsSalesforce
Hands-on resources to go deeper on Mail Merge.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Mail Merge in Salesforce?
Q2. Is Mail Merge a modern feature?
Q3. What's a modern alternative?
Discussion
Loading discussion…