Mail Merge Templates
A Mail Merge Template is a Microsoft Word document stored in Salesforce that drives the platform's native Mail Merge feature.
Definition
A Mail Merge Template is a Microsoft Word document stored in Salesforce that drives the platform's native Mail Merge feature. The document holds Salesforce merge fields, written with syntax like {!Account.Name} or {!Contact.FirstName}, that Salesforce swaps for live record data when a user generates a document. Templates live as records on the Mail Merge Template object, reached through Setup under Communication Templates, Mail Merge Templates.
Mail Merge Templates are a legacy feature. They power two older generation paths: Standard Mail Merge, which ran in the browser through the Connect for Office Word add-in, and Extended Mail Merge, which renders server-side. Standard Mail Merge and Connect for Office were retired on February 1, 2019. Most current orgs use Lightning Email Templates for email-style merge content and an AppExchange document generation app for richer letters, contracts, and PDFs.
How Mail Merge Templates fit the legacy Mail Merge feature
What the template actually is
A Mail Merge Template is a regular Word document (.doc) that an admin prepares with Salesforce merge fields and then uploads to the org. The merge fields are placeholders. At generation time, Salesforce reads the record the user started from, finds each placeholder, and replaces it with that record's data. A letter template with Dear {!Contact.FirstName} {!Contact.LastName} becomes Dear Maria Gomez when run from Maria's contact. The template stores the file plus a few metadata fields: a name, an optional description, and the object it targets. Salesforce treats each uploaded document as one Mail Merge Template record, so the library of templates is just a list of these records in Setup. Because the body is plain Word, the layout, fonts, headers, and footers all come from Word itself, not from Salesforce. That made the format approachable for anyone who could write a letter, which is part of why it stayed popular in Sales Cloud orgs for years before richer tools arrived.
Merge field syntax and supported data
Mail Merge Templates use the same Salesforce merge field syntax as Classic email templates: an exclamation mark, the object, a dot, and the field, all inside curly braces, such as {!Opportunity.Amount}. Each template is tied to one starting object, usually Account, Contact, Lead, or Opportunity. From that object you can reach related records through relationship names, so an Opportunity template can pull {!Opportunity.Account.Name} to print the parent account. You can also add user and organization fields, which is handy for signing a letter with the running user's name and title. The fields available depend on the starting object and the user's field-level security, so a field a user cannot see will not merge for them. One known gap is rich text: Mail Merge does not carry formatting out of rich text area fields, so those values come through as plain text. Picklist values merge as their stored label, and currency and date fields follow the org's locale settings at generation time.
Standard Mail Merge versus Extended Mail Merge
The same template could feed two different engines, and the difference matters. Standard Mail Merge processed on the client side. It needed the Connect for Office Word add-in (an ActiveX control), ran only in Internet Explorer, and was not compatible with Office 2010 or newer. It opened the finished document straight into Word on the user's machine. Extended Mail Merge processes on the server side, so it needs no ActiveX and works across all supported browsers. Salesforce generates the document and then either emails it to the user or drops it on the Documents tab, and it can also produce envelopes and labels. Extended Mail Merge writes in the Word 97 to 2003 .doc format. Neither path produces a polished PDF on its own, and neither carries rich text formatting. Standard Mail Merge and the Connect for Office add-in were retired on February 1, 2019, which is why any modern reference to native Mail Merge means the Extended version.
Why the format hit a ceiling
Mail Merge Templates carry the limits of an older design. Output is Word, so getting a clean PDF means a manual save or a separate conversion step. There is no built-in batch run across many records at once in the modern Lightning experience, so generating one document per record at scale is awkward. The template manager in Setup is a flat list with no folders or sharing model, which gets unwieldy once an org has dozens of templates. Tables that grow with child records, like printing every line item under an Opportunity, are hard to express because Word merge fields were built for one record at a time. Conditional content, such as showing a paragraph only when an amount is above a threshold, is not really supported. These gaps are exactly what document generation vendors built their products around, and they are the practical reason teams move off the native feature even though it still functions.
What teams use instead today
For email-style content with merge fields, the modern answer is Lightning Email Templates, authored in the Lightning email builder with rich text, dynamic merge fields, and reusable components. They are a different feature on a different object, so they are not Mail Merge Templates and the two should not be mixed up in a template strategy. For real document output, contracts, quotes, and formatted PDFs, teams reach for an AppExchange document generation app. These tools support PDF output, tables that repeat across child records, conditional sections, and bulk generation. Salesforce also ships its own quote and document features in some clouds. The migration is mostly a one-time rebuild: take what each Word template produced, recreate it in the new tool, and retire the old Mail Merge Template. The payback is easier maintenance and formats that match what customers expect, which is why the rebuild is usually worth the effort.
Inheriting an org full of Mail Merge Templates
If you take over an org that still leans on Mail Merge Templates, treat them as documentation of a business need rather than something to keep forever. Each template tells you what document a team prints, which fields they care about, and how they word it. Catalog them first: list every template in Setup, note its starting object, and find out who actually uses it. Many lists include stale templates no one runs anymore, which you can simply archive. For the live ones, decide whether email or a formatted document is the real requirement, then map each to Lightning Email Templates or a document generation tool. Watch for templates that depend on the retired Standard Mail Merge path, because those have not generated correctly since the 2019 retirement and any users still trying to run them will be stuck. A short audit usually shrinks a scary-looking template library down to a handful that genuinely need to move.
Where this sits in certification study
Mail Merge Templates show up mostly as historical vocabulary now. Older Sales Cloud Consultant and Administrator material referenced native Mail Merge as the way to generate documents from records. Current exam guides lean on Lightning Email Templates for merge content and describe document generation in general terms, so the legacy feature appears only as background. For study, it is enough to know that Mail Merge Templates are Word documents with Salesforce merge fields, that Standard Mail Merge and Connect for Office were retired in 2019, that Extended Mail Merge runs server-side and outputs .doc, and that modern orgs use Lightning Email Templates plus an AppExchange tool. If a practice question presents Mail Merge as the recommended approach for new work, treat that as a sign the question is dated rather than a reflection of current best practice.
Creating a Mail Merge Template
Mail Merge Templates are created by preparing a Word document with Salesforce merge fields and uploading it to the org. This describes the modern, supported path that feeds Extended Mail Merge. The older Standard Mail Merge add-in is retired, so do not plan new templates around it.
- Draft the document in Word
Open Microsoft Word and write the letter, fax, or label exactly as you want it to print. Set the fonts, spacing, headers, and footers here, because Salesforce keeps the Word layout as-is and only swaps in record data.
- Insert Salesforce merge fields
Where personalized data should appear, type the merge field using Salesforce syntax, for example {!Contact.FirstName} or {!Account.BillingCity}. Confirm each field belongs to the object the template will target, and use relationship names like {!Opportunity.Account.Name} for parent records.
- Save in the supported Word format
Save the file as a Word 97 to 2003 document (.doc), since Extended Mail Merge generates in that format. Keep the file somewhere easy to find for the upload step.
- Upload it in Setup
Go to Setup, Communication Templates, Mail Merge Templates, and choose New Template. Enter a name and an optional description, attach the .doc file, and save. The template is now a record other users can pick when they run Mail Merge from a record.
A clear label users will see when choosing a template, such as Renewal Reminder Letter.
The .doc Word file that holds the body text and the Salesforce merge fields.
Optional note explaining the template's purpose and which object it runs from, which helps when the list grows.
- Do not build on Standard Mail Merge or the Connect for Office add-in. Both were retired on February 1, 2019, and will not generate documents.
- Merge fields a user cannot see under field-level security will come through blank, so test the template as a typical end user, not only as an admin.
- Rich text area fields lose their formatting in Mail Merge and merge as plain text, so avoid relying on them for styled content.
- Output is .doc, not PDF. If you need a polished PDF or tables that repeat across child records, an AppExchange document generation tool is the better fit.
Prefer this walkthrough as its own page? How to Mail Merge Templates in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Mail Merge Templates.
- Connect for Office and Standard Mail Merge Have Been RetiredSalesforce
- Extended Mail MergeSalesforce
Hands-on resources to go deeper on Mail Merge Templates.
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 are Mail Merge Templates in Salesforce?
Q2. Where in Setup do admins manage Mail Merge Templates?
Q3. How do Mail Merge Templates relate to Lightning Email Templates?
Discussion
Loading discussion…