Notion and Google Drive at shutdown: preserving internal docs with context

Why do internal docs lose meaning in a plain export?#

Internal docs lose meaning in a plain export because much of their value sits in context the export does not carry: who wrote a page, when it changed, which project it belonged to and what it linked to. A playbook page that cites a post-mortem is useful; the same page with a broken link and no date is a guess.

Notion and Google Drive both store that context as live features rather than file content. Database relations, page mentions, comments, version history and sharing settings work inside the tool and may flatten or vanish outside it. Anyone who later relies on the archive, whether a successor, an auditor or a data licensee, needs to know which page is current and who stood behind it.

Notion export settings that keep context#

Notion export settings that keep context start at the workspace level, run by a workspace owner, and get tested on one teamspace first. Notion offers formats such as HTML, Markdown with CSV for databases and PDF; which formats and options your workspace has depends on its plan, so check Notion's help center before planning around one.

Database relations need special care. In a CSV export, a relation column typically shows the related pages' titles or links rather than a live connection, so a reader can rejoin two databases only if titles are distinct. Rename generic duplicates such as Meeting notes or Untitled to include a date or project before exporting.

• 1Export the whole workspace rather than page by page, so internal links point to files inside the export.
• 2Export twice: HTML for reading as a browsable archive, and Markdown with CSV for structured database content.
• 3Choose the options that include subpages and attached files, and keep subpages in nested folders if the export offers it, so the page hierarchy survives.
• 4Before exporting, add properties to key databases that record who created each row and when it was created and last edited, so that context lands in the CSV.
• 5Check whether a database export follows the current view's filters; if it does, export from an unfiltered view so hidden rows are not left out.
• 6Ask remaining members to move work pages from private sections into a teamspace, since private pages may not appear in a workspace export.
• 7Record teamspace membership and page permissions in a separate document, because exports may not carry them.
• 8Capture comment threads and page history by hand where they explain a decision.

Google Drive: keep ownership, paths and metadata#

Google Drive context depends on who owns each file and where it sits, and both can be lost when accounts are removed carelessly. Ownership decides whose name, edit history and comments travel with a document, and folder paths are often the only record of which client, project or year a file belonged to.

The account-level order, from Vault holds through ownership transfer to cancellation, belongs in the Workspace shutdown plan. For context, the rule is simple: transfer, do not copy. A transferred file keeps its edit history and comments, while a copy made by someone else starts fresh with a new owner and creation date, which erases exactly the context you are trying to keep. Capture the inventory while departing users' accounts are still active or suspended.

• 1Generate a file inventory with name, owner, folder path, created and modified dates, and sharing, using an admin report, a short script or an inventory tool.
• 2Transfer ownership of departing users' files to a retained account before any account is deleted or downgraded.
• 3If you move folders into a shared drive, record their original paths and owners first, because the move hands ownership to the organization.
• 4Export Docs, Sheets and Slides to Office formats for editing, and to PDF where a fixed copy matters.
• 5List shortcuts and files shared in from outside accounts, since neither is your copy to keep.
• 6Keep folder paths intact in the export so project and client structure stays readable.

Context checklist: what to capture in each tool#

A context checklist turns the idea of meaning into specific fields someone can tick off. The table pairs each kind of context with where it lives in Notion and in Drive, and with a practical way to keep it.

Verify the archive before deleting anything#

Verifying the archive means proving that someone without access to the live tools can find, open and understand what was kept. Pick a sample of important pages and files and walk through them as a stranger would, starting from the top-level index.

Check that internal links resolve inside the export, that database CSVs show the author and date columns you added, that attachments open and that folder paths match the live structure. Compare page and file counts with what the tools report, store two copies in separate locations and write a short readme covering the export date, formats and known gaps.

Illustrative: an operations consulting firm archives its knowledge base#

Illustrative: a fictional operations consulting firm whose headcount peaked above 50 winds down after its founders retire. Its playbooks, proposal library and engagement reviews live in Notion. Client deliverables, workpapers and data files live in Google Drive, organized by client folder.

The operations lead adds author and date properties to the playbook and engagement review databases, exports Notion in both formats and records teamspace permissions in a separate document. In Drive, departing partners' files are transferred to a retained admin, and a file inventory is generated before any account is removed.

Client folders go into a separate, restricted archive and are treated as client-confidential under the engagement letters. The firm-owned playbooks, which still link to their engagement reviews with authors and dates intact, are the only material later reviewed for licensing, after client names and details are removed.

How SourceX treats internal documentation#

SourceX treats internal documentation as useful only when its provenance is clear. In the Preparation step of the SourceX five-step transaction, pages are reviewed with their author, date and hierarchy, and client-owned material is excluded as a whole rather than redacted page by page. The SourceX Evidence Packet records where each document set came from and what was removed. Nothing is shared during the initial fit check, which works from system names and date ranges.