There is nothing
to migrate.
- 01Nothing leaves the repositoryYou do not export, convert or upload anything. The markdown stays exactly where it is, in the branch it is on, owned by git and reviewed the way your team already reviews it.
- 02You connect, which takes about three minutesRead-only access to the repositories you choose, a branch picked from the real list, and the docs root found for you. There is no configuration step because there is no configuration.
- 03You keep your old tool running as long as you likeConnecting changes nothing about your existing site. Run both, decide with your team, and turn one off — or neither. There is no cutover and no window in which documentation is unavailable.
What carries over, and what does not
The second list is the one worth reading. Everything on it is a deliberate non-goal rather than a gap we intend to close.
Comes with you
- Every markdown file
- Read as written, including the ones your old tool's config never listed.
- Your folder structure
- It becomes the navigation as it stands — that is the whole product.
- Headings, tables, code blocks, Mermaid
- CommonMark and GFM, rendered properly.
- Front matter titles
- Used when present; the first heading and then the filename when not.
- Relative links between documents
- Resolved, and reported as a health finding when one points at nothing.
- Your git history
- Untouched. We never write to your repository.
Does not
- A hand-ordered navigation
- Order is inferred: README first, numeric prefixes next, then alphabetical by title. If chapter three must follow chapter two for a reason no filename captures, that intent does not survive.
- Custom MDX components
- `.mdx` files are indexed and read as text; no JSX is evaluated. A file that is mostly components will read as mostly nothing.
- Your theme and custom CSS
- The reader is one surface in two themes. A public site takes your logo, favicon and colours, not your own CSS.
- Your public URLs and their search ranking
- A public site lives at your team's docsflowy.site address, so the addresses your current site has earned in search do not move with it. If those URLs matter, keep that site where it is.
- Redirect rules and vanity paths
- Paths come from the repository. There is no redirect table.
Where teams arrive from
From MkDocs, Docusaurus or GitBook
Your markdown is already in the repository and already in folders. Connect it and compare the tree we build against the nav you have been maintaining by hand. If ours is wrong, that is a discovery bug worth telling us about.
From Mintlify
Its pages are built around its own components and navigation file, so they do not come over as they are. If your customer-facing site works, keep it, and point us at the internal repositories that were never going in it. If you want public pages written with the work, the Handbook publishes them as named releases.
From a wiki
This is the one case with real work in it: the content has to become markdown in a repository first. Once it is there, connecting is the same three minutes as anything else.
From nothing at all
The common case. The documents exist, in six repositories, and nobody has ever put a docs tool in front of them because every one asked for a config file first.
Disconnecting is one click, and it leaves nothing behind
The same property that makes arriving cheap makes leaving cheap, and a product that is easy to leave is the only kind worth trusting with a source of truth.
Disconnect a repository and we stop reading it. Revoke the GitHub App from GitHub’s own settings and we cannot read it whether we stop or not — the switch is on your side, not ours. Your markdown is where it always was, in the branch it always was, with a history we never wrote to.
What you would lose is the layer we added on top: review and implementation state, the notes, read receipts, health findings and any artifacts an agent filed. Those are ours because they never existed in your repository — and if that matters to you, it is worth asking about before you start rather than after.
Point it at one repository and keep everything else running.
There is no cutover to schedule, so there is nothing to undo if you change your mind.
Start free