When the Bulletin Files Go Silent: Preserving Content After Publisher’s Retirement
Updated October 23, 2026

As Microsoft Publisher reached end-of-life in October 2026, churches and nonprofits face a hidden archive crisis—and a chance to preserve their stories.
On any given Friday afternoon in a church office, the same ritual plays out.
A volunteer or administrator opens last year’s harvest festival flyer. They change the date. Swap a photo. Update the potluck time. Maybe add a QR code.
Save. Print. Done.
No design degree required. No agency budget. No fuss.
For decades, this quiet workflow has lived inside one humble application: Microsoft Publisher.
That familiar workflow now needs a supported path forward.
The announcement many organizations missed Back to contents ↑
Microsoft Publisher retired from Microsoft 365 on October 1, 2026. Support for Publisher 2021 and Office LTSC 2021 ended on October 13, 2026. For churches and nonprofits still relying on Publisher, the priority is preserving access to years of accumulated work.¹
For churches, dioceses, synods, and nonprofits, this isn’t theoretical. It’s operational.
Because Publisher wasn’t used for glossy magazines or ad campaigns. It was used for the work that happens every week:
- Bulletins
- Ministry newsletters
- Donor mailers
- Event programs
- Community flyers
- Seasonal campaigns
The everyday artifacts of organizational life.
Faith organizations are already raising the flag Back to contents ↑
Across denominations, communications teams have begun alerting parishes and ministries to what’s coming.
A United Methodist conference published guidance urging churches to prepare for Publisher’s retirement and begin transitioning content before retirement.²
A Catholic archdiocesan support office warned parishes that after October 2026 they may no longer be able to create or edit existing Publisher documents.³
In the U.K., a Church of England diocesan communications resource noted Publisher’s discontinuation and advised churches to adopt alternative tools.⁴
Catholic diocesan bulletins have even begun inserting short notices flagging the retirement date and pointing staff toward replacement workflows.⁵
And church bulletin production vendors—who see thousands of parish files firsthand—have notified customers that Publisher has been discontinued.⁶
The pattern is unmistakable: awareness is spreading, but preparedness is uneven.
The archive problem hiding in plain sight Back to contents ↑
At first glance, Publisher’s retirement sounds like a software upgrade issue.
But for faith and nonprofit organizations, it’s something more personal.
Publisher files are not just documents—they are institutional memory:
- Anniversary programs from decades past
- Holiday service layouts reused each year
- Donor recognition booklets
- School graduation templates
- Outreach campaign designs
In many offices, there are folders labeled simply: “Bulletins – Old.”
Inside them? Hundreds—or thousands—of .PUB files.
When Publisher disappears, those files don’t vanish. But the ability to work with them might.
Why “just save as PDF” isn’t enough Back to contents ↑
Some organizations assume they can simply export everything to PDF and call the transition complete.
But PDFs are often visual endpoints, not living layouts.
You can view them. Print them. Archive them.
But editing next year’s Easter bulletin from a flattened PDF is like remodeling a building from a photograph of its exterior.
What teams actually need is continuity: the ability to bring past layouts forward into modern tools without rebuilding them from scratch.
Enter the migration moment Back to contents ↑
This is where the Publisher end-of-life becomes less of a disruption—and more of an inflection point.
Many churches and nonprofits are already standardizing on browser-based, collaborative platforms like Canva for day-to-day communications:
- Volunteers can help remotely
- Staff can co-edit materials
- Templates can be shared across ministries
- Brand consistency is easier to maintain
But moving forward is only half the challenge.
The harder question is: What happens to everything behind you?
Where Markzware enters the story Back to contents ↑
Markzware’s technology exists for precisely this kind of transition moment.
For decades, the company has focused on unlocking legacy creative files—preserving layouts, structure, and content so organizations can reuse rather than rebuild.
In the Publisher context, solutions like DesignMarkz for Canva are designed to help organizations bring .PUB content into modern, editable environments.
That means:
- Historical layouts can become future templates
- Weekly workflows don’t need to restart from zero
- Volunteers and staff inherit continuity, not chaos
Instead of a “cold break” in communications history, organizations get a bridge.
The deeper opportunity: preserving institutional storytelling Back to contents ↑
There’s a philosophical dimension to all of this.
Churches and nonprofits are, at their core, storytelling institutions.
Bulletins tell the story of a congregation’s rhythm.
Programs tell the story of its milestones.
Mailers tell the story of its mission.
When software disappears, those stories risk becoming static artifacts rather than living documents.
Migration—done well—is preservation.
What organizations should do now Back to contents ↑
The October 2026 retirement dates have passed, but teams can still preserve and migrate their remaining files. Practical first steps include:
1. Audit your archive
Locate and catalog .PUB files across shared drives, laptops, and backups.
2. Identify “living templates”
Prioritize materials that are reused annually or seasonally.
3. Test conversion pathways
Evaluate how legacy files translate into modern tools.
4. Build a continuity library
Create a forward-ready template system staff and volunteers can inherit.
From sunset to continuity Back to contents ↑
Software end-of-life events are often framed in technical terms: support windows, patch cycles, licensing changes.
But the retirement of Microsoft Publisher is, for many faith and nonprofit organizations, about something more human:
Continuity of communication.
Preservation of effort.
Respect for the work of volunteers and staff who came before.
The October 2026 retirement deadline has passed.
But it’s also an opportunity—to carry forward not just files, but the stories they contain.
REUSE YOUR CONTENT ONLINE
Bring Publishing Content to WordPress Back to contents ↑
Use the Design File to WordPress skill with OmniMarkz and a compatible AI agent to turn content from supported Publisher, InDesign, QuarkXPress, and PDF documents into editable WordPress drafts—with headings, paragraphs, and available images ready for review.
Follow the setup guide, connect your WordPress site, and try a sample publication. Review reading order, images, fonts, and layout before publishing; complex print designs may need adjustment for the web.
Creates drafts for review. Nothing is published automatically. The guide also covers InDesign, QuarkXPress, and PDF workflows.
References Back to contents ↑
- Microsoft Support — “Microsoft Publisher will no longer be supported after October 2026.”
- Desert Southwest Conference (UMC) — “Microsoft Publisher Is Going Away: What Churches Need to Know.”
- Archdiocese of Saint Paul & Minneapolis — “Goodbye, Microsoft Publisher!”
- Diocese of Hereford (Church of England) — “Traditional and Print Media.”
- Roman Catholic Diocese of Erie — Bulletin announcements (Mar 2025).
- LPi Bulletin Services — Publisher discontinuation guidance.

