A Ventura archive should not be migrated as a folder of anonymous files. It should be treated as a collection of publications with dependencies, production history, and different preservation goals.
The objective is usually not “convert everything to one new format.” A good migration creates durable access copies, editable modern content, and a record of what was lost, substituted, or still requires the original Ventura environment.
1. Freeze the source archive
Before conversion, make a read-only archival copy of the complete source tree. If material is still on floppy disks, Zip disks, optical media, or old hard drives, image or copy the media before opening files in applications that may rewrite them.
Do not rename files or flatten old directories until you know how the projects reference one another.
2. Inventory and classify
Record filenames, extensions, sizes, dates, directory relationships, and likely Ventura generation. Early Xerox Ventura projects can consist of a .PUB publication, multiple .CHP chapters, .STY style sheets, .CAP and .VGR companions, font-width tables, text files, and linked artwork. Later Corel-era publications may use different structures, including .VP files.
Classification matters because a recovery tool that understands an early multi-file CHP project is not automatically a parser for a later Ventura 10 publication.
3. Recover complete project sets, not isolated files
When a project is multi-file, keep the whole set together. Old File Viewer, for example, can reconstruct Xerox Ventura 1.x–3.0 projects when the related files are supplied together and reports missing companions. It can export page-oriented or text-oriented results without uploading the files.
4. Define two outputs for important publications
For material worth preserving, create at least:
- A preservation rendering — usually PDF, intended to preserve the appearance and page sequence.
- An editable migration copy — DOCX, HTML, structured text, Markdown, or another format appropriate to the future workflow.
One does not replace the other. PDF is excellent for access and visual comparison but poor as the only editable source. A clean DOCX may preserve the words while losing exact layout.
5. Preserve structure, not only text
Where possible, retain headings, paragraph-style roles, lists, footnotes, tables, captions, image associations, page breaks, index markers, and other document semantics. A migration that reduces a carefully tagged book to a stream of unstructured paragraphs may technically recover the text while destroying much of the value of the original production system.
6. Handle fonts and character encodings explicitly
Old Ventura projects may depend on code pages, Type 1 or TrueType fonts, printer width tables, Symbol or dingbat fonts, and other assumptions that no longer match a modern Unicode workflow. Record substitutions and test punctuation, accented characters, symbols, and languages instead of trusting visual spot checks alone.
7. Validate the result
For each publication, compare representative pages and structural elements:
- first and last pages;
- chapter openings;
- tables and captions;
- footnotes/endnotes;
- figures and linked artwork;
- page-number sequences;
- TOC and index entries;
- special characters and unusual fonts.
Large archives benefit from automated counts—pages, images, chapters, extracted text length—combined with manual review of representative files.
8. Keep a migration manifest
A manifest should say what source files belonged to the publication, what outputs were created, which tool/version performed the conversion, what warnings occurred, what fonts were substituted, and whether a human checked the result.
That information becomes especially valuable years later when somebody asks why two versions differ.
9. Do not discard the Ventura originals
Migration is not proof that the originals are worthless. Keep them with the manifest, checksums, and any required companion files. Future recovery tools may extract information more accurately than today’s tools.
A practical target set
For many archives, a strong preservation package is:
- original Ventura project set;
- SHA-256 checksums;
- PDF preservation copy;
- editable DOCX or structured HTML;
- images in their original or normalized formats;
- plain-text extraction for search;
- migration manifest.
Sources and tools
If your archive is already available as Ventura marked text, Publishing Tools for Corel Ventura includes a Migration Studio for mapping that structure back into a modern workflow.
