Vendor lock-in becomes a practical problem when leaving a note-taking app would discard information, structure, access, or working time that the user reasonably needs. A proprietary feature is not automatically harmful, and switching always has some cost. The warning signs are missing or untested exit paths, incomplete exports, account restrictions, and workflows that cannot be reproduced elsewhere.
The export exists only on certain accounts
Check whether the documented export applies to the exact account and storage type in use. Microsoft says full OneNote notebook export through OneNote for the web is available for notebooks stored in personal OneDrive, but it does not work for notebooks stored in work or school OneDrive or SharePoint. An export button seen in a tutorial is not evidence that a managed workspace has the same path.
The export omits important structure
Create a test notebook with sections, pages, links, tags, attachments, drawings, and dates, then export it. Open the result without the normal app and list what survives. Plain text may be sufficient for some users, while a research or project archive may require attachments, link targets, authorship, timestamps, and hierarchy. Treat undocumented omissions as a migration risk.
The archive cannot be restored or imported
A downloadable file is not useful merely because it exists. Test a bounded import into a disposable notebook or another tool, and compare the result with a known sample. If the original app supports recovery only from its own server-side history, document whether that history remains available after cancellation. Keep the live notebook unchanged while testing.
Bulk export is difficult to repeat
A healthy exit path can be performed by an authorized account owner on a predictable cadence. Warning signs include one-page-at-a-time export, hidden size limits, manual attachment retrieval, archives that expire before they can be downloaded, or repeated failures with no documented recovery. Google Takeout illustrates a more explicit pattern: users can choose product data, create an archive, and download it without deleting the server copy. That still requires opening and checking the archive.
Ownership depends on one person
Review who owns shared notebooks, billing, encryption keys, recovery methods, and integrations. Test what happens when the primary owner is removed. A team should not rely on one personal address or device to authorize every export. Do not share passwords as a workaround; establish supported administrator or ownership-transfer procedures instead.
Links and integrations hide dependencies
Inventory clipped web pages, embedded files, task links, email capture, calendars, and automation. Determine whether exported notes contain the underlying content or only references that stop working after the subscription ends. Record rate limits and permissions for approved integrations. A note collection can be portable while its surrounding workflow remains locked to a vendor.
Pricing blocks the exit path
Check whether export, version history, administrator access, or API use requires a higher plan. Record current terms and verify them before a migration because plan features can change. Estimate staff time for cleanup and validation separately from any vendor fee. Do not describe future pricing as guaranteed.
There is no tested transition window
Plan an overlap period in which the old system remains readable while the new system is checked. Migrate a representative sample first, then compare counts, text, attachments, dates, and access. Avoid deleting the source or cancelling the account until the authorized owner accepts the test. Keep a dated inventory of what was moved and what remains.
Use a selection standard
Before adopting or renewing an app, require a documented export for the actual account type, a readable sample archive, a tested import or restore path, clear shared ownership, and an estimate of exit effort. Accept limitations that match the value and risk of the notes. Reject a tool when essential content can be accessed only through an untested promise that it will be portable later.
Sources
- Export OneNote notebooks — Microsoft Support
- How to download your Google data — Google