Export
Take everything, on any plan, at any time.
Export
Section titled “Export”Exportability is a product promise, not a retention feature.
Two levels of portability
Section titled “Two levels of portability”Your pages are already yours. They are Markdown in a git repository you own. Clone it and you have your documentation, its history, and every author’s name on every commit. Nothing has to be exported for that to be true.
Everything else exports as an archive.
What the archive holds
Section titled “What the archive holds”| Item | Format |
|---|---|
| Pages | Markdown, with frontmatter |
| Assets | The files, in a folder |
| Hierarchy | A manifest, and nav.yaml |
| Redirects | redirects.yaml |
| Variables | variables.yaml |
| Snippets | The files |
| Search tuning | search.yaml |
| Glossary and style | glossary.yaml, style.yaml |
| Version information | The refs and their labels |
| API definitions | The OpenAPI documents as synced |
| Audit log | Where your plan includes one |
When you can export
Section titled “When you can export”Every plan. At any point, including after a cancellation and during a workspace deletion grace period.
An export is offered explicitly before a workspace is deleted, and before a cancellation takes effect.
Leaving
Section titled “Leaving”If you leave Staleless:
- Export the archive.
- Keep your git repository. It is the documentation.
- Detach your custom domain and point it wherever you go next.
Your published site is a build artifact rather than a database. Rebuilding the same Markdown somewhere else is a build, not a migration.
Note
This is why the repository is the source of truth. A documentation tool that owns your content owns your exit, and the cost of that is paid on the worst possible day.
What does not come with you
Section titled “What does not come with you”- reader analytics beyond your retention window, because it is already deleted;
- the daily-salted reader hashes, which cannot be joined across days by design;
- Staleless-side records of a deleted workspace, 30 days after deletion.
Imports, in the other direction
Section titled “Imports, in the other direction”Bringing documentation in is supported from a Markdown folder, GitBook, Notion, Docusaurus, Nextra, OpenAPI and HTML.
Every import produces a report:
Imported: 124 pages, 307 images, 52 redirectsWarnings: 3 unsupported embeds, 2 broken source links, 1 duplicate slugUnsupported constructs are reported rather than silently discarded. A large import runs as a restartable background job with progress.