Compare note-taking apps by running a small round-trip portability test, not by accepting a checklist that says "export available." Examine what leaves the service, what another tool can import, which metadata survives, and what account or administrator restrictions apply. Treat data ownership as a practical set of controls—access, export, deletion, sharing, and account continuity—rather than an unsupported legal conclusion.
Build a representative notebook
Create a test set containing plain text, a checklist, headings, formatting, links, image and document attachments, handwriting if relevant, labels or tags, pinned and archived states, a reminder, a shared note, and a collaborator comment. Use invented information. Record the source app, account type, operating systems, sync state, and features that matter to the real workflow.
Write must-have outcomes before comparing products. A student may require offline access and PDF hand-in. A research team may need attachments, authorship, revision history, and durable links. A regulated business may need administrator controls and retention evidence. Portability is only meaningful relative to those needs.
Distinguish complete export from a snapshot
Ask whether the app exports one note, a notebook, or the entire account. Inspect whether the package contains text, attachments, structure, labels, timestamps, collaboration state, and a documented import path. Microsoft says its whole-notebook OneNote export applies to notebooks in personal OneDrive, not work or school OneDrive or SharePoint, and notes that notebook import functionality is deprecated. Account context therefore changes the practical exit route.
A printable copy is useful but not equivalent to editable portability. Microsoft's OneNote PDF guidance describes the PDF as a static snapshot that does not update with the notebook. Test whether search, links, attachments, checkboxes, and hierarchy remain useful after export instead of counting file creation as success.
Inspect coverage and restrictions
Google's Keep export guidance says an export can include note text, list items, attachments, colors, archived or pinned status, collaborators, and labels. It also warns that work or school accounts may be restricted by the organization. Record the administrator dependency alongside the feature comparison; a route the user cannot invoke is not a usable personal exit plan.
Check export frequency limits, package size, attachment handling, password or encryption implications, link expiration, and whether deleted or archived items appear. Do not put secrets into a portability test. If an export arrives by email or download link, verify who can open it and when it expires.
Run a round-trip test
Export the representative notebook and preserve the original package. Read its manifest or file structure and compare item counts. Import into a separate test account or another candidate application only where supported. If no supported import exists, evaluate a documented conversion path and the effort required to rebuild structure manually.
Compare text, headings, checkboxes, links, images, documents, tags, dates, reminders, authorship, comments, and ordering field by field. Open several attachments. Search for distinctive test terms. Repeat on a second device and offline if that is a requirement. Record losses rather than smoothing them over with a single pass/fail score.
Evaluate practical control
Separate content control from service control. Who holds the account? Can the user change the recovery address, remove a collaborator, revoke a public link, export without an administrator, close the account, and obtain a usable copy first? What happens to shared material when an employee or student leaves an organization? Which features depend on a paid plan?
Also review the privacy, retention, and deletion documentation current at decision time. Do not infer legal ownership from the presence of a download button. If legal rights, regulated records, or intellectual-property transfer matter, obtain qualified advice and preserve the provider terms reviewed.
Score evidence, not promises
Use separate scores for export coverage, importability, fidelity, administrative independence, offline access, collaboration continuity, and effort to leave. Attach test evidence and date it because product behavior changes. A vendor-neutral conclusion might be that one app offers the best static archive while another better preserves editable structure.
Choose only after the candidate passes the workflow's non-negotiable fields. Keep periodic exports if they are useful, document how to read them, and retest after account, plan, or administrator changes. The strongest option is the one that keeps notes usable through an actual exit, not the one with the longest feature list.
Sources
- Export OneNote notebooks — Microsoft Support
- Export notes from OneNote as a PDF — Microsoft Support
- Export your data from Google Keep — Google Keep Help