migrating-to-dblisted

# 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 ```bash # Create timestamped backup cp -r ~/logseq/my-graph ~/logseq/my-graph-backup-$(date +%Y%m%d) # Or compress tar -czvf my-graph-backup.tar.gz ~/logseq/my-graph ``` ### 2. Audit Current Structure **Pages to