Feishu Export

How to fix links and organize tags after importing Feishu docs into Obsidian

Map exported Feishu URLs to local Obsidian notes, resolve duplicate titles, and use tags to track which links you have reviewed.

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

Map each original Feishu URL to a vault path. Convert confirmed destinations to path-qualified wikilinks, retain links to online documents, and use review tags to track unresolved notes.

Open an imported note and click “Release checklist.” If the browser opens Feishu, the Markdown still points to the source document. If Obsidian opens a different checklist with the same title, qualify the link with the folder path. Try both fixes on a small batch before editing the entire vault.

Export a few cross-linked documents as Markdown with Feishu Toolkit and copy them into a test vault. If the export includes an image directory, copy it alongside the notes and keep the relative layout. In a spreadsheet, record each full source URL and the corresponding path, such as Product/Release checklist.md or Operations/Release checklist.md.

Use the source URL to resolve each destination. Two documents with the same title can belong to different workspaces. If a URL points to a specific section, record that separately and check the heading in the imported Markdown.

Current destinationWhat to do
Imported document with a confirmed mappingUse [[Operations/Release checklist|Release checklist]] to retain the display text
Document still in use online or awaiting importKeep its original URL and record why it stays online
Specific section in an imported noteCheck the heading and link to [[Operations/Release checklist#Rollback]]
Image reference or external websiteKeep its existing Markdown syntax

Make the changes in one note and click each destination before applying the same mapping to the rest of the batch. If colleagues use standard Markdown editors, keep the original export or use relative Markdown links in the shared copy.

Use tags to track review status

Add #migration/needs-review to notes with unresolved links and #migration/checked after inspection. Keep any existing project tags. A release checklist and a rollback log can share a project tag while a direct wikilink records the relationship between them.

Review the remaining tagged notes before moving to the next batch. For each sample, check the source URL, a duplicate-title link, a section link, and a local image. Keep the mapping sheet so future imports can resolve links that still point online.