Moving your notes between apps: Notion, Obsidian and Joplin

Two different ideas of a note

Note apps look similar but rest on different ideas. Notion is a shared workspace where documents, databases and forms sit together, which suits people who want project information and written context in one place. Obsidian and Joplin are built around notes you keep yourself: Obsidian keeps working data locally on your device, and Joplin is an offline-first, open-source application that stores notes in Markdown.

That difference decides most of the trade-offs. A hosted workspace makes collaboration and structure easy and puts your data on someone else's service. A local-first tool gives you files you control and puts backup, synchronisation and sharing on you.

What each tool's record tells us

Notion has a free plan and paid Plus and Business plans, and paid costs depend on the number of billable members. Permissions and organisational controls vary by plan, so check that the tier you need includes what your team expects.

Obsidian's core application is free, including for commercial use, and it can be used without signing up. Optional Sync adds end-to-end encrypted synchronisation with version history, and Publish is a separate paid service. Joplin is free and open source, imports Markdown files and exported Evernote content, and can synchronise through services such as Nextcloud, Dropbox, OneDrive or Joplin Cloud, with end-to-end encryption available.

Prices and allowances change, so use these notes to decide what to test, and read the vendor's current pages before paying.

What usually breaks in a migration

Plain text moves easily. Structure does not. Databases with properties, relations and views, embedded files, comments, page permissions and internal links are the things most likely to arrive flattened or missing. That is not a criticism of any product; it is what happens whenever information leaves a system that models it richly and lands in one that stores files.

• Structured data: check that properties and relations survive, or accept a manual rebuild.
• Attachments and images: confirm they are copied, not just linked to the old service.
• Internal links: test a few pages that link to each other.
• Formatting: tables, checklists and code blocks are common casualties.
• Dates: creation and edit times may reset, which matters if you sort by them.

A safe migration plan

Treat the move as a project with a rollback, not an afternoon of dragging files. The steps below keep your original untouched until you are sure.

• Export everything from the old app and store the export somewhere separate as a backup.
• Import a sample of about twenty notes chosen for variety: long, short, image-heavy, table-heavy.
• Open each imported note and compare it with the original for formatting and attachments.
• Decide how you will back up and synchronise in the new tool before adding more material.
• Move the rest in batches, checking a few notes from each batch.
• Use both tools in parallel for two to four weeks, writing new notes only in the new one.
• Archive the old workspace instead of deleting it, and delete only when you have not needed it for a full month.

Backups and sync are your responsibility with local notes

Local files are not automatically safe. Obsidian's own record notes that local notes still need a backup strategy, and the same is true for Joplin. Decide where copies live, how often they are made and how you would restore them, then test a restore once. Encrypted synchronisation protects notes in transit and at rest on the sync service, but it is not a substitute for a backup.

If several people edit the same notes, test the shared workflow before you abandon a team workspace. The catalogue advises this for Obsidian's shared vaults specifically.

Rebuild your workflow, not just your notes

Notes are only half of what you are moving. The other half is the habits built around them: templates you copy for meetings, tags you use to find things, a weekly review, a place where tasks live. A migration that copies every page but forgets the workflow leaves you with an archive you do not use.

Before the move, write down the five routines you rely on most and decide how each will work in the new tool. Some will translate directly, some will need a plugin or a different structure, and a few you may decide to drop. Doing this on paper first is quicker than discovering the gaps one frustrating morning at a time.

Keep the structure simple at the start. Local-first tools reward a light folder and tag scheme, and hosted workspaces reward a small number of well-designed databases. You can add complexity later, once you know what you actually search for.

Which one fits you

Choose a hosted workspace when collaboration, permissions and structured project information matter most, and you accept a subscription tied to the number of people. Choose a local-first tool when ownership of the files, offline use and low ongoing cost matter more, and you are comfortable managing your own backups. If you are unsure, start with a small personal collection in a local-first tool: it is cheap to try, and Markdown makes leaving it easy.