Primary-source migration plan · September 3, 2026

Move Notion to Outline or AppFlowy without confusing source access with open source.

A workspace export is useful evidence. It is not a working replacement for permissions, database behavior, automations, search, or the habits built around them.

Start with the export boundary

Notion exports pages as HTML or Markdown and databases as CSV, with uploaded files when included.
The export omits pages the operator cannot access, and teamspace settings can exclude more content.
Only the current or default database view can be exported at once; full-page database behavior is not a CSV file.
Notion itself says an export cannot instantly recreate a workspace by reuploading it.

Inventory the authorized scope and operational behavior before choosing a destination. Do not put workspace content or user data in a public migration ledger.

Choose with a representative pilot

Outline

Shortlist when: A team knowledge base with collections and nested documents is the main job.

Current import boundary: Outline accepts Notion exports and offers a Notion integration from v0.83.0. Its documentation says fidelity cannot be guaranteed. Its BSL 1.1 license is source-available, not open source, and restricts Document Service use.

Prove before cutover: Hierarchy, files, links, collections, authorship, users, groups, permissions, search, and destination export/restore.

AppFlowy

Shortlist when: A Notion-like workspace with documents and databases is the main job, and the team can validate product-specific workflow differences.

Current import boundary: AppFlowy's hosted importer accepts a Notion ZIP and creates a new workspace, with completion reported by email. Its main repository is AGPLv3; verify the license of every deployed component and edition.

Prove before cutover: Documents, nested pages, database row pages, views, properties, formulas, relations, rollups, assets, links, clients, and export/restore.

Stop or narrow the move

Shortlist when: Permissions, database behavior, comments, integrations, automations, or public links are material and the pilot cannot reproduce them.

Current import boundary: Keep the export as evidence, not as proof that a destination can run the work.

Prove before cutover: A smaller migration scope, an explicit coexistence period, or a different destination with an owned repair plan.

The license boundary is part of the decision

Outline: the current repository uses Business Source License 1.1 and states that it is not an open-source license. Its additional-use grant restricts operating a Document Service for third parties.

AppFlowy: the main AppFlowy repository is AGPLv3. That does not prove that every hosted service, web component, packaged client, or commercial feature has the same boundary.

Record the exact component, version, edition, intended use, and license. Obtain qualified review when the use is commercially material.

Separate import fidelity from hosting

A successful import does not prove a self-hosted service is operable. Name owners for identity, SMTP, database, object storage, TLS, backups, restore, monitoring, upgrades, security response, user support, and incidents.

AppFlowy Cloud's documented deployment includes multiple services such as authentication, Postgres, Redis, and object storage. Outline also needs its own supported infrastructure. If those responsibilities lack owners and failure tests, pilot a hosted path or stop.

Primary sources

Run the migration ledger

The corrected free v0.15.1 kit contains a license boundary, source-scope inventory, destination pilot matrix, hosting ownership gate, reconciliation, cutover, and rollback checks.

Run the free migration kit ↗Request migration help Build a software shortlist

Get the next decision note

One maintained recipe each week. Explicit opt-in, no vendor-paid ranking, unsubscribe any time.