Agent skill · writing content · aiskillstore
migrating-to-db
Expert guidance for migrating Logseq graphs from Markdown (MD) format to the new Database (DB) format. Auto-invokes when users ask about MD to DB migration, converting graphs, import options, data transformation, or compatibility between Logseq versions. Covers migration strategies, common issues, and best practices.
Why this skill is useful
Provides specific migration strategies and commands for converting Logseq graphs from Markdown to Database format that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Migrating to Logseq DB When to Use This Skill This skill auto-invokes when: User asks about migrating from Logseq MD to DB version Converting markdown graphs to database format Import/export between Logseq versions Questions about what transfers during migration Namespace handling during migration Tag-to-class conversion decisions Property type inference during import User mentions "migrate", "convert", "MD to DB", "markdown to database" You are an expert in migrating Logseq graphs from MD (Markdown) format to DB (Database) format. Migration Overview Why Migrate? Feature MD Version DB Version --------- ------------ ------------ Storage Markdown files SQLite database Tags Page references Classes with properties Properties Text strings Typed values Queries Limited Full Datalog Sync File-based Real-time (subscription) Performance File I/O dependent Optimized queries Current Status (2024-2025) Important: Logseq DB is still in alpha. Consider: Data loss risk exists Some features not yet available (whiteboards) Plugin compatibility varies Requires subscription for sync Pre-Migration Checklist Before migrating, assess your graph: 1. Backup Everything 2. Audit Current Structure Pages to review: [ ] Namespaced pages (a/b/c) → May become separate pages [ ] Pages with same name, different namespaces [ ] Template pages [ ] Query pages Properties to review: [ ] Property formats (key:: value) [ ] Multi-value properties [ ] Date properties [ ] Linked properties ([[page]]) Tags to review: [ ] Simple tags (#tag) [ ] Page tags ([[tag]]) [ ] Nested tags (#parent/child) 3. Identify Migration Decisions MD Pattern DB Options Decision Needed ------------ ------------ ----------------- #tag Class or page ref Which tags become classes? [[page]] Node reference Keep as reference property:: value Typed property What type? namespace/page Separate page or hierarchy Flatten or nest? Migration Process Step 1: Export from MD Version 1. Open your MD graph in Logseq 2. Go to Settings → Export 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/migrating-to-db