Freeze the source scope and destination first, then compare high, medium and low-risk samples. Check hierarchy, text structure, images, attachments, internal links, duplicates and permissions. Record failures before re-exporting so only the affected items need another pass.
The easiest number to report after a migration is how many pages were exported. That number proves the job ran; it does not prove the original content is still readable in the right context.
Verification is not a second full migration. It is a fixed set of checks that finds concrete differences so only affected items need another pass.
Freeze the verification baseline
Before checking files, write down what this migration is supposed to represent:
| Item | What to record |
|---|---|
| Source scope | Spaces, folders and pages included in the migration |
| Destination | The local or target directory that should contain the result |
| Migration date | When the export and import took place |
| Exclusions | Content omitted because of permissions or policy |
| Owners | Who migrated, verifies and approves exceptions |
If the source wiki is still changing, freeze a destination snapshot or set a clear cutoff. Otherwise, a later difference may simply be a new source edit.
Six consistency checks
1. Folders and hierarchy
Check top-level folders, parent-child relationships and page order. Pay attention to renamed pages, duplicate titles, empty folders and cross-space documents.
Some hierarchy changes are unavoidable when platforms model folders differently. The result should still let a new reader follow a path back to the source instead of searching through flat files.
2. Document structure
Compare headings, lists, quotes, code blocks, tables and collapsible sections. Search for a phrase from the middle of a document to confirm that more than the opening survived.
A formatting change and missing content are different findings. A list becoming a paragraph may be conversion loss; a whole section disappearing is an integrity problem.
3. Images and media
Check whether images still point to temporary Feishu URLs and whether video, audio and attachments open offline. File names may change, but their order and relationship to the text should remain clear.
4. Separate attachments
A link inside a document is not proof that the attachment moved with it. Open the most important spreadsheets, PDFs, archives and source files rather than accepting a file name or download link as evidence.
5. Internal links
Internal links are among the first things to break. Test navigation-heavy pages, including folder links, anchors and cross-page references. If the destination cannot preserve the original URL, the page title should at least remain searchable.
6. Permissions and ownership
Confirm that the migration stayed within your authority. Sensitive attachments, customer files and internal discussions must keep appropriate access controls after moving to a new storage layer.
Sample by risk
A complete word-for-word comparison is rarely practical. Divide content by risk:
| Risk | Typical material | Verification |
|---|---|---|
| High | Image-heavy pages, complex tables, attachments, deep folders, many internal links | Check all or a large share |
| Medium | Project documents, meeting notes and operational instructions | Random sample |
| Low | Short text, one-page notes and stable reference material | Check titles and openability |
The exact sample size depends on the wiki, but high-risk pages should not rely on random luck. Record what was checked and what remained outside the scope.
Turn findings into an actionable list
Do not re-export everything as soon as one issue appears. Record:
- Source URL or unique title
- Destination file path
- Failure type: missing, duplicate, order, broken image, missing attachment or link
- Severity
- Owner
- Repair batch and recheck result
Repair only affected pages, then verify those items again. This preserves successful output and makes it clear where the conversion process failed.
Run a final usability test
Move the verified folder, open sampled pages offline, search for body text, open images, tables and attachments, and follow several internal links.
Ask someone who did not perform the migration to find three documents from the folder structure. If that person succeeds, the archive is closer to being independently usable.
What passing means
Verification does not require byte-for-byte identity with the source platform. It confirms four outcomes:
- The folders make sense.
- The text is searchable.
- Images and attachments open.
- Permissions and exceptions are documented.
A migration is complete when someone can say which content arrived reliably, what still needs work and who owns the next review, not when the export counter reaches 100%.