Carried into the draft
- Markdown and MDX page paths
- Navigation from docs.json or mint.json
- Redirects declared in Mintlify configuration
- Referenced snippet files and shared content
- Local images and downloadable assets
Mintlify migration
Move from Mintlify without hiding what changed.
Bring a Mintlify repository into Staleless while keeping its Markdown, navigation intent, shared content, assets, and redirects visible for review.
A report before a commitment
See what moves. Review what cannot.
The import starts from a Mintlify repository. It counts pages and assets, names changed paths, groups conversion notes by cause, and produces navigation for a person to review.
Named for a person
- Custom React or MDX components
- Interactive blocks with no portable Markdown meaning
- Theme and site-specific presentation settings
- Generated pages or assets absent from the repository
The migration
Four steps, with the old site still available.
- 01Export
Provide the documentation repository, including docs.json or mint.json and snippets.
- 02Inspect
Run the import report first. Nothing overwrites an existing page silently.
- 03Review
Read the conversion notes, navigation proposal, changed paths, and missing assets.
- 04Launch
Preview, crawl, add redirects, then move the domain only when the result is verified.
Verification checklist
The upload finishing is not the migration finishing.
Keep the source export and the old site until readers, search engines, assets, and redirects all reach the intended answers.
- 01Review the proposed navigation beside the original site.
- 02Open every reported custom component and choose a portable replacement.
- 03Compare redirect rules and normalized page addresses.
- 04Search the preview for high-value product and API terms.
Bring a real export
See the migration report before you decide.
Other sources