Move your docs from GitBook
Sync your GitBook space to GitHub, then import it into OpenDocs. Pages keep their order and hierarchy, and you do not retype anything.
Five steps, in this order
- Sync your GitBook space to GitHub. In GitBook, turn on Git Sync and sync the space to a GitHub repository. GitBook writes your pages as Markdown files, with a
SUMMARY.mdfile that holds the table of contents. Git Sync is a GitBook feature, so check that your GitBook plan includes it. - Create a space in OpenDocs. Start free: every account opens with 14 days of Pro, no credit card. Add an empty space for the imported docs.
- Import the repository. Open the space and choose Import from GitBook. Paste the repository address (
owner/repoworks) and, for a private repository, a GitHub token withreposcope. The token is used once and is not stored. - Review the pages. Check the page order, the images, and any page that uses GitBook-specific blocks such as tabs or hints. The importer converts standard Markdown, so special blocks are the pages most worth a look.
- Publish. Share the OpenDocs address, or put the space on your own domain (Pro). Keep your GitBook site live until you are happy.
What carries over, and what does not
| Item | In the import |
|---|---|
| Page content (Markdown) | Converted into OpenDocs pages |
| Page order and parent/child hierarchy | Kept, from the SUMMARY.md table of contents |
| Front matter at the top of a file | Removed |
| Images | Linked from your GitHub repository, so keep the repo available |
| Page status | Imported pages are published immediately |
| Files that cannot be fetched | Reported in a list, and the rest still import |
| Users, comments, analytics and integrations | Not part of the repository, so set them up in OpenDocs |
Try it without risking your live docs
The import only reads your repository. Nothing changes in GitBook, so your current docs stay online while you check the result. Because imported pages publish right away, import into a new space first and share the link only when you are ready.
What you get after the move
- Docs that Claude and other AI tools can read. Every published space has a built-in MCP server, an
llms.txtfile and a clean Markdown version of every page. - Translations in 38 languages with Claude, using your own Anthropic API key, plus your Anthropic usage.
- Two-way GitHub sync, so your repository can stay your source of truth.
- A Free plan that stays free. After the 14-day Pro trial you continue on the Free plan with 1 space, published docs included.
Comparing first? Read OpenDocs vs GitBook for the side-by-side, including where GitBook is the better fit.
Questions people ask
Does my repository have to be public?
No. A public repository imports with no token. For a private one, give a GitHub token with repo scope. It is used once for the import and is not stored.
My repository has no SUMMARY.md. Can I still import?
The importer builds the page tree from SUMMARY.md, which GitBook creates when it syncs a space. Without that file it stops and tells you so, so nothing is half-imported.
Will my images still work?
Yes, as long as the repository stays available. Images are linked from GitHub rather than copied.
Can I import again later?
Yes. Import into a new space whenever you want a fresh copy.