How to Replace Microsoft Publisher Without Losing Layouts

To replace Microsoft Publisher without losing your layouts, work from a checklist: inventory every .pub file, batch-export them to PDF as a safety net, choose a replacement tool, rebuild your repeating templates once, and give your team an hour of hands-on practice. The catch nobody warns you about is geometry. Publisher's exact box positions don't survive most conversions, so plan a short cleanup pass per file instead of expecting a perfect one-click move.

Publisher reaches end of life on October 1, 2026, and Microsoft has confirmed it won’t ship a successor. Churches, schools, nonprofits, and small businesses now have a hard deadline. Here’s the reassuring part. Treat this as a project with five clear steps instead of a fire drill, and a small org can finish in a weekend. An org with hundreds of files might need a few weeks. For the full timeline and what stops working, see our breakdown of Publisher’s October 2026 end of life.

Step 1: Inventory every .pub file you actually use

You can’t migrate what you can’t find. Before you open any tool, build a plain list of what exists.

Search every machine and shared drive for .pub files. On Windows, run a search for *.pub across your Documents folder, the network share, and any USB sticks. That usually flushes out the strays. Don’t forget the volunteer’s laptop and the files buried in old email attachments.

Then sort what you find into three buckets:

• Live documents you reprint or re-edit regularly: the weekly bulletin, the monthly newsletter, the menu, the price list.
• Templates disguised as documents: the flyer you duplicate every event, the certificate you fill in by hand each term.
• Archive you only need to read or reprint occasionally: last year’s programs, old postcards.

Most organizations are surprised by how small the live set turns out to be. A church might have a bulletin, a flyer template, and a directory. A school might have permission slips, a couple of certificates, and one event poster they reprint every spring. That short list is what actually needs a replacement editor. Everything in the archive bucket might only need a PDF.

Step 2: Batch-export every file to PDF as a safety net

This is the step people skip, and it’s the one that saves them. Before you migrate anything, capture a faithful PDF of every .pub file while Publisher, or a tool that opens it, still runs.

Why go to PDF first? A PDF freezes exactly how the document looked, so you always have something to print or check against even if a later edit goes sideways. And for archive files you’ll never reopen, the PDF is the whole migration. Once it exists, that file is done.

If you still have Publisher installed, its built-in Export to PDF handles this fine. If your subscription has already lapsed or you’re on a fresh machine, open each .pub and export a PDF with Korva’s free tier. That includes the free browser converter, which runs entirely in your own tab and uploads nothing. Got a large pile? The free korva-cli has an export subcommand, so you can script the whole folder in one go.

One thing about color. Korva exports an RGB PDF, which is what you want for digital sharing, office printers, and most short-run community printing. If a particular document is headed to a commercial offset press that demands CMYK with crop marks and bleed, flag it now and take that file straight to your print shop. Be honest about which files those really are. For the average bulletin, flyer, or newsletter, RGB is exactly right.

Step 3: Choose a tool to replace Microsoft Publisher

There’s no single right answer. The right answer depends on your files and your team. Here’s a fair comparison of the realistic options:

A few honest notes on each. LibreOffice Draw and Scribus are both capable and genuinely free, and they run offline, but neither opens .pub files natively, so you’d rebuild every layout by hand. Scribus is the strongest pick if you do real prepress work and need CMYK. Microsoft 365 keeps you in a familiar suite, except Word and PowerPoint aren’t page-layout tools, and you’re paying a subscription forever. Online converters are fast for a single file. The problem is they require uploading your document to someone else’s server, which rules them out the moment a file holds member names, donor records, or student details.

Korva sits in a specific spot. It opens your existing .pub files, pulls out the text and every embedded image, and reflows them onto a clean editable page, so you’re not starting from a blank canvas. It runs entirely on your computer. No account, no cloud, no telemetry. The reader and converter tier is free forever, and the full editor is a one-time US$49 covering two seats with no subscription. Korva is an independent product, not affiliated with or endorsed by Microsoft. For a wider survey of the field, read our roundup of Publisher alternatives.

Step 4: Rebuild your master templates (just once)

This is where the “open and fix” reality matters, so let me be straight about it.

When Korva opens a .pub file, it reads the documented text and image streams inside the file and reflows them onto a page. It deliberately doesn’t try to decode Publisher’s undocumented internal geometry, the fragile part that breaks other converters. Your words and pictures come back intact. The exact box positions won’t be pixel-perfect, so you’ll nudge a few things into place.

That sounds like a chore until you notice you only do it for templates, and only once. The workflow goes:

1. Open your master .pub (the bulletin, the flyer, the certificate).
2. Let Korva import the text and images.
3. Spend ten to twenty minutes tidying. Drag boxes into position with the snapping guides, resize photos, fix a font size or two.
4. Save it as Korva’s native .pwl format. That’s your new clean master.

From then on you open the .pwl, not the .pub. The cleanup is already paid for. Spread that one-time tidy across a file you reprint every week and it barely registers.

If a document is simple enough, starting from a built-in template can beat fixing an import. Korva ships seven of them: Blank Letter, Blank A4, Church Bulletin, Event Flyer, Business Card, Certificate, and Address Labels. The bulletin template is a sensible place to start if you’d rather build fresh, and we walk through it in how to make a church bulletin.

One more time-saver to set up now. If you used Publisher’s mail merge for name badges, certificates, or labels, Korva does the same job with a .csv file and {{field}} placeholders, producing one filled page per row. The Business Card, Certificate, and Address Labels templates come mail-merge ready.

Step 5: Train the team in one short session

Migrations stall when one person learns the new tool and everyone else keeps emailing them files to fix. Head that off by getting people on keyboards early.

You don’t need a course. For most teams a single 45-to-60-minute walkthrough does it:

• Open a .pwl master and make one real edit, like changing the date on the bulletin or swapping a photo.
• Show double-click to edit text in place, drag to move, the eight resize handles, and arrow-key nudging.
• Demonstrate Undo, which goes back up to 100 steps so nobody is scared of breaking something, and the help overlay you reach by pressing ?.
• Export a PDF and confirm what’s on screen is what prints.

Korva runs offline on Windows 10+, macOS 12+, and 64-bit Linux, and the same files open on all three. So a mixed-device team (the office PC, the pastor’s Mac, the volunteer’s Linux box) works from identical documents. Install it everywhere before the session so nobody sits there blocked.

A realistic timeline

For a small org with under a dozen live files, this is a focused weekend. Inventory on Friday evening. Batch-export PDFs and rebuild two or three templates on Saturday. Train the team Sunday afternoon. For a school or larger nonprofit with deep archives, give yourself two or three weeks of part-time effort. Most of that goes to step two, batch-exporting the archive, and step four, rebuilding the handful of templates you actually reuse.

The deadline is firm, but the work has limits. You almost certainly have fewer files that genuinely need rebuilding than you think.

Frequently asked questions

Can I still open my old .pub files after Publisher is gone?

Yes. Publisher loses support and leaves Microsoft 365 in October 2026, but your files don’t self-destruct. A tool that reads .pub directly, like Korva’s free tier, can open them and export a PDF or let you edit, for free, for as long as you need.

Will my layout convert perfectly?

No conversion is pixel-perfect, and anyone promising that is overselling you. Text and images come across reliably. Exact box positions need a short cleanup, roughly ten to twenty minutes per template, done once. Documents you only archive skip cleanup entirely by becoming PDFs.

Do I have to pay to replace Microsoft Publisher?

Not necessarily. Opening .pub files and exporting PDFs is free in Korva forever, and LibreOffice Draw and Scribus cost nothing either. If you want full editing without a subscription, Korva’s editor is a one-time US$49 for two seats. See current details on the pricing page.

Is it safe to use an online .pub converter for member or donor files?

Online converters upload your document to a server you don’t control, which is a poor fit for anything holding personal data. An offline tool keeps the file on your machine. Korva’s free web converter is the exception among browser tools, because it processes the file inside your own tab and never uploads it.

What about CMYK and professional print?

Korva exports faithful RGB PDFs, which suit digital use along with most office and community printing. For commercial offset jobs that need CMYK, crop marks, or bleed, hand those specific files to your print shop, or use Scribus, which is built for prepress.

Start with the cheapest, safest step. Open one .pub file in Korva’s free converter and export a PDF. Once you’ve watched your content come back clean, the rest of the checklist is just follow-through.