How to Migrate Your Notes to a New App (Without Losing Anything)

Why Note Migration Feels So Daunting

Switching notetaking apps should be straightforward, but in practice it is one of the biggest sources of friction in personal productivity. You have months or years of accumulated thinking in one tool, and the idea of losing any of it is genuinely stressful. The good news is that with a methodical approach, you can move to a new app without losing anything important — and you might even improve your system in the process.

Step 1: Audit Before You Export

Before touching an export button, take thirty minutes to review what you actually have. Open your current app and look at your notes with fresh eyes.

Ask Yourself

• How many notes do I have? Dozens? Hundreds? Thousands?
• When did I last touch most of them? If you have not opened a note in over a year, you probably do not need to migrate it urgently.
• What formats are involved? Plain text, rich text, images, attachments, drawings, tables?
• Is there a folder or tag structure? How important is preserving that hierarchy?

This audit usually reveals a surprising truth: most people actively use only 10-20% of their notes. The rest is reference material, old drafts, or things that felt important at the time but never got revisited.

Step 2: The Pragmatic Migration Strategy

Rather than migrating everything in one shot, use a tiered approach:

Tier 1 — Active Notes (Migrate Immediately)

These are the notes you use daily or weekly. Project plans, ongoing research, active meeting notes, personal dashboards. Move these first and make sure they look right in the new app.

Tier 2 — Reference Notes (Migrate Gradually)

Important but infrequently accessed. Past project documentation, recipes, travel plans, saved articles. Migrate these in batches over the next few weeks as you encounter them.

Tier 3 — Archive (Keep in the Old App)

Old notes you have not touched in a year or more. Rather than migrating these, simply keep your old app installed as a read-only archive. You can always pull individual notes over if you need them later.

This approach gets you productive in the new app within a day instead of spending a weekend fighting with import tools.

Step 3: Choose Your Export Format

Most notetaking apps support one or more of these export formats:

• Markdown (.md) — The gold standard for portability. Plain text with simple formatting. Almost every modern notetaking app can import Markdown files.
• HTML (.html) — Preserves more formatting than Markdown but is harder to edit directly. Good as a backup format.
• Plain text (.txt) — Maximum compatibility but you lose all formatting.
• PDF (.pdf) — Good for archiving but essentially read-only. Not useful for migration.
• Proprietary formats — Some apps use their own formats (like Evernote's ENEX). Look for community-built conversion tools if you are stuck with these.

The best practice: Export to Markdown whenever possible. It is human-readable, future-proof, and widely supported.

Step 4: Handle the Tricky Parts

Images and Attachments

This is where migrations most commonly break. Some apps embed images as base64 data, others link to cloud-hosted files, and still others store them in a local folder alongside the note. When exporting, make sure images are included as separate files and that your new app can reference them.

Internal Links

If your notes link to each other — common in Zettelkasten or wiki-style systems — those links will almost certainly break during migration. Document your most important links before exporting, and plan to recreate them manually in the new app.

Folder and Tag Structure

Export your folder or tag hierarchy as a simple text outline before migrating. This gives you a reference when rebuilding the structure. Some people use a migration as an opportunity to simplify their organization — if you had 47 folders before, maybe you only need 12.

Tables and Special Formatting

Complex tables, embedded code blocks, and custom formatting often do not survive migration cleanly. Check your most important formatted notes after import and fix any issues manually.

Step 5: Test Before You Commit

Before migrating everything, do a small test run:

1. Export 5-10 representative notes from your old app.
2. Import them into the new app.
3. Check formatting, images, and links.
4. Note any issues and figure out workarounds.

This ten-minute test can save you hours of frustration later.

Step 6: Set Up Your New System

Once your active notes are in the new app, take a moment to set up your organizational structure intentionally. Do not just recreate your old system blindly. Consider what worked, what did not, and what the new app does differently.

For example, if you are moving to a spatial canvas tool like OmniCanvas, you might organize notes visually on a canvas rather than in folders — grouping related ideas by proximity and using color or position to convey relationships that a folder tree cannot express.

Common Migration Pitfalls

• Trying to migrate everything at once. This leads to burnout and a messy new system. Use the tiered approach.
• Losing your old app too soon. Keep it installed for at least three months as a safety net.
• Perfectionism. Some formatting loss is inevitable. If the content is there, you can fix formatting as you use each note.
• Not backing up before export. Always make a full backup of your old app before starting any migration process.

The Liberating Truth

Migration is also an opportunity. Moving to a new app forces you to confront what you actually need and use. Many people find that the process itself — reviewing, pruning, and reorganizing — makes their note system dramatically more useful, regardless of which app they land on.