Migrate Skill

SkillFiles & storage

Universal migration from Obsidian, Notion, Logseq, markdown, CSV, JSON, Roam

Available today. Use it from your connected AI after setup.

Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Then ask your AI: use the Migrate Skill skill

What this skill tells your AI

The instructions your AI receives, as published by inbrainfun/inbrain in skills/migrate/SKILL.md and read by ahel’s review.

Universal migration from any wiki, note tool, or brain system into Inbrain.

Contract

  • Source data is never modified or deleted; migration is additive only.
  • Every migrated page is verified round-trip: written to inbrain, read back, spot-checked.
  • Cross-references from the source system (wikilinks, block refs, tags) are converted to inbrain equivalents.
  • Migration is tested on a sample (5-10 files) before bulk execution.
  • Post-migration health check confirms page count, link integrity, and embedding coverage.

Supported Sources

SourceFormatStrategy
ObsidianMarkdown + [[wikilinks]]Direct import, convert wikilinks to inbrain links
NotionExported markdown or CSVParse Notion's export structure
LogseqMarkdown with ((block refs))Convert block refs to page links
Plain markdownAny .md directoryImport directory into inbrain directly
CSVTabular dataMap columns to frontmatter fields
JSONStructured dataMap keys to page fields
RoamJSON exportConvert block structure to pages

Phases

  1. Assess the source. What format? How many files? What structure?
  2. Plan the mapping. How do source fields map to inbrain fields (type, title, tags, compiled_truth, timeline)?
  3. Test with a sample. Import 5-10 files, verify by reading them back from inbrain and exporting.
  4. Bulk import. Import the full directory into inbrain.
  5. Verify. Check inbrain health and statistics, spot-check pages.
  6. Build links. Extract cross-references from content and create typed links in inbrain.

Obsidian Migration

  1. Import the vault directory into inbrain (Obsidian vaults are markdown directories)

  2. Wire the graph with native wikilink support (v0.12.1+):

    inbrain extract links --source db --dry-run | head -20    # preview
    inbrain extract links --source db                         # commit
    

    extract links natively parses [[relative/path]] and [[relative/path|Display Text]] alongside standard [text](page.md) markdown syntax. Ancestor-search resolution handles wiki KBs where authors omit one or more leading ../ prefixes. The .md suffix is inferred automatically for wikilinks.

Obsidian-specific:

  • Tags (#tag) become inbrain tags
  • Frontmatter properties map to inbrain frontmatter
  • Attachments (images, PDFs) are noted but handled separately via file storage

Notion Migration

  1. Export from Notion: Settings > Export > Markdown & CSV
  2. Notion exports nested directories with UUIDs in filenames
  3. Strip UUIDs from filenames for clean slugs
  4. Map Notion's database properties to frontmatter
  5. Import the cleaned directory into inbrain

CSV Migration

For tabular data (e.g., CRM exports, contact lists):

  1. For each row in the CSV, create a page with column values as frontmatter
  2. Use a designated column as the slug (e.g., name)
  3. Use another column as compiled_truth (e.g., notes)
  4. Store each page in inbrain

Verification

After any migration:

  1. Check inbrain statistics to verify page count matches source
  2. Check inbrain health for orphans and missing embeddings
  3. Export pages from inbrain for round-trip verification
  4. Spot-check 5-10 pages by reading them from inbrain
  5. Test search: search inbrain for "someone you know is in the data"

Anti-Patterns

  • Bulk import without sample test. Never import the full dataset before verifying with 5-10 files. The cost of cleaning up hundreds of bad pages is enormous.
  • Destroying source data. Migration is additive. Never modify, move, or delete the source files.
  • Ignoring cross-references. Wikilinks, block refs, and tags from the source system must be converted to inbrain equivalents. Dropping them loses the knowledge graph.
  • Skipping verification. A migration without post-import health check, page count comparison, and spot-check reads is incomplete.

Output Format

MIGRATION REPORT -- [source] -> Inbrain
=======================================

Source: [format] ([file count] files, [size])
Mapping: [field mapping summary]

Sample Test (N files):
- Imported: N/N
- Round-trip verified: N/N
- Cross-refs converted: N

Bulk Import:
- Total imported: N
- Skipped (duplicates/errors): N
- Links created: N
- Tags migrated: N

Verification:
- Page count match: [yes/no]
- Health check: [pass/fail]
- Search test: [query] -> [result count] hits

Tools Used

  • Store/update pages in inbrain (put_page)
  • Read pages from inbrain (get_page)
  • Link entities in inbrain (add_link)
  • Tag pages in inbrain (add_tag)
  • Get inbrain statistics (get_stats)
  • Check inbrain health (get_health)
  • Search inbrain (query)

Signals

GitHub stars
143
Forks
126
Last commit
Jul 2026
Advanced
Item type
skill
Key
migrate-inbrainfun
Source
github.com/inbrainfun/inbrain