holydocs migrate

Usage

bash
holydocs migrate <platform> [options]

Imports content from another docs platform. Support is partial today: some platforms copy files automatically, while others print the manual export steps you should follow.

Options

Option	Description	Default
--source <path>	Source directory for file-based migrations	Current directory
--api-key <key>	API key for ReadMe migrations	—
--url <url>	Remote URL for platforms that need one	—
--token <token>	Token for platforms that need one	—
--dir <path>	Output directory	Current directory

Supported Platforms

Platform	Current Behavior
mintlify	Copies pages and assets so you can finish setup in HolyDocs
docusaurus	Copies docs content and strips some Docusaurus-specific frontmatter
gitbook	Prints the current manual migration steps
readme	Checks the ReadMe API and lists categories
confluence	Prints the current manual migration steps
notion	Prints the current manual migration steps

Mintlify

bash
holydocs migrate mintlify

Mintlify migration copies the content tree first so you can finish the setup inside your HolyDocs project.

You can also migrate from another source directory:

bash
holydocs migrate mintlify --source ../old-docs --dir ./docs

Docusaurus

bash
holydocs migrate docusaurus --source ./legacy-site --dir ./docs

The current Docusaurus migration:

• Copies .md and .mdx files
• Removes some Docusaurus-specific frontmatter like sidebar_position
• Converts sidebar_label into title when needed

You still need to create or finish docs.json yourself afterward.

GitBook

bash
holydocs migrate gitbook

Today this prints the manual export steps. It does not yet convert a GitBook export automatically.

ReadMe

bash
holydocs migrate readme --api-key rdme_xxxxxxxxxxxxxxxx

Today this verifies the ReadMe API key and lists the categories it finds. Full page import is still a follow-up manual step.

Common Flow After Migration

For most migrations, the next steps are:

1. Run holydocs init if you still need a local HolyDocs config scaffold
2. Run holydocs check
3. Run holydocs dev
4. Run holydocs deploy

holydocs migrate uses a positional platform argument. It does not support the older --from, --config, or --dry-run flags.