> ## Content Index
> Fetch the complete content index at: https://notionsolutions.net/llms.txt
> Use this file to discover other available public pages before exploring further.

# Back Up a Notion Client Project Without Mistaking an Export for a Restore
- URL: https://notionsolutions.net/notion-client-project-backup/
- Published: 2026-10-24T09:00:00.000Z
- Updated: 2026-10-24T08:59:59.000Z
- Description: Keep a portable project archive and a clear recovery route. Check export scope, database relationships, and missing settings before you need to rebuild.
- Author: Kevin Turner
- Tags: guide, client-work

For a Notion client project, keep a dated export outside Notion and a recovery note describing the databases the project depends on. The export gives you a portable copy of content; restoring the working project is a separate task. Notion explicitly says you [cannot instantly recreate a workspace by reuploading its export](https://www.notion.com/help/back-up-your-data?ref=notionsolutions.net).

I recommend checking the archive while the original project is still available. A ZIP file can contain the project brief and task rows without giving you enough information to rebuild their relations or the views your team uses.

## Recover a recent edit or deletion first

If content is already missing, start with Notion's recovery controls before importing an old export. Use the route that matches the loss:

| Problem                              | First route                                                               | Check before proceeding                                                                       |
| ------------------------------------ | ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| A page was deleted                   | Open **Trash**, find the page, and restore it.                            | By default, pages remain in Trash for 30 days. Enterprise owners can customize retention.     |
| A page was edited incorrectly        | Open the page's **••• → Version history** and inspect an earlier version. | Copy back only the needed blocks, or preview the earlier version before choosing **Restore**. |
| A database or its properties changed | Inspect the database's version history.                                   | Restoring database pages and properties does not restore the text inside each database page.  |

These routes come from Notion's [deletion and version-history instructions](https://www.notion.com/help/duplicate-delete-and-restore-content?ref=notionsolutions.net). You need at least **Can edit** access to use version history, and how far back it reaches depends on your plan: 7 days on Free, 30 days on Plus, 90 days on Business, and unlimited on Enterprise. A database restore may affect existing views and other collaborators, so check its preview before you restore.

For a deleted database property, check **database settings → Edit Properties → Deleted Properties** first. Notion provides a restore arrow there, but permanently deleting a property from that list cannot be undone through that control. If built-in recovery can't bring the missing material back, [contact Notion support promptly](https://www.notion.com/help/back-up-your-data?ref=notionsolutions.net#accidental-deletions). Notion says its backups let support recover page snapshots from the past 30 days. That recovery happens through support, and it's separate from the export you keep yourself.

## Define the client project's export scope

A project's page hierarchy and its database relationships can be different. For example, a project brief might contain a linked Tasks view while the Tasks data source lives elsewhere in the workspace. A Clients database may hold the related client record outside the project's subpages. The [Clients, Projects, and Tasks model](https://notionsolutions.net/notion-client-project-tracker-template/) makes those dependencies easier to identify.

Before exporting, record the project page's URL and the locations of its source databases. List the records the project needs, including completed work you still need to retain. Then note any essential files held outside Notion; do not assume an external link supplies a downloaded copy of its destination.

### Make the boundary concrete

For an educational Website launch project, suppose the project page contains Brief and Decisions subpages, but shows tasks from a shared Tasks source under Operations. Its Harbor Studio client record lives in a separate Clients source. Write three export items: the project page with its subpages, the required task records from Tasks, and the client record from Clients. A linked task view inside the page does not turn the source database into a child page.

Use [database settings → Manage data sources to identify Sources and Linked](https://www.notion.com/help/data-sources-and-linked-databases?ref=notionsolutions.net) before choosing the archive boundary. Record the original source location; do not move it merely to make the page tree look complete. In this example, include both the active Clarify page count task and completed Collect brand assets task in the scope note. Completed status is not a reason to omit a record you need for recovery.

[![Website launch subpages sit inside the project boundary while Tasks and Clients sources require separate export checks](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/backup-source-boundary.webp)](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/backup-source-boundary.webp?ref=notionsolutions.net)

A page’s nested content and its database dependencies can have different boundaries.

Choose an exporter who already has access to the required material. A workspace export omits pages that account cannot access, such as another user's private pages, and teamspace settings can exclude content too. The [workspace export's access limits](https://www.notion.com/help/export-your-content?ref=notionsolutions.net#export-your-entire-workspace) still apply even when you select the entire workspace.

Keep the client scope deliberate. Exporting a shared Clients or Tasks database may put other clients' information in the archive. Store an internal recovery archive under suitable access controls, and prepare a separate, checked package if you need to send files to a client.

## Choose and run the export

Use desktop or web for the workflow below. Choose the format by the material you need to preserve:

| Format         | Useful for                                                                  | Important limit                                                                                             |
| -------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| HTML           | Reading pages in a browser, with subpage files and associated assets.       | HTML export can include page and block comments, but HTML import does not restore comments or edit history. |
| Markdown & CSV | Plain-text page content and database rows you can inspect in a spreadsheet. | CSV relation values are text URLs; they are not a restored relationship between databases.                  |
| PDF            | A readable copy of an individual page or database for reference.            | A PDF is a document copy, not a database recovery format.                                                   |

For a relational project, I'd keep both formats when each serves a real recovery need: HTML for readable reference and Markdown & CSV for inspecting the rows. If you'll only need to read the pages later, HTML is enough. Notion lists the content and options for each format in its [export instructions](https://www.notion.com/help/export-your-content?ref=notionsolutions.net), and its [HTML import limits](https://www.notion.com/help/import-data-into-notion?ref=notionsolutions.net#html) explain the comment and history gap.

1. Open the top-level project page and select **••• → Export**.
2. Choose **HTML** or **Markdown & CSV**. Turn on **Include subpages** for the nested pages you need.
3. Export any required source databases that sit outside that subtree. When exporting a database, check the selected view: Notion offers the current or default view, and [does not export every database view at once](https://www.notion.com/help/export-your-content?ref=notionsolutions.net).
4. Download the resulting files and label the archive with its project and export date. Record the chosen format, view, and exporter alongside it.

[![Markdown and CSV export with Include subpages enabled and separate checks for outside sources and database views](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/backup-export-controls.webp)](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/backup-export-controls.webp?ref=notionsolutions.net)

Include subpages follows the page tree. Check required sources and the exported database view separately.

If the project includes a form, [export its questions and responses from a Table view](https://www.notion.com/help/export-your-content?ref=notionsolutions.net); Notion does not currently export Form views. Check the resulting rows against the records you intended to keep.

For a whole-workspace copy, go to **Settings → Workspace → General → Export all workspace content** on desktop or web. The download link expires after seven days; Notion sends it by email, or to the in-app inbox if email notifications are off. [Large workspace exports can take up to 30 hours](https://www.notion.com/help/export-your-content?ref=notionsolutions.net#export-your-entire-workspace), so starting an export doesn't mean you have the copy yet.

If **Export** is missing, Enterprise workspace or teamspace policies may have disabled it. Notion's [export-permission guidance](https://www.notion.com/help/export-your-content?ref=notionsolutions.net) says guests need **Full access** to export a page or database. Ask the workspace owner to arrange the export; don't widen a client's access just to get a file. If a large export fails, Notion recommends [exporting important top-level pages in smaller batches](https://www.notion.com/help/back-up-your-data?ref=notionsolutions.net) with subpages included.

## Inspect the archive and record the rebuild

Open the downloaded ZIP before changing or discarding the original project. For HTML, open the project page and follow its local subpage links. For Markdown & CSV, inspect the page files and the database rows. Open the essential attachments too; a filename alone does not establish that its contents are readable.

Compare the archive with your scope note. Check that the expected project and client records are present, and inspect a representative completed task as well as an active one. Record any missing pages or inaccessible files. If the package is incomplete, correct the scope or ask an authorized owner to export the missing material.

Check how the export handles relations. Notion says [CSV exports turn relation properties into plain-text URLs, and reimporting the exported CSV does not re-establish those relations](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net). A new CSV import can't create new relations, rollups, or formulas. Importing or merging CSV also adds rows instead of updating existing ones, so a recovery attempt into a live database can create duplicates. Those are [documented CSV import limits](https://www.notion.com/help/import-data-into-notion?ref=notionsolutions.net#csv); a completed import isn't evidence that your original database was restored.

[![A task’s Project relation becomes a plain-text URL in CSV and needs manual relation rebuilding after import](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/backup-relation-gap.webp)](https://storage.ghost.io/c/5c/30/5c30c46b-86a3-4d20-984f-4f6ae8ad1ed2/content/images/2026/10/backup-relation-gap.webp?ref=notionsolutions.net)

Keeping the task row is different from restoring its connection to the project.

Keep a short recovery note beside the archive:

- Record the original page and data-source URLs, the export date, the exporter, and any known omissions.
- Describe each relation's destination and direction. For each important rollup, record its relation, source property, and calculation.
- Preserve formula definitions and the settings needed to recreate important views. Record the defaults or automation rules the workflow depends on.
- Identify the person responsible for recovery and the intended sharing rules. Include the checks needed before a rebuilt project can be shared again.

The note describes a manual rebuild; it does not make the export a complete relational snapshot. If rebuilding becomes necessary, keep the imported copy separate from the live project until you have reconciled its records and rebuilt the required relationships. Restore page contents individually when database version history alone cannot recover them. Recheck client access before using the recovered area as a portal; the [client portal permissions checklist](https://notionsolutions.net/notion-client-portal-permissions/) covers that separate check.

### If you must rebuild from the files

Use a separate recovery area and keep a list of imported files. For CSV, [open Settings → Import → CSV, choose a new database and import location, then map the columns](https://www.notion.com/help/import-data-into-notion?ref=notionsolutions.net#csv). Check one imported record’s title, date, status, and page content against the archive before continuing. If a task row is present but its notes are missing, use the matching exported page file to recover the needed body content separately. If an import fails, inspect for partially imported pages before retrying so a second attempt does not quietly add another copy.

1. Reconcile the required client, project, and task records against your scope note. Compare saved source URLs and the distinguishing details in each record; a matching title alone may identify the wrong project.
2. Rebuild the necessary relations using your recovery note. [Create a Relation property, choose its destination database, and select Add relation](https://www.notion.com/help/relations-and-rollups?ref=notionsolutions.net); then choose the intended recovered record in each relation cell. In the example, the recovered Website launch project should refer to the recovered Harbor Studio client, and both required tasks should refer to the recovered Website launch project.
3. Recreate the important rollups, formulas, and views from the recorded definitions. Review one active task and one completed task through the intended project view, rather than treating an imported row count as proof that the workflow is ready.
4. Check the brief, decisions, essential attachments, and sharing scope. Keep any unresolved omission in the recovery note and leave client access closed until it has a clear disposition.

If you only need a readable reference, you can stop once you've verified the exported pages and files. Rebuilding relations is necessary when you want the working project model back, but you don't need it just to read an old brief.

## Choose a copy frequency and recovery standard

Set the export interval by how much work you could afford to lose between copies. I'd export a project that gets client revisions every day more often than a quiet reference project, since a longer gap between copies puts more of that work at risk. Keep the downloaded archive somewhere you can reach independently of the Notion workspace, with access appropriate for the client material.

If manual exports can't meet that requirement, judge a backup service by what it can restore. Check whether it rebuilds relations between the actual project databases, includes required attachments, and supports the destination workspace you'd need. Ask for its exclusions and required access permissions before you connect client data. For example, [Notion Backups' restore FAQ says a complete restore is not possible](https://notionbackups.com/?ref=notionsolutions.net) because of API limitations, despite its broader backup wording. Scheduling copies, on its own, doesn't tell you how much a service can recover.

Before the next database redesign or client handoff, download a dated archive, inspect the required files and rows, and finish the recovery note while the original settings are still available.