Carried into the draft
- Markdown pages and directory paths
- Directory landing pages published from README files
- Images included in the Git export
- Redirects declared in GitBook configuration
- A proposed navigation structure for review
GitBook migration
Move from GitBook without hiding what changed.
Move a GitBook space without losing the paths readers already use. Staleless imports the export into a reviewable draft and reports what needs a person.
A report before a commitment
See what moves. Review what cannot.
The import starts from a GitBook export. It counts pages and assets, names changed paths, groups conversion notes by cause, and produces navigation for a person to review.
Named for a person
- Hosted /files assets that are not present in the export
- GitBook-specific blocks without a direct Markdown equivalent
- Navigation labels and editorial ordering
- Every changed or newly normalized URL
The migration
Four steps, with the old site still available.
- 01Export
Create a GitBook Git or Markdown export and keep its asset directory with it.
- 02Inspect
Run the import report first. Nothing overwrites an existing page silently.
- 03Review
Read the conversion notes, navigation proposal, changed paths, and missing assets.
- 04Launch
Preview, crawl, add redirects, then move the domain only when the result is verified.
Verification checklist
The upload finishing is not the migration finishing.
Keep the source export and the old site until readers, search engines, assets, and redirects all reach the intended answers.
- 01Compare the imported page and image counts with the export.
- 02Review every item grouped under “What needs a human.”
- 03Crawl the old public URLs and map each one to the preview.
- 04Test redirects before changing the documentation domain.
Bring a real export
See the migration report before you decide.
Other sources