Migrate to Documentation.AI
Move your documentation from Mintlify, GitBook, ReadMe, Document360, or another platform to Documentation.AI with an AI assistant, and check a preview before anything goes live.
The Documentation.AI migrator moves an existing documentation site into your Documentation.AI project. You describe the migration to an AI assistant. The migrator copies every page word for word, rebuilds your sidebar, and checks the result against your old site. You make four decisions along the way, and your live site changes only when you merge the result.
Before you begin
- You need the Editor or Admin role in the organization that owns your Documentation.AI project.
- Every plan includes preview sites, so you can check the result before it goes live. See Preview sites.
- Install the migrator in Claude Code or Codex. See Install the migrator.
- Migrate only a site you own, or one whose owner has given you permission to copy it.
What moves to Documentation.AI
| Part of your site | What happens to it |
|---|---|
| Pages | Copied word for word: titles, descriptions, headings, text, tables, and code |
| Sidebar | Rebuilt with the same tabs, groups, languages, versions, and order |
| Components | Callouts, cards, tabs, steps, and accordions become their Documentation.AI equivalents |
| Links | Links between pages point to the new pages, and links to headings keep working |
| Page addresses | Kept the same. If an address changes, a redirect sends visitors to the new one |
| Images and files | Copied into your project's media library |
| API reference | Endpoint pages from your OpenAPI specification keep their method badges in the sidebar |
| Look | Your brand colors, logo, favicon, and top bar links, on the template you choose. Read from your live site, or from a Mintlify repository; other repositories and exports carry no branding |
What moves in detail depends on your old platform. Anything Documentation.AI has no place for, such as a custom footer, is listed for you instead of guessed. See What does not move.
Supported platforms
Mintlify
Live sites and repositories
GitBook
Live sites and Git Sync repositories
ReadMe
Sync repositories, the ReadMe API, and live sites
Document360
Export files and live sites
Docusaurus, Nextra, and Fern
Repositories
Other platforms
Any live site, Markdown folders, and MadCap Flare
How a migration works
Your assistant runs the migrator on your computer and stops only when it needs you. At each decision it shows a short summary and asks you to choose. It never approves a decision for you.
Start the migration
Tell your assistant which site to migrate. It asks how you want to deliver the result and which template to use.
Decision 1: pages and structure
The migrator finds every page and reads your sidebar. You confirm that the list is your site, and choose anything to leave out.
Decision 2: conversion plan
You review how components convert, how page addresses carry over, and how the new site looks. Anything without a clear equivalent is explained so you can decide.
Decision 3: converted site
The migrator converts every page and compares it with the original. You review the results before the migrator creates the migration branch.
Decision 4: preview
Documentation.AI builds a preview of the migration branch. The migrator checks every preview page, then you review the preview and approve the release.
Go live
You merge the migration branch in the dashboard. Your live site changes only at this step.
If something cannot move exactly, the migrator stops and explains what to decide. It never rewrites or drops your content to get past a problem.
Choose how to deliver
Both ways end with the same migration branch and the same preview.
| Without Git | With Git | |
|---|---|---|
| Best for | Anyone, including people who do not use Git | Teams that already work in the project's repository |
| You need | Your Documentation.AI sign-in | A copy of your project's repository, and permission to push to it |
| The result | A migration branch created in your project | A migration branch pushed from your copy of the repository |
If Documentation.AI manages your project's repository for you, migrate without Git.
Migrate without Git
How to migrate without Git
Start the migration
Open Claude Code or Codex and describe the migration, for example:
Migrate https://docs.acme.com to Documentation.AI without Git
Sign in and choose your project
Your browser opens so you can sign in to Documentation.AI and allow access. If your account can edit more than one project, your assistant asks which one to use.
Make the first three decisions
Review each summary, then approve it or ask to see more. See How a migration works.
Sign in again to create the migration branch
Your browser opens again. It opens each time the migrator needs your project: to choose it, to copy your images, and again here. The migrator sends every page to a new branch in your project, such as migration/mig-5f2c0a1b9e, and publishes that branch. Your live site does not change.
Open the preview
In the editor, switch to the migration branch and open its Preview link. Give the preview address to your assistant, and it checks every page. See Check the preview.
Approve the release and go live
Make the fourth decision, then merge the migration branch. See Go live.
Migrate with Git
How to migrate with Git
Copy your project's repository to your computer
Find your project's repository in Settings → Git Settings, and clone it to your computer.
Start the migration
Open Claude Code or Codex and name the folder you cloned, for example:
Migrate https://docs.acme.com to Documentation.AI. My project's repository is cloned at ~/acme-docs
Your browser opens once so you can sign in to Documentation.AI. The migrator needs this to copy your images and files into your project's media library.
Make the first three decisions
Review each summary, then approve it or ask to see more. See How a migration works.
Let the migrator push the migration branch
The migrator creates a branch such as migration/mig-5f2c0a1b9e and pushes it with your own Git access. Your current branch and any unfinished work in the folder are not touched. Documentation.AI builds a preview of the pushed branch automatically.
Open the preview
In the editor, switch to the migration branch and open its Preview link. Give the preview address to your assistant, and it checks every page. See Check the preview.
Approve the release and go live
Make the fourth decision, then merge the migration branch in the editor or through a pull request. See Go live.
Check the preview
The migrator opens every page of the preview and compares it with your old site. A page fails the check only when a reader would miss something:
- The page does not load.
- Text or a heading from the old page is not on it.
- A link on the page leads nowhere.
- A sidebar entry is missing.
Differences in how Documentation.AI draws a page are listed as notes, not failures. For example, a language label above a code block, or a wide table that scrolls sideways on a phone.
If a page fails, your assistant shows you which one. Fix the cause and check again. If you look at the page and it is acceptable, tell your assistant to accept it with a short reason. The report records the finding with your name next to it.
Go live
Going live replaces your project's current pages and sidebar with the migrated site. If the project already has pages you want to keep, copy them somewhere safe first.
Open the migration branch
In the editor, switch to the migration branch.
Merge it into your live branch
Click Save, choose Save & Merge, then click Merge. If your team reviews changes in Git, choose Save & Create PR and merge the pull request instead. See Branches and previews.
Finish the switch
Point your domain to Documentation.AI and check a few old addresses. See the Migration checklist.
Find the report
The migrator writes a report for you and anyone who needs to sign off: what moved, what did not and why, and what still needs a decision. It is saved in the folder for your migration, for example ~/migrations/acme-docs/report/customer-report.pdf. Ask your assistant to open it.
The report is also saved as a web page. The PDF version needs Chrome or Chromium on your computer.
Common questions
If a migration stops
Your assistant shows the message and what it means. Match it below:
- "this account can edit no Documentation.AI project": Ask an admin in your organization for the Editor role, or sign in with a different account.
- "could not sign in to Documentation.AI": Sign in to the dashboard in the same browser, then ask your assistant to try again.
- "Path "…" already appears at …": Your old sidebar lists the same page in two places, which Documentation.AI does not accept when you migrate without Git. Migrate with Git instead.
- "publishing … met conflicts with changes made in the editor meanwhile": Someone edited the migration branch in the editor at the same time. Resolve the conflicts in the editor, then ask your assistant to publish again.
- "cannot push to …": Your computer does not have permission to push to the repository. The message ends with the fix, such as signing in with the GitHub CLI.
- No Preview link appears: The preview may still be building. See Preview sites.
What does not move
| Item | What happens |
|---|---|
| Footer links and social links | Documentation.AI has no footer setting. They are listed in the report. |
| Custom fonts | Not copied. You can change typography with Custom CSS. |
| Announcement banner | Documentation.AI has no banner setting. It is listed in the report. |
| Background images and decoration | Not copied |
| Components with no equivalent | You decide how to handle each one at the second decision. Nothing is left out without your decision. |
| Features only your old platform offers | Listed on the page for your platform, such as ReadMe variables |