Does trying the import change my current setup?

No. The importer only reads the files you upload, and Pull from GitHub only reads your repository. Nothing is written back to either, so your current site keeps running until you move the domain.

Will someone help with the move?

Yes. Book a call and a founder will go through your project with you and help the first release over by hand. Questions also reach us at founders@octri.dev.

Migration guide

Migrate from Mintlify to Octri

Zip your docs repository and upload it. Your name, logo, favicon, primary colour and spec come across, every page in your navigation is listed with its path, and most of your MDX renders as written.

Start on the Free plan Book a call

Written by Octri · Checked 25 October 2026

What to have to hand

Octri reads Mintlify’s own files. A .zip of your repository or a single config file, up to 15 MB.

docs.json
mint.json
openapi.json

What comes across

Each row is a field the Mintlify importer reads, and where it lands. Rows marked “By hand” are what is left for you.

What	In Octri	From Mintlify
Spec	The project’s spec	openapi in docs.json
Site name	Project name	name
Primary colour, logo, favicon	Docs appearance	colors, logo, favicon
Guide pages	Listed with their paths	navigation
Guide content	Page drafts, by Pull from GitHub	Your MDX files
SDK languages	Picked in onboarding	By hand

Step by step

Bring it in
Sign up, choose Switch to Octri when onboarding asks for your spec, and drop in a .zip of your docs repository, or docs.json (or mint.json) with your OpenAPI file.
Check the preview
Before anything is created, Octri shows what it found: the spec, your name and theme, and every page in your navigation with its path. Anything it could not carry is named in a note under the preview, so you know what is left to do by hand.
Pull your guides from GitHub
Connect the repository that holds your Mintlify docs, then choose Pull from GitHub in the API Studio Files panel. Pick up to 50 Markdown or MDX files at a time and each lands as a page draft, with its title, description, icon and badge taken from the frontmatter. Switch on sync on push and later edits in Git keep landing on the same pages.
Rename two tags
Almost every Mintlify component renders as written. The two that differ are in the table below.
Set up your SDKs
Mintlify carries no SDK settings, so pick your languages on the next screen. Give each language the package name your users already install, and publish the first Octri release as a new major version, since method names and types can change. Every later spec change arrives in the SDK repository as a pull request.
Keep your old links working
Open octri.json in the Files panel and add a redirect for each old path, starting with the ones in the redirects block of docs.json. A rule that ends in /* covers a whole section, and a project keeps up to 500 of them.
Go live
Publish, then point your custom domain at Octri last, so readers keep the old site until the new one is ready. From then on every merged spec change rebuilds the draft of your docs, SDKs and MCP tools, ready for you to publish.

Tags that change name

Note, Tip, Info, Warning, Card, CardGroup, Accordion, AccordionGroup, Steps, Tabs, CodeGroup, ParamField, ResponseField and Frame render as written.

Mintlify	Octri
<Tree>	<FileTree>
<Columns>	<CardGroup>

Questions

No. Every endpoint page shows the call through your own SDK in each language you publish, generated from the same spec, so the samples match the package your users install.