A company wiki is often the richest set of documents the company has. Hundreds or thousands of pages, linked to each other, edited over years by the people who do the work. micro1 lists internal knowledge bases among what it takes; Scale AI lists Jira and Confluence knowledge records; SimpleClosure takes Google Drive and Notion workspaces from companies that are winding down.
Getting that content out cleanly is mostly a question of timing.
Why not export everything now?
Because an export is a full copy, with every name, comment and attachment in it, sitting outside the access controls that protect the original. Until a buyer has said which spaces it wants and in what format, that copy has no use and real risk.
Some buyers skip the export entirely in the early stages. Scale AI, for instance, does its anonymizing on the company’s own systems and agrees each package with the company before anything is pulled out. Ask before assuming a download comes next.
What should you count first?
One row per space, teamspace or shared drive:
| Field | Why a buyer asks |
|---|---|
| Tool and space name | Scope and access |
| Page or file count | Size of the set |
| Oldest and newest edit | Years of history |
| Owning team | Domain (operations, engineering, support) |
| Names in body text: often, rarely, never | Redaction effort |
| Client or third-party content: yes or no | Rights |
Most tools show page counts in space or workspace settings. Twenty minutes with this table answers more of a buyer’s first questions than any export would.
How does each tool export?
Menu names change, so treat this as a map, and check each tool’s own help pages before you start.
Notion
A workspace owner can export the whole workspace from the workspace settings. Markdown and CSV keeps the page tree as folders and turns databases into CSV files; HTML keeps the layout closer to what users see. Single pages and their sub-pages can be exported from the page menu.
Watch the databases. Person and email properties come out as plain columns in the CSV, and they are easy to miss because nobody reads a CSV export the way they read a page.
Confluence
A space admin exports a space from the space settings. HTML keeps pages and links; XML keeps more structure and is meant for importing into another Confluence site; PDF is easy to read and loses most of the links that make a wiki useful.
Watch the personal spaces and inline comments. Personal spaces often hold drafts and notes about colleagues, and they should stay out of scope.
Google Drive
A Google Workspace admin can export all users’ data with the Data Export tool in the admin console. A single user can use Google Takeout for their own files. Docs convert to Word, HTML or other formats; Sheets to Excel or CSV.
Watch comments and suggestions in Docs, which carry names, and the sharing settings that told you who could see a file. A shared drive is usually a better unit of scope than “everything.”
SharePoint
There is no single export button. Libraries are copied out by sync or download, and an admin can export through Microsoft Purview. Keep a list export of the library’s metadata columns alongside the files, then strip the “modified by” column from it.
Which format should you choose?
The one the buyer asks for. If it has no preference, pick the format that keeps the most structure without the most names:
| Keep | Drop |
|---|---|
| Page titles and hierarchy | Personal and private spaces |
| Links between pages | Comments and suggestions |
| Created and edited dates | Author and editor names |
| Labels and templates | Unchecked attachments |
Scale AI’s list of “documents and files with metadata” is the reason to keep dates and structure. A wiki flattened into a folder of PDFs is much harder to use.
What order should the work follow?
- Inventory the spaces and agree scope with the buyer.
- Remove out-of-scope spaces and pages in the tool itself, or mark them for exclusion.
- Resolve or delete comments, and decide on version history.
- Export the agreed spaces only.
- Run the names and pattern passes from the redaction guide on the export.
- Keep the export on one controlled machine or bucket, and delete it when the license says to.
If you are still working out whether to sell company documents from your wiki, the inventory table above is the whole first step, and it costs nothing to fill in.
An export you never had to make is the safest copy of all.