Skip to main content

Migrate from GitBook

GitBook spaces map to Docsio sites one-to-one. The two products have similar mental models — pages with a sidebar, an editor, branching for review — so most of what you have moves intact.

Choose your import path

Live URL — if your GitBook space is publicly accessible, paste the URL into Docsio's URL onboarding. Docsio scrapes every page and rewrites them as markdown.

Markdown export — GitBook's Git Sync writes markdown to a GitHub repo. Connect that repo to Docsio's GitHub Sync and pick GitHub → Docsio for the first sync. You'll get a Docsio site backed by the same files, with bidirectional sync from then on.

Direct copy-paste — for small spaces (under 20 pages), it's faster to paste each page into the editor and ask the agent to clean it up. You stay in control of the structure as it lands.

What translates cleanly

  • Headings, lists, paragraphs, blockquotes, code blocks, tables.
  • Embedded code with syntax highlighting.
  • GitBook's {% hint style="info" %} blocks become Docsio's :::tip admonitions automatically.
  • Image links — Docsio re-hosts the images so your GitBook URLs aren't load-bearing.

What needs a hand

  • Hint styles — GitBook has info, warning, success, danger. Docsio uses note, tip, info, warning, danger. The agent maps them on import; you may want to adjust tone afterwards.
  • Embedded components — GitBook's drawing/diagram components don't have direct equivalents. Replace with embedded Figma, Excalidraw, or static images.
  • Custom domains and integrations — Docsio re-issues SSL certificates from scratch, so plan a quick DNS swap. See Custom domains.

After the import

GitBook spaces often have legacy structure — old pages, half-finished sections, deep nesting. The Docsio AI agent doesn't carry that over automatically. Once your content is in:

  1. Ask the agent: "Audit our sidebar and suggest a flatter structure if useful."
  2. Tag a version (Pro) so you can roll back if you don't like the result.
  3. Apply the agent's suggestions selectively.

Bidirectional sync from day one

If you connected via GitHub Sync during import, your team can keep editing in GitHub or in Docsio's editor. Edits in Docsio commit to your repo on Publish; pushes from anywhere rebuild the live site. See GitHub Sync overview.

GitBook locks live edits when sync is on. Docsio doesn't — you can edit alongside a teammate's git push and Docsio snapshots your draft so nothing is lost. Different trade-off, both work in practice.