Migrate from Docusaurus, Nextra, or Fern

You can migrate a Docusaurus, Nextra, or Fern site from its repository. Tell your assistant the folder where you cloned it. The steps are the same as for every platform. See Migrate to Documentation.AI.

To migrate one of these sites from its live address instead, see Migrate from other sites and Markdown.

Docusaurus

• Pages move with their titles, descriptions, headings, text, tables, and code.
• The generated sidebar moves as it is: your docs folders, _category_ files, and sidebar_position values.
• A sidebars.js or sidebars.ts file is code, and the migrator does not run code from your repository. Your pages still move, and you review the sidebar at the first decision.
• Versioned or translated sites move with every version and language. You review how they are arranged at the first decision.
• Draft and unlisted pages do not move, because Docusaurus does not publish them. Your assistant reports how many were left out.

Nextra

• Pages move with their titles, descriptions, headings, text, tables, and code.
• The sidebar is written in _meta files, which are code the migrator does not run. You review the page order and labels at the first decision.

Fern

• The navigation in fern/docs.yml moves as it is, including tabs, versions, and page order.
• API reference sections move with their OpenAPI specifications.
• Files that docs.yml does not reference are not published by Fern, so they are not migrated.

What needs your decision

• Custom React components, at the second decision
• Any sidebar that comes from code, at the first decision

What does not move

• Your footer, custom fonts, and banner. See What does not move.

Related