Skip to content
DocblockOpen workspace

Import and export

Bring the knowledge you already have.

An existing folder of notes is a useful starting point. Import Markdown files or a vault, review path conflicts, and keep a workspace archive available when you need a copy elsewhere.

01

Start from familiar files

Import Markdown files, a folder, a ZIP, or an Obsidian vault. Keep folder organization and supported note metadata rather than retyping your collection.

02

Choose how conflicts are handled

When an incoming path already exists, choose the import behavior described in the guide. Review the destination before bringing a large collection together.

03

Keep a portable archive

Export accessible notes as a ZIP with Markdown, Block definitions, properties, and included attachments. Keep the manifest with the files to restore that structure on import.

FROM IDEA TO USEFUL CONTEXT

Put it into practice.

  1. Choose the source

    Select your Markdown files, folder, vault archive, or a Docblock share URL.

  2. Review the destination

    Choose where the notes belong and decide what should happen to existing paths.

  3. Check and reuse

    Open the imported notes, verify links and metadata, and connect an agent or export a copy when useful.

A FEW USEFUL DETAILS

Questions, answered.

Can I import an Obsidian vault?

Yes. The import guide covers Markdown folders, ZIPs, and Obsidian vaults, including supported metadata and limits.

Is a share import a synchronization connection?

No. It copies the shared notes and records their source. Later changes to the source collection are not synchronized.

Does a workspace export include history and access settings?

No. The archive excludes version history, Trash, members, credentials, share links, and external files. It is a portable content archive.

KEEP EXPLORING

Connect the next piece.

A PLACE TO BUILD ON

Give your next thought a home.

Start with a note. Add structure, connect an agent, and keep the useful context together.

Open Docblock