Preserve the Publisher source
Keep the original .pub file unchanged and work from a copy. Record the source filename, approximate Publisher era, page count, intended size and any known special fonts. Check long linked stories, tables, numbered steps, screenshots, headers, sections and page references after Publisher import.. If a reliable PDF or printed reference exists, keep it beside the migration project for visual comparison.
Import supported content as editable objects
Megal Publisher uses its own direct PUB import engine to reconstruct supported pages, text, pictures, shapes, tables, borders and layout data as editable Megal objects. It does not require Microsoft Publisher or LibreOffice behind the scenes. Import is a starting point for review, not a promise that every proprietary effect or font will reproduce identically.
Audit the publication systematically
Check page size and count first, then compare object positions, fonts, text wrapping, images, tables and decorative elements. For this training handbook, pay particular attention to check long linked stories, tables, numbered steps, screenshots, headers, sections and page references after publisher import.. Review course purpose and outcomes, module sequence, explanations and examples, activities or checklists and references, assessment and support contacts against the reference. Fix structural problems before fine visual differences so later edits do not have to be repeated.
Create the editable Megal master
Once reviewed, save an .mpub working file and retain the untouched .pub and reference proof. Test an ordinary edit: change text, replace or crop an image, move an object and reopen the saved project. Then create the required PDF or print proof. Proof contents and cross-references, writable spaces, page breaks and duplex or binding margins in the final handbook.. Archive the approved output with notes about any accepted conversion differences.