How to export your data from Notion: full guide

How to export your data from Notion before a renewal or exit

A renewal, a plan change, a data residency rule or a lock-in concern can all force a Notion workspace to leave, and the first practical step is getting the content out. Notion exports pages and databases as PDF, HTML, Markdown and CSV, and workspace owners can export all workspace content in one job. That workspace-wide export has limits: Notion says it can take up to 30 hours, and the download link expires after 7 days, so the file must be downloaded and stored within that window. Some content will not come out. Form view databases are not exported, and private pages the exporting account cannot access are skipped, so a full export is only as complete as the permissions of the person running it. Check this before relying on the archive: have a workspace owner run a test export, open a sample of pages and databases, and compare them against a list of critical spaces. On Enterprise plans, a workspace admin may have disabled exporting in the security settings, and Notion's Enterprise plan also offers an Admin API for scheduled exports, so confirm which option your administrators can use before the exit date.

Be clear about what the export does not cover. Notion's HTML and Markdown output keeps text and structure, but permissions, comments, page history, workspace-level integrations and the relations and rollups between databases do not carry over as working features. Plan separately for user accounts, groups and access rules in the target system, and for any Notion AI or automation content that you need to keep. Agree the target platform before you start exporting, because the format you choose should match what that platform imports. Docmost, for example, accepts Notion exports, and its documentation lists which importers are available in its paid edition, so confirm that detail with the vendor before you commit. Treat the export as one step in a longer exit. Keep a dated copy of the archive, record which spaces were exported and by whom, and run a short reconciliation after import. Ask your migration partner or internal team to confirm, in writing, what will be carried over, what will be rebuilt by hand and who signs off on the result.

Which Notion content exports, by method, format and limit

This table compares the Notion export routes by scope, format, plan and who can run them. Read it to decide whether a single page, a database or the full workspace is the right starting point, and which limits apply to each route.

Export route	Formats available	Plan or role needed	Limits to plan for
Single page or database	PDF, HTML, Markdown and CSV (databases as CSV)	Any member with edit or export access to the page	Only pages the exporter can access are included
Page with Include subpages	PDF	Business or Enterprise plan	Subpages are included only in this option, and only for PDF
Full workspace export	Pages and databases in Markdown and CSV, plus HTML where offered	Workspace owners only	Can take up to 30 hours to complete
Download link from workspace export	Single ZIP archive	Workspace owner who started the export	Link expires after 7 days, so download promptly
Form view databases	Not exported	Not applicable	Rebuild forms or export responses separately
Private pages the exporter cannot access	Not exported	Not applicable	Ask page owners or a workspace owner to grant access first
Scheduled or automated exports	Via Admin API	Enterprise plan	Confirm the current Admin API scope with Notion before planning
Export disabled by admin	None	Enterprise security settings	Confirm with the workspace admin before the migration starts

What Notion skips and how to recover it

A Notion export is useful but not complete. Form view databases, pages the exporter cannot reach, and Enterprise workspaces where exporting has been switched off all leave content behind. Each gap needs a named owner, a check against the export, and a decision before the workspace is shut down.

Form view databases

A workspace export does not include databases shown as form views. The records exist, but the form layout that people use to read or submit them is not carried into the export. Before you export, list every database that uses a form view and check whether its records appear in the table or board views. Where they do, export those views as CSV. Where they do not, copy the field definitions and the submitted entries into a structured tool such as Baserow or Grist, or into a spreadsheet, and rebuild the form there. Confirm the current behavior with Notion before you rely on it.

Private pages the exporter cannot access

The person who runs the export only receives pages they can open. Private pages owned by other members, and pages shared with individuals who have since left, may be silently left out. Ask each page owner to review their private content and share the pages that must move, with edit or view access as appropriate. Then compare the list of pages in the export with a list of known pages from the workspace sidebar or search. Any gap should be resolved with its owner before the export is treated as complete.

Enterprise exports disabled by admins

On Enterprise plans, a workspace admin can turn off exporting in the security settings. When this is set, members cannot start an export at all, which blocks a migration before it begins. Ask the Enterprise admin in writing to enable export for a defined migration window, and to name the person who will run it. Ask whether the Admin API can schedule the export instead, since it is part of the Enterprise plan. Once the export is complete, ask the admin to restore the previous setting and record the change.

Confirming gaps before cutover

Treat every gap as a known item rather than a surprise at cutover. Keep a short register that lists each skipped database, each private page, and each person who has agreed to share content. Re-run a sample export after the owners respond and compare the results with the register. Keep the Notion workspace readable until the register is empty, because a page that is not exported today can still be opened and copied by hand in Notion.

How the export files are structured and what they lose

The export format you choose decides what survives the move. Markdown and HTML keep page text, headings, lists and the parent-child hierarchy of subpages, but they do not carry every block style, color, toggle state or inline layout detail that Notion renders. Expect the visual layout of a page to change even when its words arrive intact, and plan a review pass on the pages that rely on columns, callouts or embedded content. Databases are different. They come out as CSV rows, one file per database, with the property values flattened into cells. Relations, rollups, formulas, linked views and filters do not survive as working logic, so a database that powered a dashboard in Notion becomes a static table after export.

Before you import anything, open the ZIP and check its structure. Confirm that folder names match the page hierarchy you expect, that each page has a file and that attachments sit alongside the pages that reference them, and that no page appears twice or is missing. Look for filenames that contain Notion's generated identifiers, because those can break internal links when a target tool rewrites paths. Count the pages in the export against what your workspace owner reports, and sample a few pages from the deepest levels. Access also matters: pages the exporter cannot reach are skipped, so the ZIP is only as complete as the permissions of the account that ran it.

Do not assume the importers in your target tools behave alike. Docmost's import dialog accepts Markdown and HTML, BookStack and XWiki each handle folder structures, images and attachments in their own way, and some tools map the parent-child hierarchy differently from others. Run a test import of a representative sample, covering nested pages, images, tables, code blocks and any page with a database link, into a non-production instance of each candidate tool. Record what changed, what broke and what needed manual repair, and ask the vendor or community which fields and folder conventions their importer expects. The results of that test, not the export format alone, should drive your migration plan.

The order to run a complete Notion export

This sequence turns a Notion workspace into a dated, inventoried archive that you can check page by page before any migration starts. Each step ends with an output you can verify, so gaps show up while the source workspace is still available.

Inventory pages and databases with owners
Before exporting, list every top-level teamspace, page tree and database in the workspace, and record who owns or last edited each one. Mark pages you suspect are private or shared only with a few people, because the workspace export skips private pages the exporter cannot access. Store the inventory as a spreadsheet, since it becomes your reference for the verification steps later. The step is done when every teamspace has a named owner and each database has a row with its view count.
Confirm the owner or admin role
Only workspace owners can run a full workspace export, so confirm with your Notion admin which accounts hold that role and whether your plan allows it. On Enterprise, ask whether an admin has disabled exporting in the security settings, since that setting blocks the export regardless of role. If you are not an owner, arrange for one to run the export while you keep the inventory. The step is done when you have written confirmation of the account that will run the export and the workspace settings allow it.
Decide the format for each content type
Choose Markdown or HTML for pages you want to read in a wiki or static viewer, and PDF where page layout and fidelity matter more than editing. Plan CSV for databases, since a page export does not rebuild database structure. Note that PDF export of subpages depends on the plan, so confirm whether your plan includes that option before relying on it. The step is done when each row in your inventory has a target format and a note on what that format loses.
Run the workspace export
From the workspace settings, start the export of all workspace content in the format you chose for pages. Notion states that a full export can take up to 30 hours, so start it when someone can monitor it and keep the request confirmation. Record the start time, the account used and the format selected. The step is done when Notion sends the notification that the export is ready.
Download the archive before the link expires
The download link expires after 7 days, so download the ZIP as soon as the notification arrives and save it to storage you control. Keep the original file unchanged, and store a second copy in a separate location. Note the download date in your inventory, because an expired link means running the export again. The step is done when the ZIP is on your storage and the download date is recorded.
Export databases separately as CSV
Export each database you inventoried as CSV from its own menu, since a full workspace export does not capture form view databases and the page export does not rebuild database relations or views. Keep a note of which views and filters applied, because CSV carries the rows and columns but not the view configuration. Save each CSV with the database name in the file name. The step is done when every database in your inventory has a matching CSV file.
Compare page counts and check attachments
Count the exported pages and compare the total with your inventory, then list every page the export skipped or that you could not open, and resolve those with the owners. Open a sample of attachments, images and embedded files to confirm they were included and not replaced by placeholders. Log every difference in the inventory. The step is done when each gap is either fixed or documented with an owner and a reason.
Open sample pages and record a checksum
Open a set of pages across different teamspaces, including long pages, pages with tables and pages with images, and compare them with the originals in the archive. Then generate a SHA-256 checksum for the ZIP and each CSV file using a command such as sha256sum, and save the results alongside the inventory. The checksum lets you prove later that the archive has not changed. The step is done when the sample checks pass and the checksum file is stored with the archive.

Questions buyers ask before exporting their Notion data

How long does a full Notion workspace export take?

Notion says a full workspace export can take up to 30 hours, so the figure matters for scheduling more than for cost. Start the export early, not on the day a cutover is due, and plan for the download link to expire after 7 days. Large workspaces with many attachments are the ones most likely to run long, so ask your team to size the workspace before setting a date. Repeat exports are needed if content changes after the first pull, so plan a final delta export close to cutover.

Can a workspace member who is not an owner run a full export?

Full workspace export is an owner action in Notion's help documentation, so a regular member should not expect to export the whole workspace. Members can export pages and databases they can access, but that is a partial export. Confirm current owner permissions in Notion's help center before you assign the task. If owners are not available, plan for a Notion admin to grant access or perform the export under a documented procedure.

What does the team need to provide for a Notion export project?

The team needs three things: owner-level access to the workspace, a named person who verifies the output, and time for someone to review databases. Owner access is required for the full export. The verifier should compare page counts, attachments and key pages against the source, and should sign off on what is missing. Database review takes the most attention, because CSV files flatten relations, rollups and linked views. Ask your own team to estimate that review time from the number of databases.

Can we export Notion ourselves without outside help?

Yes, a small workspace with few databases and no restricted pages can often be exported by an owner using Notion's built-in options. Notion exports pages and databases as PDF, HTML, or Markdown and CSV. The effort rises when you need to validate completeness, rebuild database structure in the target tool, or handle content that the export does not carry. Decide early whether an internal owner has the time for that verification work. Outside help is usually scoped as a fixed project with written deliverables.

What makes a Notion export take more effort?

The main drivers are the number of databases, relations and rollups between them, private pages the exporter cannot open, and Enterprise security settings that disable exports. Form view databases are not exported, so each form that holds data needs a separate plan. Pages that only specific people can access are skipped if the exporter lacks access, which means a sweep with the right accounts is required. On Enterprise, check whether an admin has turned off exporting, because that setting must change before any export can run. Notion's Enterprise plan also offers an Admin API for scheduled exports, which some teams use for repeatable pulls.

What should we ask a consultant to include in a written scope?

Ask for a written scope that lists the workspaces and teamspaces in scope, the export formats, and the target platform. Request a completeness check that names the pages, databases, form views and private pages that are excluded and how each gap is recorded. Ask who performs the owner-level export, who verifies it, and how the link expiry of 7 days is handled. Require a plan for database rebuilding, attachments, permissions and a final delta export. Confirm deliverables, acceptance criteria and timelines in writing before work begins, since DeployOpen works from fixed-scope agreements and does not publish a price list.

Does an export preserve permissions and access rules?

Standard Markdown, HTML, PDF and CSV exports do not carry the full permission model of a Notion workspace into another system. Treat the export as content only, and rebuild spaces, roles and access rules in the target wiki. List who needs access to each area before cutover so that permissions are set deliberately. Confirm the exact behavior of your export in Notion's help center, since the export options and their limits can change.

Choosing where the exported files go next

Docmost is the most direct destination for a Notion wiki. Its import dialog accepts Markdown, HTML, Word, Notion and Confluence exports, and pages export back out as Markdown or HTML, so the files you produce from Notion can usually be brought in without a separate conversion project. Docmost is licensed AGPL-3.0, and the most recent release supplied for this page is v0.96.0, published on September 8, 2026.

Import formats: Markdown and HTML from Notion's export load through the standard import dialog.
Paid importers: Docmost's documentation lists the Confluence, DOCX and PDF importers as paid-edition features, so confirm which importers your edition includes before you plan the work.
Databases: Notion databases arrive as flat files, so tables and relations need their own rebuild step.
Licensing: The AGPL-3.0 terms apply to modified network-facing deployments, which your legal team should review.
Attachments: Confirm in a test import how attachments and internal links resolve.

Run a test import of a representative workspace subset before committing to a full migration, and check the edition features against the current Docmost documentation.

What to plan before the Notion contract ends

Leaving Notion is mostly a scheduling problem. The export itself is simple, but its timing, the admin settings that control it, and the plan you are on all decide what you can actually get out. Work through these items before the contract end date so the export, the archive and the cutover do not depend on last-minute access.

Export window before access changes

A full workspace export can take up to 30 hours to prepare, and the download link expires after 7 days. Start the export well before any plan change or license end, and do not rely on a single download. Confirm with your Notion account team what access remains after the contract ends, and record the date you plan to request the export so the timing is documented.

Enterprise admin settings that block export

On Enterprise workspaces, admins can disable exporting in security settings, which stops members and sometimes owners from exporting content. Check this setting early, because a workspace owner may not be able to change it without a Notion admin. If exporting is disabled, ask for the change in writing and confirm who will run the export.

Retention of exported archives

The export archive will contain your content but not your permissions, comments or workspace-level controls in a form you can reuse directly. Decide where the archive is stored, who can read it, and how long it is kept, and treat it as confidential data. Store a verified copy in your own controlled storage with checksums, since the Notion download link is temporary and the archive is no longer protected by the Notion workspace.

Plan downgrades that remove export features

Some export options depend on your plan. Notion's Include subpages option for PDF export is limited to Business and Enterprise plans, so a downgrade before you export can remove that option mid-project. Before any plan change, list the export options you need, run them, and confirm the output is complete. Do not assume an option will remain available after the plan changes.

Private pages the exporter cannot reach

A workspace export skips private pages the exporting account cannot access, and it also skips form view databases. Before exporting, have page owners confirm which private pages they hold, and ask a workspace owner to review shared content. Keep a list of what was excluded so gaps are found during verification, not after the Notion workspace is closed.

Cutover date with both systems readable

Set a cutover date only after the new wiki has received the imported content and reviewers have compared it against the export. Keep Notion readable until verification is signed off, so reviewers can check pages side by side. Agree the date with the people who own each space, and freeze edits in Notion for the final export so the archive matches what the new system holds.

What to confirm with Notion and your own team

Start by confirming what your Notion plan allows, because export capability is not identical across tiers. Notion's help center documents that the Include subpages option for PDF export is limited to Business and Enterprise plans, so a workspace on a lower tier may need to export page by page or accept a different result. Check the current plan documentation at Notion's export help page rather than relying on what a colleague remembers, since plan limits change. Also confirm whether your workspace is on Enterprise, because only Enterprise offers an Admin API for scheduled exports. Next, ask whether security settings block exporting. Enterprise workspace admins can disable exports in security settings, and if that setting is on, no member can produce the archive you need until an admin changes it. Decide with your security and compliance owners whether an export is permitted for this migration, under what approval, and where the resulting files may be stored. Record that decision before anyone starts, because an export is a copy of company data outside the tool that governs it.

Identify which owners hold the access required. Only workspace owners can export all workspace content, so list the people who hold that role, confirm they are available for the full export window, and confirm who will receive the download link. Note that the link expires after 7 days, and that the export can take up to 30 hours to complete. Plan for a single named person to start it and a backup owner to monitor it. Also confirm that the export will not include form view databases or private pages the exporter cannot access, so someone must inventory those pages and databases and arrange access or manual capture. Finally, test with your own data, not Notion's description of it. Run an export of one team space or a representative sample, inspect the Markdown, HTML and CSV output, and check attachments, nested databases and internal links. Use the results to size the migration, and ask your target vendor or implementation partner to confirm how their importer handles the same files. Treat every export size estimate as provisional until a trial run on your workspace confirms it.

How DeployOpen scopes and delivers a Notion data exit

DeployOpen treats a Notion data exit as a written, fixed-scope engagement. We agree what is exported, what is rebuilt and what is handed over before any export runs, so your team knows exactly what the workspace will and will not carry across into a self-hosted platform.

How we scope

We inventory workspaces, teamspaces, databases and page counts to define the export boundary.
We identify form view databases and private pages the exporter cannot access, and agree how each is handled.
We confirm your Notion plan and whether Enterprise security settings restrict exporting before work starts.

How we build

We run the workspace export and check completeness against the inventory, including the up to 30 hour processing window.
We convert Markdown, HTML and CSV output into the import format of the target platform in your own infrastructure.
We test imported pages, attachments and database exports on a staging instance before any cutover.

How we hand over

We deliver a written reconciliation report listing exported, rebuilt and skipped content with reasons.
We document the export procedure, the import steps and the known gaps so your team can repeat or audit it.
We keep the export archive in storage you control, so access to the source data does not depend on Notion.

How we support

Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
Ongoing support, upgrades and continuous testing of the new platform are available as a retainer.
Quotes follow from the written scope, so ask for line items covering inventory, conversion, testing and handover.

How to export your data from Notion