How Commercial Printers Can Keep Customer Publisher Files Working
Your customer’s next print run can begin with the work they already have.
For a repeat print job supplied as a Microsoft Publisher file, preserve the .pub original, request a customer-approved reference, and test the intended editing output before estimating the full job. Conversion and press-ready approval are separate steps.
A customer asks for another run of a brochure, with a new telephone number and a revised offer. The only editable source is a Microsoft Publisher file from an earlier job. Before quoting a complete rebuild, find out what the document contains and what your production team can reuse.
The useful question is not simply whether a file converts. It is whether the converted result supports this customer’s next job, with a review process your team can repeat.
Publisher support ended in October 2026; perpetual editions can still run. Check Microsoft’s retirement notice for your license.
In this article
- Start at customer-file intake
- Test the next production step
- Give approved content another destination
- Example: estimate a repeat brochure with one changed phone number
- Before you reuse the result
- Publisher Migration FAQs for Commercial Printers
Start at customer-file intake
Keep the supplied .pub file intact and work from a copy. Request the customer’s approved PDF or printed reference, together with available linked photographs, logos, and font information. An old reference helps establish what the customer expects; it does not confirm that every detail is still current.
Record the requested change, intended output, deadline, and person responsible for approval. A repeat brochure, a new layout, and a website update need different deliverables.
- Check page size and count against the reference.
- Flag missing assets or uncertain fonts before promising a turnaround.
- Confirm which prices, dates, addresses, and offers need updating.
- Separate material approved for reuse from content the customer intends to retire.
Test the next production step
Choose a representative publication before converting a whole customer archive. Include a job with the kinds of tables, photographs, and text arrangements your team regularly receives. Test the supported output in the actual editing application you plan to use.
Compare the result with the reference at both page and detail level. Look for changed line breaks, clipped copy, substituted fonts, image cropping, and unexpected page geometry. Keep a short exception log so an estimator can distinguish routine correction from a substantial rebuild.
A successful conversion is a useful starting point. It does not make the job press-ready. Complete your normal proofing and production checks, including bleed, image quality, color handling, and the final output file.
Give approved content another destination
The same brochure may hold useful service descriptions, staff introductions, or event information for the customer’s website. Treat that as a separate editorial assignment: agree which material should move online, who owns it, and who approves the result.
An editable web draft can make updates easier, but a folded leaflet should not dictate the reading order of a responsive page. Turn the selected material into clear sections, verify links, and check image permissions before the customer publishes it.
This gives your team a practical conversation about reuse: another print run, a refreshed design, or selected website content. Start with the customer’s need and quote the review work as carefully as the conversion.
Example: estimate a repeat brochure with one changed phone number
A one-line customer change can still expose missing fonts or image problems. Run a representative file through intake, editing, and proof review before promising a simple correction.
- Intake: Record the supplied filename, requested change, deadline, page size, reference PDF, and available fonts and linked assets.
- Conversion test: Open the supported output in the receiving layout application. Check the changed text and nearby line breaks, then compare every page with the reference.
- Production review: Check image resolution, bleed, page geometry, color handling, and final output using the shop’s normal preflight process. Obtain customer proof approval.
Separate the estimate into conversion, manual correction, and proofing work. Log a missing logo or substituted font as an exception with a named next action. An output that opens successfully should not be quoted as finished production work.
Accept the workflow when the production editor can make the requested change, document the remaining corrections, and produce a proof the customer can review. Use measured correction time when estimating the next group of customer files.
Watch the audience overview
Before you reuse the result
- An untouched original and an approved visual reference are retained.
- The destination application opens the sample as expected.
- Corrections and missing assets are documented.
- The customer has approved the final content and proof.
OmniMarkz can inspect and convert supported Publisher files; available outputs vary by workflow.
Use the WordPress setup guide with OmniMarkz and a compatible AI agent; review drafts before publishing.
Publisher Migration FAQs for Commercial Printers
Can this workflow handle file types other than Microsoft Publisher?
Yes. The Design File to WordPress workflow covers supported Microsoft Publisher (.pub), Adobe InDesign (.indd), QuarkXPress (.qxp), and PDF files, creating editable drafts with a compatible AI agent and configured WordPress access.
OmniMarkz also supports workflows involving Illustrator (.ai), IDML (.idml), and Affinity files. For these additional formats, confirm the available preview, inventory, extraction, and conversion options for your product, platform, version, and license before planning a WordPress migration. Test a representative file of each type and review the resulting content and images.
Can I see what is inside a customer’s Publisher file before quoting the job?
Preview supported files and review their document inventory with OmniMarkz before estimating. Check page count, fonts, images, and usable content, then test the intended output on a representative file. Quote conversion, corrections, and production review according to what the sample actually requires.
Can the same Publisher publication support both a print job and a WordPress article?
Yes, where the source content and available assets are suitable. Keep the original file and approved print reference, then prepare a separate editable web draft. Review the print output and the responsive WordPress version for their different destinations.
Will conversion remove the need for preflight?
No. Review the converted document and final production output using your normal preflight and proofing process.
Should every archived customer job be converted?
Prioritize returning customers and publications with a known next use. Keep uncertain or incomplete jobs in a separate review group.
Compare Microsoft Publisher migration and conversion options before selecting a destination workflow.
Give your publications a useful next step
Choose a representative publication and a clear destination. The audience guide brings the next steps together for your team.
Next in the series · Keep Church and Nonprofit Publisher Content Working for the Next Volunteer
Explore all Keep Your PUB Files Working audience guides →
File support, output quality, and editability depend on the source, available fonts and assets, and destination. Test representative files before expanding. The optional WordPress workflow requires setup and review; additional costs may apply.
References & further reading
