Migrating from the legacy version

Last updated 2 days ago

Follow this guide if you already have content on legacy.gitbook.com

Before migrating, you should check the important differences brought by the new version. If you see blockers, do not hesitate to contact us through our support messaging.

Migrating a legacy organization

If you own an organization on legacy.gitbook.com, you can migrate it automatically to the new version.

Starting the migration process has no consequence until you confirm the migration. This allows you to experiment the new version and check that everything is right before moving in definitively.

You can migrate your organization(s) to the new version either from the new dashboard, or from your organization's page on legacy.gitbook.com.

Legacy organizations are suggested for migration on your dashboard

Either way, you will be asked to follow the different migration steps. If you experience any issue, contact us through the Intercom messenger widget.

After finishing this process, you will be able to experiment with your imported organization, before confirming the migration definitively. You must wait 24 hours before confirming the migration.

Migrating individual books

Our priority has been to migrate organizations first. Books that did not belong to a legacy organization cannot be migrated as easily yet, but we are working on facilitating individual user migration.

My book is on GitHub

If your book is on GitHub, you can simply login to the new version using your legacy GitBook credentials, create an organization for your books and setup the GitHub integration for each of your books repositories. In the end you should have one personal organization for your own books, containing a space for each of your book repository with the GitHub sync configured.

My book is not on GitHub

We are working on adding a migration button for single-user and their non-GitHub books. For now, you can simply manually copy over your content. If this is not conceivable, contact us through Intercom.