How to pick a docs platform you can leave

Nobody evaluates the exit while they are excited about the features, which is exactly why platforms are careless about it. By the time it matters you have four hundred pages, every link support ever sent points at those URLs, and the cost of leaving is a quarter of someone’s time.

That cost is not neutral. It is the number that sits silently in every renewal, every price rise and every feature you wanted and did not get. A platform that is easy to leave has to keep earning you; a platform that is hard to leave does not.

The test is not whether an export button exists. Almost all of them have one. The test is what comes out of it, and whether that thing is a website somewhere else or a pile of files you would have to rebuild from.

1. What format does the export produce?

There are three answers and they are not close. Source — your Markdown, plus a config that builds the same site with an open source generator — means you can leave in an afternoon. Built HTML means you have an archive you can host but not edit further. A proprietary format, or nothing means the content is hostage.

Ask specifically whether the export includes a working build config. Markdown alone is portable content; Markdown plus a config is a portable *site*.

2. Is the export on the plan you are on?

An export button behind the top tier is not an exit, it is a toll. This matters most on free plans, which is precisely where people put the content they cannot afford to lose.

3. Do you own the URLs?

If your docs live on a subdomain of the vendor, every link ever shared points at them. Leaving breaks all of it: search rankings, support macros, blog posts, README links, whatever a customer bookmarked in 2024. On your own domain you repoint a CNAME and the links keep working.

The follow-up question that matters more than people expect: what happens to the old address when you leave? Somewhere between "it 301s to your domain for a year" and "it dies immediately" is a lot of traffic.

4. What happens to your images and files?

The most commonly missed one. Prose exports cleanly and assets often do not: images stored on the vendor’s CDN, referenced by absolute URL, and a Markdown export full of links that stop resolving when the account closes. Export a page with three screenshots and check whether the images came with it and whether the links are relative.

5. Does the search index leave with you?

If search is a hosted service tied to your subscription, your exported docs have no search. Whether that matters depends on the size of the doc set, but discovering it after you have left is the wrong time.

6. Does history come with it, or only the current state?

Nearly always only the current state, which is usually fine — but if you are in a regulated environment where you have to show what a page said on a date, ask before you need it rather than after.

All of it is checkable on a free plan before you commit anything, and it is worth doing on every platform in your shortlist on the same afternoon.

• Create a site with three pages, one image, one internal link and one code block.
• Publish it.
• Export it — both source and built site, if both exist.
• Unzip the export somewhere else and open it. Does the internal link resolve? Does the image load from the folder, or from their CDN?
• If a build config came out, run the generator it names on the exported source. Does it produce the same site?
• Search the exported copy. Does search still work with no internet?

Whatever comes out of that is what you would be holding on your worst day. Ten minutes now against a quarter of an engineer later is not a close trade.

A summary rather than a verdict — check it yourself with the test above, because this is exactly the kind of thing that changes.

Self-hosting scores best on this axis by definition — you never joined anything. That is a real advantage and it is worth weighing against everything in do you actually need a static site generator.

It would be cheap to publish this checklist without answering it. So, in the same order:

• Format. Export source gives your Markdown with a generated config that builds with plain Zensical, no Docszero involved. Export site gives the built HTML.
• Plan. Both, on every plan, including Free. It is not an upsell and it never will be.
• URLs. A docszero.com subdomain on Free; your own domain from Pro, and when you point a domain at us the subdomain keeps working and redirects to it. If a paid plan lapses, readers are sent back to the docszero.com address and nothing is deleted.
• Assets. Images live in your pages and come out with the export, with links rewritten to be relative.
• Search. The index is built at publish time and is one of the exported files, so an exported copy still searches offline.
• History. Export is the current published state. Version history and earlier builds live in the app, not in the export.

The reason to publish this is not modesty. A product that is easy to leave has to be worth staying on every month, and that is a better thing to build than a moat.