Import your notes

Banter is markdown-native, so anything you can export as markdown can come in. There’s no built-in bulk importer yet — the import path is an AI agent connected over MCP, and it works better than a dumb importer would, because the agent can propose structure instead of mirroring your old mess.

1. Export from your current app

• Notion — Settings → Export all workspace content, format “Markdown & CSV”. Import the markdown; database CSVs are usually better recreated by hand or summarized by the agent.
• Obsidian — your vault already is markdown. Use the folder as-is.
• Apple Notes — use an exporter (e.g. the built-in share-to-Markdown per note, or a batch exporter app).
• Craft — export documents as markdown.

2. Connect an MCP client

Set up the Banter MCP server with Claude, Claude Code, Codex, or another MCP client. Claude Code is the best fit for imports — it can read your export folder from disk and write to Banter in the same session.

3. Let the agent propose structure first

Before importing anything, ask:

Here’s an export of my old notes. Propose a Banter folder structure for it — don’t create anything yet.

A good structure is a few top-level folders, two or three levels deep. See Folders and naming for what works.

4. Import small, then review

Start with one active project, customer, or class — not the whole archive:

Import everything related to Acme into /Work/Acme. Keep note titles descriptive.

Review the result in Banter. If the filing looks right, import the rest in batches. Old, inactive material often isn’t worth importing at all — you can always come back for it.

Getting back out

Everything you import (and everything Banter creates) exports as markdown in one click — see Export and portability.