Docs-as-code migrations
This is for SaaS teams whose product docs live somewhere they no longer want them: a Zendesk help center, a Confluence space, a folder of Word files or a shared drive full of Google Docs. We move that content into Markdown in your own Git repository, published with Docusaurus, MkDocs, Zensical or GitBook, and we use the move to fix what went wrong along the way: duplicate pages, a navigation nobody can follow, and old links that still have to work.
From $4,500 (up to 150 pages), $9,500 (up to 500 pages), custom above
Reply within 1 business day
30-day fix window
If you are still weighing whether a move is worth it, the handbook page on deciding whether to migrate lays out the tradeoffs, including the cases where staying put is the right call.
The deliverable is a working documentation site in your repository, not a folder of converted files to finish yourself. Concretely:
On the target platform: Docusaurus is our default for teams that want React components, versioned docs and a site that matches the product. MkDocs suits teams that want plain Markdown and very little front-end work; since Material for MkDocs went into maintenance mode, we also look at Zensical, the new generator from the same team. GitBook suits teams that want a hosted editor for non-engineers with Git sync underneath. The platform comparison goes deeper, and we recommend one in writing during scoping.
You get a short written update at the end of each stage, and any decision that changes what readers see comes to you first. Whoever scopes your project stays on it through delivery and the fix window, so the context never gets lost in a handoff and you always know who to ask when something looks wrong.
The tier is set by the page count we agree during scoping, and pages we decide to retire rather than migrate do not count toward it. Above 500 pages, we quote the project after reading a representative sample.
What moves the price within a tier is how much work each page needs, not the page itself. A single, well-structured export converts quickly. Content spread across several tools, heavy rich-text formatting, custom macros, multiple product versions, or a large share of pages that need rewriting rather than converting all take longer, and the quote says so line by line. Prices are in US dollars; the euro figures are approximate conversions for reference.
Coming from a specific tool? The Confluence to Docusaurus and Zendesk to Docusaurus pages cover the details that are particular to each one.
Send a link to your docs, an export, or a few lines on what needs to change. We reply within 1 business day with questions or a quote.