Identify whether the problem is in permissions, page capture, file output or migration verification before changing tools or re-exporting everything. Reproduce it with one non-sensitive test document, record the observed result, fix that layer and verify the archive offline.
When an export fails, “the tool is broken” is usually too broad to be useful. A missing download button, half a document, broken images, missing attachments and a confusing migration can fail in four different layers: permissions, page capture, file conversion and migration verification.
Locate the layer first. Changing tools, clearing the browser cache or re-exporting the whole wiki often repeats the same failure at a larger scale.
Three fixed actions
Reproduce with one test document
Use a page with headings, text, a list, a table, an image and an attachment, and no sensitive information. Try another page or format to see whether the problem follows the document or the method.
Record the observed result
Write what you saw and where it failed. “Content is incomplete” is hard to diagnose; “the final three images after the second heading are missing” narrows the scope.
Do not start a full re-export
Confirm the cause on one page first. If a single export is unstable, a batch job will produce more failures and make them harder to track.
Four-layer triage table
| Layer | Common symptom | First check | Next action |
|---|---|---|---|
| Permission and entry point | You can read but not export, the download button is disabled or the extension does nothing | Web version, account permission and organizational policy | Ask the owner for the required access or use an approved workflow |
| Capture and conversion | Only the first half appears, collapsed content is missing or images never enter the result | Lazy loading, collapsed sections and tab changes | Confirm capture scope on a test page, then handle images or batch work |
| File output | Markdown images break, Word layout changes, PDF pages split badly or attachments remain separate | Remote links and independently downloaded files | Choose the right format and save media locally |
| Migration and verification | Counts look correct but folders, links, duplicates or permissions do not | Source scope, destination and cutoff time | Sample by risk, record failures and re-export only affected items |
Permission layer: confirm what you may handle
Reading and downloading are separate permissions. An organization may restrict export, copy, attachment download or external sharing.
Confirm:
- The document is open in the browser web app, not only inside a desktop client.
- The current account has the required read and download access.
- Company policy permits a local copy.
A browser extension can organize content the page already allows you to see. It should not and usually cannot bypass permission rules, download restrictions or account policy. The correct path is the document owner or administrator, not another random conversion tool.
Capture layer: why only part of the document appears
Online document editors load content around the viewport. Long sections, collapsed blocks, comments or attachment areas may not be available until they render.
Narrow the test to one question:
- Expand all the content that should be saved.
- Scroll through the page once to trigger lazy loading.
- Search the exported result for a phrase from the middle of the document.
- Try a short document to separate a capture-scope issue from a failed file.
If short documents work and long documents fail consistently, work on lazy-loaded pages rather than changing image or format settings.
File layer: the file exists but is still unusable
Four common gaps:
| Result | Problem | Check |
|---|---|---|
| Markdown | Images show as broken | Whether links still point to temporary Feishu URLs |
| Word | Headings, tables or pagination changed | Source structure and format compatibility |
| Content is split at the wrong point | Print layout and page breaks | |
| Attachment package | The text names a file that is missing | Whether attachments were downloaded separately |
Text, images and attachments should move together. Move the whole folder and open it offline to confirm it no longer depends on the original computer, login or session.
Migration layer: why correct counts can still produce a messy wiki
Batch migrations often preserve the number of pages while damaging hierarchy, internal links, duplicate handling and permissions.
Freeze the source scope and destination, then sample:
- Can the original path still locate the content?
- Can a phrase from the middle of a document be searched?
- Do images, tables and attachments open?
- Do internal links and cross-page references work?
- Are excluded permission-restricted items documented?
Record failures before re-running everything. Group them by page, batch or format, repair only affected items and verify them again.
A simple issue record is enough
For each investigation, record:
- Source URL or unique title
- Export method
- Observed and expected result
- Failed step or file path
- Whether the issue affects one page, one batch or one format
- Recheck result after repair
The record is not documentation for its own sake. It prevents the next investigation from starting again at “is the tool broken?”
When a full re-export makes sense
A full re-export may be justified when the source scope, account permission or export policy changes everywhere. Missing text, broken images or omitted attachments usually call for a small repair and verification pass instead.
A reliable export or migration ends with searchable text, visible images, openable attachments, understandable folders and documented permissions. Triage exists to find which of those failed as quickly as possible.