Migrate notes by preserving the source library first, testing the destination with a representative sample, and verifying content before changing or deleting the old account. An export file is evidence of a backup, but it is not proof that the destination can reproduce every note feature.
Inventory what must survive
Count notebooks, folders, notes, attachments, tags, shared notes, links between notes, scans, drawings, audio, reminders, tasks, and locked content. Identify the features that matter most to the daily workflow. Record a few representative notes for each feature, including one large note, one with several attachments, and one with nonstandard formatting.
Check who owns shared notebooks and whether collaborators need a separate migration plan. Export only material you are authorized to move. Remove unrelated secrets from test samples and use a protected local folder for the export.
Create a source export
Use the source app's supported export function rather than copying the visible text alone. Choose the most structured format available, plus a readable format if practical. Evernote's export documentation allows desktop exports in ENEX or HTML. Google Takeout guidance explains how to create an archive of selected Google product data and warns that recent changes may not appear if they occur between the request and archive creation.
Save the export date, source app version, account, selected content, file count, total size, and format. Keep the original archive unchanged. Make a working copy for conversion or import so an unsuccessful attempt does not alter the only preserved copy.
Confirm destination compatibility
Read the destination app's current import documentation. Map source features to destination behavior before importing. Some formats preserve structure better than others, and unsupported features may become plain text, embedded files, or separate notes. For example, Apple Notes documentation lists supported import formats and can preserve a folder structure when importing a folder on Mac. That capability does not guarantee that every feature from another service transfers identically.
Import the representative sample first. Compare note titles, body text, headings, lists, tables, attachments, links, tags, dates, folder placement, searchability, and sharing state. Open files rather than trusting attachment icons. Check the sample on every device type that will be used.
Run and verify the full migration
Freeze editing briefly or record a cutover time so new source changes are not missed. Import the full working copy, then compare counts by folder and search for distinctive phrases from the sample. Review failures and duplicates. Preserve a list of items that need manual repair, and do not silently discard unsupported features.
Keep the source account and original export until the new library has been used and verified. Test offline access, synchronization, sharing permissions, links, and a second-device sign-in. Confirm that backups or future exports can be produced from the destination.
Close carefully
After verification, update integrations and shortcuts that pointed to the old app. Cancel billing separately if required. Download a final delta export for notes changed after the first archive. Only then consider deleting the source account, following its retention and deletion instructions. Keep the original export in protected storage according to the sensitivity of the notes.
Sources
- Export Notes and Notebooks as ENEX or HTML — Evernote
- How to download your Google data — Google
- Import or share notes and files to the Notes app — Apple Support