How to Migrate Word Documents to Obsidian

To move Word documents into Obsidian, convert a sample to Markdown, check its text and images, then import into a staging folder in your vault. Keep the original Word files until you have checked the migration. A successful conversion is the start of the process: properties, links and image paths still need review.

Start with a representative sample

Choose a short note, a table-heavy document and a document with images or equations. Inventory legacy .doc files separately from .docx files. Save a copy of the original library and preserve source filenames and folder paths. Two different files named Plan.docx must not become one Plan.md when you flatten folders.

Option 1: use the Word converter

1. Open Word to Markdown and sign in or create a free account. Conversions use credits.
2. Select your documents, convert, and download the Markdown results.
3. Put them in a staging folder such as Imports/Word/ inside your vault.
4. Open each sample in Obsidian and compare headings, tables, lists, links, images and equations with the Word original.

The tool converts document structure, not Word's page layout. Word images are represented by generated descriptions or placeholders, not extracted original image files. Check those descriptions against the source; use local media extraction or add the original images yourself when your vault needs the pictures. See multiple Word documents to Markdown for volume workflows.

Option 2: use Pandoc locally

Pandoc reads DOCX and writes GitHub-Flavored Markdown. Legacy .doc requires conversion to DOCX first. Its manual explains media extraction and warns that complex document conversion can lose formatting. Use a separate media directory for every document to avoid colliding image filenames.

This Bash example runs from a folder containing .docx files. Replace the destination with your actual vault path. It stages one folder per document and refuses to overwrite an existing import:

vault="$HOME/ObsidianVault/Imports/Word"
mkdir -p "$vault"
for f in *.docx; do
  [ -f "$f" ] || continue
  base="${f%.docx}"
  dest="$vault/$base"
  if [ -e "$dest" ]; then
    printf 'Already exists, review separately: %s\n' "$dest"
    continue
  fi
  mkdir -p "$dest"
  source_file="$(pwd)/$f"
  (cd "$dest" && pandoc "$source_file" -f docx -t gfm --extract-media=media -o "$base.md")
done

Running inside each destination makes extracted media references relative to that note. Inspect the paths and images before moving anything. Keep each note and its media folder together. The example handles a single folder; preserve hierarchy or assign unique names for nested libraries. Failed imports can leave a partial destination: inspect it before retrying.

Add properties without replacing your notes

Use Obsidian's Properties interface or add a YAML block manually. Record the original path, import status and useful tags. The import date is not the original creation date. Use a YAML-aware serializer for automated metadata: quotes, colons and multiline titles need escaping.

Move only reviewed imports into your chosen Projects, Resources or Archive folders. Conversion reruns can overwrite annotations: create a new staged result and compare it with your curated note instead of treating repeated conversion as harmless.

Restore links and check attachments

Turn genuine cross-document references into [[Note name]] links or standard Markdown links. Review ambiguous titles manually. Global regex replacements can modify code, existing links and frontmatter; preview changes on copies before applying them.

If you centralize images, update the paths actually written by your converter and resolve duplicate filenames first. An absolute disk path that displays on one machine may fail after sync. Test a note in its final folder and keep portable relative references.

Check the migration before retiring Word copies

• Compare text at the beginning, middle and end of important documents.
• Check tables, equations, footnotes and meaningful links.
• Open images from the final note location.
• Check properties and tags.
• Search for a distinctive phrase and follow a restored link.
• Back up the vault and verify that notes and assets travel together.

For mixed libraries, PDF to Markdown, URL to Markdown and Audio to Markdown feed the same review-and-organize workflow.

Related workflows

• how to test Word formatting preservation
• a Markdown editor
• how to benchmark Word to Markdown converters
• word tables guide