Import from GitBook
Free on every plan
No credits
No Git repo needed
Undo until you publish
IMPORT CONTENTTrusted by product teams worldwide
Getting your docs
out of GitBook.
GitBook has no Markdown download button. Its official route is Git Sync, which writes each space into a GitHub or GitLab repo. Blocks like hints and tabs come out in GitBook-only syntax, and every URL changes when you move. Clevera reads GitBook directly instead, with no repo and no code.
No Git repo needed
Clevera reads GitBook directly, so you can skip Git Sync.
Works with your public site
Paste your docs address and Clevera reads every published page.
Bring a private space with a token
Private spaces come over too, with a GitBook token.
Have an export? Upload it.
Already on Git Sync? Upload the repo as a zip.
What comes over.
What stays behind: files other than images, authors, dates and comments. Hidden GitBook pages come over like any other page, so untick them in the preview before you publish.
How it works.
1
Connect GitBook.
Paste your public docs address or a GitBook token. No developer needed.
2
Check the preview.
See every page before anything moves, and untick what you don’t want.
3
Import.
Pages, images and links come over. It’s free and uses no credits.
4
Publish on your domain.
Go live when you’re ready. Old links redirect once your domain points to Clevera.
What you get
after the move.
Your GitBook pages land in a full help center. Four things you get on day one:
Answers with sources
Ask AI replies to readers from your published pages and lists the pages it used. It uses no credits: 300 answers a month on Free, 1,000 on Starter, 5,000+ on Pro.
See what readers miss
Insights show searches with no result and what readers asked, with Write article next to each gap.
Your own domain
Free sites live at your-site.clevera.help. Use help.yourcompany.com from Starter.
A video in every article
Record your screen and Clevera writes the article and makes the how-to video that sits in it. Videos and articles use credits.
When to stay on GitBook.
If your docs live in Git and your developers review changes as pull requests, GitBook’s two-way Git Sync and PR previews are built for that. The same goes for API reference docs, or docs that change per reader, which GitBook offers on Ultimate as adaptive content. Clevera is built for help centers that support and product teams write in an editor and keep current. Staying? On Pro, Clevera can publish its articles to GitBook.
GitBook vs Clevera for a help center.
Questions.
Does the GitBook import cost anything?
What comes over from GitBook?
What happens to my old links?
My docs are in several languages. Does that work?
How long does it take?
Can I keep GitBook live during the move?
What about videos?
Do I need a developer?