-
-
Notifications
You must be signed in to change notification settings - Fork 463
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import from Roam's JSON export #411
Comments
You may choose to export to markdown instead, here's a gist that I tried that seems to work, using https://gist.github.com/jethrokuan/370e14b6cd9b7725b815bbdd0cb923fe |
Thanks! Some things I noticed:
2 and 3 work together for |
There's another issue with aliased internal links, like https://gist.github.com/AyeGill/72744b0e54ebf898268beb8c992cabd5 Another thing that doesn't work is "nested links" - in Roam, you can have a link as part of a page title, and this "just works" when linking to that page. |
Probably easiest to write elisp to do this, sed was just a quick experiment. I'll do it if there's enough demand for it. |
Hey @jethrokuan, if you do, would you mind doing a screencast of you coding it? |
Sure, I don't really mind. It's a bit separate from this project though, so might not be so relevant. |
I second this request. I'd love to migrate from Roam Research, but doing manually is a very tough endeavour. It'd improve the adoption of Org Roam too. |
I wrote a tool that converts Roam Research exports into Org-roam compatible markdown: https://github.com/fabioberger/roam-migration |
RoamResearch provides a way to export your entire database as JSON. This feature would allow importing that data into org-roam. This would enable people with existing personal Roam DBs to fully switch to org-roam.
The text was updated successfully, but these errors were encountered: