Mail Merge in Writer

LibreOffice

Chapter 4 · Mail Merge in Writer

Word & PowerPoint Chapter 7 established the underlying job: one template, one data source, many personalized documents. That job hasn't changed. What's genuinely different here is the flow — Writer walks you through it with a guided, step-by-step Mail Merge Wizard, rather than the more free-form, Ribbon-driven process Word uses.

The Same Job, a Different Flow: The Mail Merge Wizard

Tools → Mail Merge Wizard opens an 8-step guided sequence: select a starting document, choose the document type (letter or email), insert an address block, create a salutation, adjust the layout, edit merge fields directly if needed, personalize and preview the documents, then complete the merge. Word offers the same overall set of decisions, just made in whichever order you choose from its Mailings tab rather than a fixed guided sequence.

Choosing the Data Source

Within the wizard, Select Address List connects to your data — a Calc spreadsheet (.ods or .xlsx), or an external database registered with LibreOffice. This is genuinely broader than Word's own merge, which is built primarily around file-based sources; Writer's merge is designed from the ground up to work against real database connections too, not just spreadsheet files.

The Registered Data Sources Concept

Writer's merge mechanism is built around registering a data source with LibreOffice first — giving it a name LibreOffice remembers (via Tools → Options → LibreOffice Base → Databases, or File → New → Database) — rather than browsing fresh to a file every single time, the way Word's Select Recipients → Use an Existing List does. Once registered, that same named data source can be reused across multiple merge documents without ever re-browsing to the underlying file again.

Address Block and Salutation: Built-In Smart Matching

Steps 3 and 4 of the wizard attempt to automatically match your data source's own column names to the fields an address block or salutation expects — a "Match Fields"-style step conceptually identical to Word & PowerPoint Chapter 7's own Match Fields dialog, and driven by the exact same underlying concern: column names that don't match exactly need to be explicitly mapped, or the merge silently produces blank or mismatched results.

Inserting Additional Merge Fields Manually

Insert → Field → More Fields → Database tab (also reachable directly from within the wizard) lets you place any specific column's value anywhere in the document — the same underlying action as Word's Insert Merge Field, just reached through a general-purpose Field dialog rather than one dedicated Ribbon button.

Personalizing and Completing the Merge

The wizard's later steps preview each record's actual data filled into the document — the same purpose as Word's own Preview Results — before finishing by printing directly, saving the merge as one combined document, or emailing each personalized copy: the same three completion options Word & PowerPoint Chapter 7's Finish & Merge offers.

AspectWordWriter
Starting flowFree-form, via the Mailings tabA fixed, guided 8-step Wizard
Connecting a data sourceBrowse to a file fresh each timeRegister the source once by name, reuse it across merges
Field name matchingMatch Fields dialogBuilt into the wizard's address block/salutation steps
Data source types supportedMostly file-based (Excel, etc.)Spreadsheets and real registered database connections
The same clean-spreadsheet lesson from Excel Fundamentals still applies
The exact Excel Table used for Word & PowerPoint's own capstone Mail Merge — clear column headers, one record per row, no blank rows scattered through it — could, in principle, serve as this Writer merge's own data source too, since Calc opens .xlsx files directly. Excel Fundamentals Chapter 7's "a well-structured data source matters" lesson travels across both apps and both suites unchanged; only the mechanism connecting to it looks different.
A registered data source is tied to a file path, and that path can go stale
Registering a data source links it to the exact file location it pointed at when registered. If that file is later moved, renamed, or deleted, the registration doesn't update itself — the next merge attempt using that registered name simply fails to resolve it, requiring the source to be re-registered against its new location. This is a genuinely different failure mode from Word's simpler "browse to the file fresh each time" approach, which has no equivalent stale-registration problem, precisely because it never remembers a file's location between merges in the first place.

Hands-On Exercises

Exercise 1

Create a small Calc spreadsheet with columns Name and Amount, 3 rows of sample data. Register it as a data source with LibreOffice, then run through the Mail Merge Wizard in Writer to produce a personalized letter per row. Describe which wizard step connects to your registered source, and which step lets you preview one row's actual data before finishing.

📄 View solution
Exercise 2

Six months after Exercise 1, the original spreadsheet file is moved to a different folder and renamed. You open the same Writer template and try to run the merge again using the same registered data source name. Describe what happens and what step is needed to fix it.

📄 View solution
Exercise 3

Your spreadsheet's columns are named CustName and AmtDue, but the wizard's address block step expects fields named Name and Amount. Explain what would happen if you proceeded without addressing this, and identify the exact Word & PowerPoint Chapter 7 concept this situation directly mirrors.

📄 View solution

Chapter 4 Quick Reference

  • Tools → Mail Merge Wizard — an 8-step guided flow, same underlying job as Word's Mailings tab
  • Data sources are registered by name with LibreOffice, then reused across merges without re-browsing
  • Writer's merge supports both spreadsheets and real database connections, more broadly than Word's mostly file-based sources
  • Field-name matching in the wizard is the same exact-match concern as Word & PowerPoint Chapter 7's own Match Fields
  • A registered data source's file path can go stale if the file is moved or renamed, requiring re-registration