Backup & Archive

How to Name Feishu Backup Files and Track Export Versions

Organize Feishu exports into dated batches, track their sources and validation status, and avoid overwriting usable backups.

4 分钟4 min read 发布于 Nov 16, 2026Published Nov 16, 2026 更新于 Nov 16, 2026Updated Nov 16, 2026
本页结构 On This Page
直接回答Short Answer

Create a separate folder for every export batch, record its source and export time, and keep the original downloads unchanged. Organize a working copy and mark a batch as usable only after checking it.

Repeated exports can leave a downloads folder full of files called “Project notes” and “Project notes (1)”. A small folder convention makes it easier to identify the right copy without relying on names alone. This is a manual workflow, not an automatic naming feature of the extension.

Keep each export in its own batch

Use a folder such as Project-A_2026-11-16_1530/. Create another folder for the next export rather than overwriting the previous one. The timestamp describes the export, not the source document’s last edit.

Inside the batch, keep original-exports/, working-copy/ and inventory.md. Preserve downloaded files or ZIP archives in the original folder. Make naming and link changes in the working copy, keeping document assets together with the text.

Record sources, not just titles

FieldWhat to record
SourceOriginal URL and wiki location
Export timeDate, time and time zone
Local locationRelative path to the saved document
OwnershipExporter and reviewer
StatusUnchecked, passed or incomplete
GapsMissing attachments or online-only links

Put same-named documents from different projects into separate project folders. When renaming a file, record the old name and new location. A source URL helps trace a document; it does not prove the saved copy works.

Relative image paths depend on where the Markdown file and asset folder live. Moving either can break images. Try the convention on one document with images, internal links and attachments before applying it across a batch.

Open cross-document links too. If a link still leads to Feishu, mark it as requiring online access. Keep the original export so that an unsuccessful reorganization can be started again from an unchanged copy.

Separate downloaded from verified

Mark a new batch as unchecked. Review its text, images and important attachments before marking it as passed. Record gaps explicitly so the next person does not have to rediscover them.

Agree on a retention period before deleting older batches. Keep the previous verified copy until the replacement passes review. Restrict backup access according to the source material’s access rules.

Next, run a restore drill to check whether someone else can use the archive.