Migration guideMigrate from Document360

Migrate from Document360

See what moves when you migrate a Document360 knowledge base to Documentation.AI, and what you decide along the way.

You can migrate a Document360 knowledge base from an export file or from its live site. The steps are the same as for every platform. See Migrate to Documentation.AI.

What you can migrate from

  • An export from Document360, as the ZIP file or its unzipped folder. It includes your articles, categories, and media. Tell your assistant where the file is.

Two things an export needs today

  • Its images have no public address for Documentation.AI to fetch, so copying them into your media library needs a project API key, set as DAI_API_KEY and DAI_API_BASE.
  • The migrator cannot yet confirm by itself that an export lists every category, so a migration from an export does not pass its final release check. Your assistant reports this, and you decide whether to accept it or migrate from the live site instead.
  • Your live site, such as https://docs.acme.com.

What moves

In Document360In Documentation.AI
Categories and their orderSidebar groups and pages, in the same order
Articles from the WYSIWYG and Markdown editorsPages
Info, warning, error, and success boxesCallout with the matching style
Expandable details sectionsExpandable
FAQ blocksA group of expandable questions
TabsTabs
TablesTables
Embedded frames and videosEmbedded frames and Video
Images and files in the exportFiles in your media library, with a project API key

What needs your decision

  • Snippets. An export contains snippet placeholders, such as {{snippet.contact}}, but not the snippet text. At the second decision, give your assistant the text for each snippet. Pages that use a snippet without its text wait until you do.
  • Workspaces and languages. If your export mixes several, choose which to migrate at the first decision.
  • Articles outside any category. The first decision lists them so you can place them or leave them out.

What does not move