Duplicate last week
Carry the layout, church details and existing sections forward for review.
Publisher reaches end of support in October 2026
Move the weekly bulletin before Publisher becomes the weekly emergency
Microsoft states that Publisher support ends on October 1, 2026 and that Microsoft 365 subscribers will no longer be able to access Publisher after retirement. Export the files you need and move the recurring bulletin workflow while there is still time to compare every page.
Source: Microsoft: Publisher will no longer be supported after October 2026
Replace the weekly process, not only the page file
A modern bulletin needs to solve more than layout
Moving to another blank canvas leaves the office with the same email chasing, copy fitting and version confusion. Church Bulletin Software turns the recognizable issue into a reusable church workflow.
Collect by role
Invite the pastor, music director and ministry leaders to only their assigned sections.
Proof the final issue
Check names, dates, links, images and page fit before the final visual proof and print run.
Publish for phones too
Create a live mobile issue from the same reviewed content instead of uploading a hard-to-read PDF.
A careful migration path
Move one representative issue before moving the weekly deadline
-
Protect the source files
Before October 1, open important .pub files in Publisher and export them to PDF. Keep the original .pub files, logos, photos and fonts together.
-
Choose a representative issue
Use a recent bulletin that shows the recurring cover, sections, columns, footer and normal page count.
-
Upload and review the reusable structure
The guided importer proposes church details, recurring sections, colors and layout clues beside the original. Select only the candidates you have checked.
-
Run one issue in parallel
Compare the new PDF with the old workflow before switching the office deadline permanently.
The change in practice
From a shared layout file to a guided bulletin system
| Weekly task | Typical Publisher workflow | Church Bulletin Software |
|---|---|---|
| Start the new issue | Copy and rename a file | Duplicate a reviewed issue and check carried content |
| Collect content | Email, messages and attachments | Private links scoped to each contributor’s task |
| Fit copy | Manual editing inside text boxes | Structured sections, guided shortening and a final visual proof |
| Review changes | Compare files and email threads | Submission status and side-by-side review |
| Produce print copies | Manual page and booklet setup | Print formats with practical preflight checks |
| Share online | Upload a PDF separately | Publish a responsive mobile issue from the reviewed source |
Optional done-with-you starting point
Bulletin migration service · $149 one-time
We rebuild one current exported PDF as a reusable church bulletin template, add the church’s core brand details and return it ready for the weekly workflow.
- One current PDF bulletin reviewed
- One reusable template
- Core colors, logo and recurring sections
- One print format and live mobile structure
- Migration review before handoff
What to send: one representative PDF, the current logo, the normal page size and notes about recurring sections. This service rebuilds the PDF as a new template; it does not directly convert or edit the .pub file.
Publisher migration questions
Know the boundaries before you move
Can Church Bulletin Software open a .pub file directly?
No. Open important files in Publisher and export them to PDF before retirement. The rebuild uses a representative PDF as the visual reference and creates a new reusable structure; it is not direct .pub conversion.
Should we keep our original .pub files?
Yes. Keep the originals as part of the church’s archive, along with exported PDFs, logos, images and font information. The new weekly workflow does not require those files.
Will the rebuilt bulletin look exactly the same?
The importer preserves reviewable structure and visual clues rather than promising a pixel-for-pixel conversion. Page flow can differ because the new template must also support structured editing and mobile reading.
Why run one issue in parallel?
A parallel issue lets the church compare content, page order, print behavior and office responsibilities before the new process becomes the only deadline path.
Can we rebuild the template ourselves?
Yes. Start free and upload a recent PDF or clear printed-page photo. Review the extracted candidates beside the original and apply only what is correct. The $149 assisted migration is optional.
Protect the source files first