Save Publisher Files Before October 1—or Microsoft 365 Cannot Open Them

Convert every Publisher file you may need by October 1, 2026, while Publisher is still available through Microsoft 365. Preserve each original .pub file, export layout-sensitive publications to PDF, and create Word copies only when future text editing justifies a less faithful result.

Microsoft’s official retirement guidance states that subscribers will lose access to Publisher after October 1 and will no longer be able to open or edit .pub files in the application. It recommends converting files beforehand and documents manual PDF conversion, a PDF-to-Word route, searches across PCs, OneDrive and SharePoint, and a sample PowerShell workflow for bulk export.

Confirm which Publisher deadline applies

The October 1 cutoff applies to Publisher supplied through a Microsoft 365 subscription. Keeping the .pub files alone will not preserve access for those subscribers because the Publisher application will no longer be available to open them.

Perpetual Publisher licenses follow a different timetable: The Register’s deadline summary places the end of Microsoft 365 access on October 1, 2026, and the end of support for perpetual versions on October 13, alongside Office LTSC 2021 and Consumer Office 2021. Perpetual-license users can continue installing and using the application after support ends, but an unsupported copy is better treated as temporary recovery capacity than as the archive’s only access method.

Find the complete .pub archive

Search for .pub files on every relevant PC, then repeat the search in OneDrive and SharePoint. Include shared folders, migrated user directories, departmental templates, communications archives, and folders exchanged with printers or outside designers.

Build an inventory containing each file’s full path, filename, modification date, owner or business area, and planned destination. Flag apparent duplicates without deleting them: similarly named files may contain different pages, languages, images, or print settings.

Create a controlled local working copy of cloud-hosted files before bulk conversion. Preserve the source folder hierarchy so identically named files do not collide, and place untouched originals in a protected archive governed by the organization’s existing access and retention rules.

Choose PDF, Word, or both

PDF is the safer preservation format when appearance matters more than continued editing. It suits completed brochures, newsletters, certificates, labels, signs, programs, and other publications that primarily need to be viewed, printed, or retained as records.

Use Word only when the content genuinely needs revision. The documented route is to export the Publisher file as PDF, open that PDF in Word, and save the converted document. Because Word optimizes the result for text editing, text boxes, columns, graphics, page breaks, and object positions may differ from the original, especially in graphic-heavy publications.

For an important reusable design, retain the original .pub file, a validated reference PDF, and a replacement template rebuilt in the application chosen for future work. The PDF preserves the approved appearance; the rebuilt file supplies a maintainable editing path.

Convert individual files manually

For a small archive, open each publication in Publisher, go to File, select Save As, choose a destination, select PDF as the file type, and save. Use a predictable output name without overwriting the .pub source.

1. Open the publication and address any missing-font, missing-image, or linked-content warnings.
2. Save a PDF in the corresponding destination folder.
3. Open the PDF independently and inspect every page.
4. If editing is required, open the PDF in Word and save a separate .docx copy.
5. Log the result as passed, accepted with a documented difference, or failed.

Pilot the process with demanding files rather than only simple ones. Include a multipage publication, a folded design, a label sheet, a file using uncommon fonts, and a document containing several positioned graphics; faults found in this batch should shape the checks applied to the remaining archive.

Bulk-export large collections

The sample Convert-PubFileToPDF.ps1 script accepts a file path or wildcard filter and supports the optional -Recurse switch for subfolders. Windows Latest’s inspection of the PowerShell workflow describes how it finds matching files with Get-ChildItem and controls the installed Publisher application through COM/Interop to export them.

Run the script first against a copied pilot folder on a Windows PC with a working, licensed Publisher installation. A recursive command can use Convert-PubFileToPDF.ps1 -Filter "*.pub" -Recurse, while a specific folder or filename filter limits the scope of the first run.

The sample continues after errors and identifies successful and failed conversions. Capture its output as a migration log. It also stops rather than overwriting an existing destination file, so investigate name collisions instead of deleting prior PDFs indiscriminately.

Process large archives in manageable batches and reconcile discovered .pub files against successful exports. Retry only recorded failures after correcting their cause; files that will not open, rely on missing resources, or repeatedly fail belong in a manual-recovery queue.

Validate access and layout

A successful export is not yet a verified archive. Inspect every high-value or complex PDF and sample simpler batches under a documented rule. Compare page count, dimensions, orientation, margins, text flow, images, colors, transparency, crop boundaries, and page order with the Publisher original.

Check publications that use unusual fonts from another authorized machine. For labels, folded sheets, and print-ready material, print representative pages at actual size and verify registration, folds, bleeds, and duplex order.

• Keep a manifest linking each original path to its PDF and any editable replacement.
• Record the conversion method, validation status, date, and reviewer.
• Calculate file hashes when the archive requires integrity verification.
• Retain migration logs and unresolved failures with the archive records.
• Confirm that another authorized user can retrieve and open the converted files without Publisher.

Complete a recovery test before access ends: select files from several source locations, retrieve their converted copies, and confirm that they open, print, and map back to the preserved originals. The archive is ready when the inventory has no unexplained gaps and every failed conversion has a documented resolution path.

Also read:

• Cowork Can Save a Workflow, but It Cannot Retire the Reviewer
• How to Protect PDF Files to Prevent Sharing
• Blockchain Alone Cannot Open Stock Exchanges—But It Can Cut Friction