Publisher to PDF: single files and batch conversion checks

Export one file when Publisher still runs

In a working Publisher installation, Microsoft documents File, Export, Create PDF/XPS Document, and Create PDF/XPS. Select PDF and an output filename, then inspect the exported pages. Availability depends on the installation and license after retirement; do not assume every Microsoft 365 user can still launch Publisher. For an inaccessible original, use the linked compatible-import guide or request a PDF from someone who can open it.

1. Open a copy of the publication.
2. Export to a new PDF file using the documented export command.
3. Check page count, page size, images, and the final lines of each text box.

Inventory before conversion

Work from a copy of the archive. Record relative path, filename, size, and modification date, and keep the originals unchanged. Group files by business purpose: newsletters, labels, brochures, mailings, and templates. A folder containing many generations of the same template can hide repeated compatibility problems.

Decide which files require editable output and which only need a readable record. Use separate status fields for these outcomes. A PDF can be approved as an archive copy even when an editable conversion needs further work. This prevents one requirement from obscuring the other.

Create a pilot with difficult files

Include long documents, linked text boxes, missing fonts, embedded images, tables, and unusual page sizes. Add a few ordinary files so the pilot reflects everyday work as well as edge cases. Where available, gather PDFs exported from the original application as comparison references.

Evaluate candidate tools on the same files. Printicorn and Pub Rescue describe batch conversion workflows; their current documentation and trials are the right place to check supported inputs and output limits. Do not compare only the easiest file from one tool with the hardest file from another.

Use an explicit approval checklist

Check page count, dimensions, orientation, text clipping, paragraph reflow, image resolution, missing objects, and font substitution. Review page edges and the last paragraph in every linked text flow. If a newsletter contains an address or date, verify the actual text rather than judging the page from a thumbnail.

A visual comparison utility can help find differences between two PDFs, but a large number of harmless rendering differences can obscure important changes. Human review is still necessary for representative pages and every flagged exception. Record what was checked and what remains uncertain.

Create a manifest, not just an output folder

For each input, record output paths, conversion tool and version, conversion time, status, warnings, and reviewer decision. Suggested statuses are pending, converted-unreviewed, approved, and manual-rebuild. Keep errors separate from warnings so a missing output cannot be mistaken for an accepted conversion.

Preserve the original folder structure where practical. Avoid silently overwriting outputs with the same name from different folders. If a file must be reprocessed, keep enough history to know which approved output is current. A simple CSV manifest is often sufficient for a small archive.

Make handover part of the project

Open a sample on another machine. Confirm that the archive can be navigated without the conversion tool and that someone else understands the manifest. Back up originals, accepted exports, and instructions together. Test restoring a small folder rather than assuming that a backup job proves recoverability.

For editable files, ask the future editor to update one issue without help. If the result requires extensive manual repair, document that cost before converting the rest. A smaller approved archive is more useful than a large collection whose reliability no one can explain.