Cloud autosave prevents some editing losses. It does not guarantee access after an account, permission or organizational change.
An individual or small team does not need to copy the whole company wiki. Define the files worth keeping, then decide how often, in what format and where they should live.
Four common triggers
Permissions change
You were a collaborator and are later removed from the space. If access remains under someone else’s control, the file is not fully yours to rely on.
The working relationship changes
A role change, offboarding or project completion can change ownership and access. Personal material should be organized before that point.
A document is deleted or rewritten
Cloud recovery exists, but historical versions expire and folder-level deletion can affect several documents.
You need offline or cross-platform use
Offline reading, note software, AI context and Git repositories all need a portable format.
Decide what to back up
| Priority | Content | Action |
|---|---|---|
| Must keep | Personal material you created and may retain | Save Markdown and images |
| Useful archive | Project material you depend on, with stable updates | Export once when the project ends |
| Handover only | Company assets, client files and restricted attachments | Follow policy; do not keep privately |
An inventory is safer than downloading whatever happens to be open.
How often
- Active documents: review changes monthly or weekly.
- Project material: export at project completion.
- Long-term archives: check readability every three to six months.
Do not apply one schedule to every type of content. Active work and final archives have different costs and risks.
Where to store the archive
| Location | Strength | Risk |
|---|---|---|
| Computer or external drive | Simple and offline | Device failure or loss |
| NAS | Central and multi-device | Still needs an offsite copy |
| Git repository | Clear history and diffs | Not suitable for private images or secrets |
| Another cloud drive | Easy access | Still a third-party service |
A stronger pattern is a local primary copy plus a separate medium or offsite copy. Copying one cloud drive to another does not cover every failure mode.
Three execution tiers
Fewer than twenty documents
Export one by one, organize by project or year, and confirm that images are local.
Dozens to hundreds
Use a batch queue. Export to a temporary directory, inspect it, then move it to the long-term archive. Feishu Toolkit Pro covers this tier.
Thousands with unattended operation
Use an API and scheduled job with logs, retries and verification. At this scale, backup becomes a formal data-governance process.
Verify the backup
Open three random documents offline, move the whole folder, and check images, tables and code blocks.
Keep a short record:
- Backup date
- Included scope
- Storage location
- Offline check result
- Next review date
An unverified export is only an attempt, not a backup.
Avoid these shortcuts
Do not upload sensitive documents to a public repository, retain content you are not authorized to keep, or assume that a second cloud drive is automatically a resilient backup.
The value of a second copy is not the number of copies. It is whether the content still opens when the first copy does not.