Mail Merge: Multiple Pages per Record to Separate PDFs
For a mail merge with multiple pages per record, each separate PDF must contain all the pages belonging to that record. Splitting every two pages works only when every record actually occupies two pages. A long address, paragraph or table can change where the next record begins.
Start with a few test records and write down their actual page ranges. This guide covers the boundary checks that a multi-page batch needs. For the broader choice of manual export, macros and add-ins, see saving mail merge as individual PDF files.
Use record identity rather than an assumed page count
A record is the source item that should produce one document. It might be a customer letter, an invoice or one attendee's certificate package. A page is only part of that document's layout. Keep those two counts separate when planning the split.
Consider an invented batch with three records: A occupies two pages, B occupies three, and C occupies two. The correct ranges are 1–2, 3–5 and 6–7. A fixed two-page split would separate part of B and combine pages from different records. The following table is a worked example, not a measured output from your file.
| Document ID | First page | Last page | Expected filename |
|---|---|---|---|
| A | 1 | 2 | batch-A.pdf |
| B | 3 | 5 | batch-B.pdf |
| C | 6 | 7 | batch-C.pdf |
A free manual route for a small batch
Finish a test merge into an editable document. Find the start and end of each record and note its identifier. When your PDF export or print-to-PDF dialog supports selecting pages, export the verified range for one record to its own file. Open that file and confirm that its first and last pages belong to the same record.
Repeat with the next verified range. Keep a written expected-file list so that you can account for every selected record. Menu names and page-selection options vary by application and platform; check the actual export dialogue rather than assuming a screenshot from another setup matches yours.
This route needs no splitting macro, but the range mapping is manual. Use it for a manageable batch where you can inspect every boundary. For a large batch or frequently changing layout, use an export method that processes one source record at a time.
Preview difficult records before the full merge
Select a short record, a long record, and one containing optional content. Include cases where a table or paragraph approaches the bottom of a page. Check each identifier and the beginning of the following record.
Microsoft's Excel mail merge instructions describe editing the recipient list and stepping through Preview Results. Verify the selected source records before examining their page boundaries. A record excluded from the merge cannot appear in the resulting PDF batch.
Use the mail merge test checklist to record the source export and template version. Save the source used for this run; changing it later can make a missing-file investigation refer to different input.
Check how a macro or add-in defines one output
Before applying an existing macro, read how it locates the next record. Code that exports a fixed number of pages has different assumptions from code that merges one source record at a time. A section-based splitter also needs a test: a template can contain section breaks inside one recipient's document.
Do not assume every section is a separate recipient. Ask what happens when one record has more than one section, and check the first, middle and final output. Use an approved macro or add-in in accordance with your organisation's policies; a successful run message does not establish that the boundaries are correct.
Microsoft's mail merge rules documentation explains record-advancing rules. Check any such rules in the template when records seem to repeat or skip. Preserve a working copy before adjusting the template.
Give each PDF a stable, unique filename
Use a document ID or a combination that uniquely identifies one expected output. A recipient's name may repeat legitimately across several documents. Add a batch reference when you need to distinguish a rerun from the original outputs.
Plan the filenames before exporting. If two expected records would receive the same name, resolve the collision deliberately rather than relying on the exporter to overwrite or rename a file. See custom filenames for merged documents for the naming plan.
Reconcile the outputs before distribution
For each expected document, verify the filename, recipient identifier, first page, last page and relevant content. Check for unexpected files as well as missing ones. An apparently correct file count can hide one duplicate and one omission.
The free output reconciliation log records those observations. Keep corrected outputs in a clearly identified rerun folder until review is complete, then distribute the approved version only.
Generating separate documents from the start
When your task is one personalised document per spreadsheet row, open Docs from Excel with a small test set and your prepared template. Inspect the generated documents and available output options in the tool. Check the current download terms before purchasing a batch.
Whichever method you choose, test the longest record. Generating separate files avoids a later combined-file split, but each document still needs its own layout and identity check.
Can I simply split at every blank page?
Only if you have verified that the blank page consistently marks a record boundary in this particular output. Blank pages can also be part of the layout. Never use their presence alone to identify the recipient.