Feishu handles collaboration. Obsidian handles long-term personal notes. Two-way sync sounds like the natural bridge, but conflicts, renames and permissions soon make it expensive.
For finished material that only needs a local copy, a one-way migration is easier to check and maintain.
Why two-way sync is harder
A reliable sync must handle:
- Which version wins when both sides change.
- Rename, move and delete operations.
- Images, attachments and internal links.
- Future Feishu changes and plugin maintenance.
For a one-time migration, those costs usually exceed the benefit.
Clean up inside Feishu first
- Simplify merged tables and decide whether the complexity is necessary.
- Move important comments into the body because they may not export.
- Remove expired links and duplicate documents.
- Confirm titles and hierarchy.
- Select only content you are authorized to retain.
Doing this before export is faster than repairing the same problems inside Obsidian.
What the Markdown should contain
| Item | Recommended result |
|---|---|
| Body | Headings, lists, tables and code blocks preserved |
| Images | Local assets folder with relative paths |
| Frontmatter | At least title, source and import date |
| Folders | A rough match to the Feishu hierarchy |
| Links | Broken Feishu links clearly marked |
If images remain remote CDN links, the vault may look correct until the account changes or the machine goes offline.
A practical migration path
1. Export Markdown and images
Use an export that saves the body and images together. Markdown export is free. Image ZIP is a Pro tool for documents with many images.
2. Check outside the main vault
Place the export in a temporary folder and verify:
- Open three documents and check heading levels.
- Confirm that image files exist.
- Search for a term that appears once and confirm the paragraph is present.
- Move the folder and confirm the paths still work.
3. Import by topic
Keep imported material separate from active notes:
vault/
├── 00-inbox/
├── feishu-archive/
│ ├── project-a/
│ └── project-b/
└── assets/Keep source and imported_at in frontmatter if the vault contains several sources.
4. Check search before adding structure
Confirm full-text search, filenames and images first. Add tags and backlinks only after the imported archive is reliable.
What should not go into the vault
Large attachments, videos, executables and confidential files can make the vault heavy and complicate backup. Keep them in a separate resource area.
It is also unwise to treat a frequently updated collaborative Feishu document as a continuously maintained personal note. A one-way archive captures a point in time and should be explicit about that.
When a two-way plugin makes sense
Only consider two-way sync when changes must originate in Obsidian and return automatically to Feishu, and when you are prepared to manage conflicts and credentials.
For occasional edits, change the Feishu source and export again after it stabilizes. One-way migration gives up one background system and gains a clearer boundary.