How to migrate to Logseq db version

I have been a heavy Logseq user for the past two years, relying on it extensively to accumulate and organize all kinds of notes. Recently, I tried the new online database version of Logseq. However, the planned deprecation of namespaces is likely to disrupt my entire workflow, as namespaces are a critical part of how I organize my data.

I would greatly appreciate it if an experienced Logseq user or professional could take a look at my setup and provide guidance on how it might function in the new database-driven ecosystem.

Here’s some additional context about my setup:

  1. Dual Tools: In addition to Logseq, I use Obsidian within the same vault to complement my workflow.
  2. Namespace Automation: I autogenerate namespace-based pages using a URL tool (available here: https://notes.zealmaker.com/) and have open-sourced this approach on GitHub (repository link).
  3. Integration with Notion: These pages are dynamically created from links generated via Notion, which I use for project and task management.

Given the complexity of this setup and its reliance on namespaces, I am concerned about how it will translate to the new database paradigm. Any insights, suggestions, or strategies to adapt my system effectively would be incredibly helpful.

Thank you in advance for your time and support!

Regards,
Rahul

PS- My hosted notes https://zealmaker.com/notes/#/page/home

1 Like

Concerning namespaces, are you aware of this?

1 Like

I tried this. However I doubt it will work on page creation using URL. Additionally it has not worked for me for PPV/C_Study kind of names which have underscore in name