Switch Note-Taking Apps Without Losing Track of Your Notes

Nemos is our own app, so weigh what we say about it with that in mind.

This guide is a verification workflow, not a promise that every pair of apps can transfer every feature. The examples use current export and storage documentation from Notion, Joplin and Obsidian, reviewed on November 2, 2026. We have not performed a hands-on migration benchmark. Use harmless sample material while deciding whether your particular source, format and destination work together.

Write your migration contract first

Before choosing an export format, make a short list of what must survive. “My notes” is too vague to test. A recipe collection may need images and source links; a research archive may need PDFs and internal links; a journal may depend on dates and the order of entries. Mark each requirement essential or optional.

Do not turn this into a huge spreadsheet. A simple note with the sample titles, expected files and a pass-or-problem column is enough. It gives you something concrete to compare when the new app's layout makes the archive look different.

Keep an untouched source package

Use the source app's documented export feature and save the result somewhere you can identify later. Name the folder with the source and date, and keep the original download unchanged. Work from a copy when extracting archives or preparing an import. If a conversion fails, you should be able to return to the same source package rather than repeat an increasingly confusing series of changes.

Read the export options carefully. Notion's documentation distinguishes PDF, HTML, and Markdown with CSV for databases. It also describes including subpages and separately saved assets. Pages the exporter cannot access may be omitted, and an export cannot simply be reuploaded to recreate the workspace instantly. Export scope matters as much as the format name.

If the export is generated on desktop or web, do that part there and use the iPhone for the checks that matter on the phone. Do not assume a mobile share action and a full workspace export produce the same package. Confirm the supported route in the current documentation for your app.

Choose a format for the job

A readable archive and an editable migration are different goals. Keep a readable reference when appearance matters, but check the destination's supported import formats before deciding how to move editable notes. A file extension alone does not tell you whether tags, links or attachments will map into the new system.

Joplin's import guide gives a useful example of the tradeoff. Its Evernote ENEX import can bring notes, tags, attachments and metadata across, while complex formatting and recognition data need separate consideration. It also warns that links between notes may not always be restored correctly, including when titles are ambiguous. Do not treat that as a universal defect in every migration; use it as a reason to test the features your archive actually uses.

For an archive that must return to its original app, inspect that app's native backup format as well. Joplin documents JEX as a format that preserves notes and metadata for reimport into Joplin. That is a different purpose from assuming another application can read the same file. Choose a destination-supported exchange format separately.

Move a small, deliberately awkward sample

Start with several notes that expose likely problems rather than only your simplest text. Include an older note, a recent note, an image, a PDF or other attachment, a long note, a checklist, and two notes linked to each other. Add repeated titles if your library contains them. These are suggested checks, not results from tests we ran.

Import that sample into a clearly named test area when the destination supports one. Keep a record of the source note and destination note so you can compare them directly. If a feature changes form, write down the change: for example, a tag may become text, a nested folder may become a flatter collection, or a checklist may arrive as ordinary text. Whether that is acceptable depends on your migration contract.

When something is missing, stop before importing the full archive. Check whether the source package contains it. If it is absent there, investigate the export settings; if it exists there but not in the destination, investigate import support. That split helps you ask a precise support question instead of reporting only that the migration failed.

Treat attachments as files, not previews

Obsidian's attachment documentation explains that attachments are regular files in the vault and can live in different configured locations. This makes a useful general check: keep the note files and their associated asset folders together while evaluating an export. Moving only text files can leave references pointing somewhere you did not move.

Open the sample attachments from inside the destination. Check a full-size image and a multi-page document. A thumbnail or a filename is not the same as the underlying file opening correctly. For a link to an external page, check whether the note holds a URL or an actual stored copy; those are different things to preserve.

Use the iPhone for a second check after the destination finishes its initial sync or download. Reopen your sample there and try the searches you wrote down earlier. If you need offline access, disconnect the network and inspect those same notes and files. Record what is available instead of inferring whole-library offline support from one cached note.

Switch over in batches

Once the sample meets your requirements, move one manageable collection and repeat the checks. Compare titles and counts, but also open representative content. Equal counts can hide a missing attachment or a link that opens the wrong note.

Decide where new notes will go during the transition. Write down a cutover date and keep a short list of changes made in the old app after its export. Otherwise, you can end up with two diverging libraries and no clear answer about which version to trust. Avoid repeated full imports into the same destination unless you understand its duplicate-handling behavior.

Keep the original archive until you have verified the result and understand recovery. Do not cancel a service, delete a notebook or remove an old device simply because the import completed. Check what access you retain before making that decision. This guide cannot guarantee a lossless transfer between products; the verification steps help expose problems while you still have the source.

For related decisions, see private notes and encryption boundaries, offline notes on iPhone and the capture-first note-taking workflow. Choosing where to capture future material is separate from proving that an old archive transferred correctly.

Where our app fits

Nemos is our own app, so weigh what we say about it with that in mind. Nemos keeps links, notes, screenshots and files in one library. Nemos lets you search saved links, notes and text in screenshots. Nemos is free to download, with optional in-app purchases.

FAQ

Which export format keeps everything?

There is no universal format that preserves every feature across every app. Compare the source's export options with the destination's import documentation, and test the fields and files you need. Keep a native backup separately when available.

Can I migrate using only my iPhone?

It depends on the apps and export scope. Check current platform requirements. A single-page export and a full workspace export may have different supported routes, so use desktop or web when the documented workflow requires it.

When can I delete the old notes?

Wait until you have verified representative notes, attachments, links and search, and have a recovery plan. Keep the original export unchanged while checking the destination. Do not use an import success message as your only evidence.

Sources

Reviewed November 2, 2026: Notion export documentation, Joplin import and export documentation and Obsidian attachment storage. Product examples illustrate documented boundaries; they are not a hands-on migration comparison or a guarantee about other applications.

Last reviewed: 2026-11-02