Find out what breaks before you migrate, not after.

Exitproof takes your Word documents and templates, converts them with LibreOffice, Collabora Online and ONLYOFFICE, and reports what each one changed.

It runs on your own machine, with no network access during conversion. No document leaves the building.

How a run works

1. Point it at a folder

   Every .docx, .dotx, .docm and .dotm underneath it. Duplicates and near-identical variants are grouped, so a corpus of 2,000 files is not reported as 2,000 separate problems.

2. Each document is read before it is converted

   Content controls, fields, form fields, tracked changes, comments, data bindings, text boxes, SmartArt, macros, and every font face the document asks for — recorded first, so there is something to compare against.

3. Every suite converts it twice

   Once to PDF, for what a reader sees, and once back to .docx, for what an editor gets. Conversion runs in containers with no network access.

4. The output is compared with the original

   Text against the printed page, page count and page images against a reference exported by real Microsoft Word where you supply one, and the round-trip .docx re-read feature by feature.

5. You get files, not a dashboard

   A self-contained HTML report, a row per document and per suite in CSV, an aggregate across the corpus with charts, and a structured log. Nothing is uploaded and there is nothing to sign in to.

What it measures

• Text. Every word the document should show, checked against the words that reached the printed page.
• Pagination. Page count against the Word reference, so "it grew by a page" is a fact and not an impression.
• Layout. Page images compared with the reference, page by page, with the worst pages and a difference heatmap.
• Fonts. Which faces the document asks for, which have a metric-compatible substitute, and which ones actually ended up embedded in the output.
• Structure. A content control, a field or a form control that quietly became plain text is caught by re-reading the converted file, not by looking at it.

Every finding carries a severity, the evidence behind it, and a fix suggestion written in advance rather than generated, so what you read is reviewable and identical on every run. The methodology is published in full.

What it will not tell you

Macros are detected, never executed and never converted. A document whose logic lives in VBA will convert as a document and still not work as a tool.

Status

Exitproof is in development. A corpus of public-sector templates is being measured now; the findings are published once a human has confirmed them, not before. If you want them when they land, or a run against your own templates, say so here.