notes-migrator

Tested with:

• Emacs versions
  • 29.0.5
• org-roam versions
  • v2.2.1

Purpose

To migrate notes from one software to another.

Fluidly taking notes is a powerful habit. In the quest of a fluent workflow, you (like me) might find yourself trying many software. In this repo I will put code I use to convert my notes from one software to another, so I can assess them with my actual of notes instead of just toying around.

If you want conversion b/w software not covered in this repo and are willing to get your hands dirty, please create an issue. I will assist you write the required code. Or you can create a PR if you have already written one.

Supported Conversions

org-roam to denote

Usage

1. Install and setup denote. org-roam notes will be copied, converted, and saved in denote-directory

   For example, this is what I have in my emacs-config:

   (use-package denote
     :config
     (setq denote-directory (expand-file-name "denotes" org-directory)
           denote-date-prompt-use-org-read-date t)
     (add-hook 'dired-mode-hook #'denote-dired-mode))
       

2. Load ./notes-migrator.el

   You can do this in one of the following ways:

   1. Copy paste it in an elisp buffer (e.g *scratch*), and run M-x eval-buffer
   2. Download this script somehow (e.g git clone https://github.com/bitspook/notes-migrator), and run M-x load-file to select this file
   3. If you use straight.el, you can do

      (use-package notes-migrator
        :straight (notes-migrator
                   :type git
                   :host github
                   :repo "bitspook/notes-migrator"))
              

   4. Press M-: in Emacs and copy paste below snippet in it

      (with-current-buffer (url-retrieve-synchronously "https://raw.githubusercontent.com/bitspook/notes-migrator/master/notes-migrator.el")
        (goto-char (point-min))
        (re-search-forward "^$")
        (delete-region (point) (point-min))
        (eval-buffer))
              

3. Run M-x migrate-org-roam-to-denote

Known limitations

• If you are using org-roam’s feature of having multiple nodes in a single file (having a ID on a subtree in a org-roam file treats the subtree as a separate note in itself), then the same file will result in multiple denote notes. The filename will be different (it is one file per sub-note), but original file’s complete content is present in each.