Getting Started
Docvora supports importing existing documentation from GitBook, allowing organisations to migrate their knowledge bases without manually recreating pages and content.
The migration process supports transferring GitBook spaces, including their page structure, formatting and images.
Existing content within GitBook is not modified during the migration.
To begin migrating from GitBook, a personal access token is required.
The token must be generated from a GitBook account that has access to the spaces intended for migration.
Personal access tokens inherit the permissions of the account they belong to, meaning only spaces accessible to that account can be imported.
Docvora only uses the provided token during the migration process and does not store it.
A personal access token allows Docvora to access existing GitBook documentation during the migration.
Sign in to GitBook.
Open Account settings.
Navigate to Developer tools.
Select API access tokens.
Generate a new personal access token.
Copy the generated token for use during the migration.
Personal access tokens should be kept secure and should not be shared outside the migration process.
Open the Docvora Staff Panel.
Navigate to Migration Tools.
Select Import from GitBook.
Paste the generated token into the Personal access token field.
Select Find spaces to retrieve the available GitBook spaces.
The GitBook account associated with the token must have access to the spaces intended for migration.
Select spaces and options for the import.
Select start import.
The GitBook migration tool supports importing the following content:
GitBook spaces
Page hierarchy and structure
Page formatting
Images
The migration process is designed to preserve the existing organisation and content of GitBook documentation when transferring it to Docvora.
For assistance with migrating from GitBook, the Docvora support team can provide guidance throughout the process.
Visit the Docvora Contact Page to get in touch.