Migration guides
Move to Octri
A guide for each of 13 tools: what comes across on its own, what you set by hand, and every step of the move in order.
Written by Octri · Checked 25 October 2026
Pick the tool you use now
Your config comes across
Upload the tool’s own config and Octri reads it: languages, package names, theme and the page list.
Migrate from
Stainless
Targets, package name, repository and method names from stainless.yml and your spec.
Read the guideMigrate from
Speakeasy
Languages, SDK name, package name and x-speakeasy extensions from workflow.yaml and gen.yaml.
Read the guide
Migrate from
Fern
SDK generators, package name, docs theme and the page list from the fern folder.
Read the guide
Migrate from
liblab
Spec, languages, auth schemes and package name from liblab.config.json.
Read the guide
Migrate from
Mintlify
Name, theme, spec and the page list from docs.json or mint.json, plus your MDX by Pull from GitHub.
Read the guide
Your spec and Markdown come across
Bring the OpenAPI file and pull your Markdown from GitHub. Settings are a few minutes in API Studio and SDK Studio.
Migrate from
ReadMe
Your OpenAPI file and the Markdown that bi-directional sync keeps in Git.
Read the guide
Migrate from
Redocly
Your bundled OpenAPI file, your Markdown in Git and the redirects in redocly.yaml.
Read the guide
Migrate from
Scalar
The OpenAPI document from your Scalar registry or repository, and your Markdown and MDX guides.
Read the guide
Migrate from
GitBook
The OpenAPI file your API blocks read and the Markdown that Git Sync keeps in your repository.
Read the guide
Migrate from
Stoplight
The OpenAPI file and Markdown articles in the repository your Stoplight project syncs with.
Read the guide
Migrate from
Docusaurus
The OpenAPI file your plugin reads, your MDX pages and the layout in sidebars.js.
Read the guide
Migrate from
APIMatic
The API definition your SDKs are built from and the Markdown guides in your portal.
Read the guide
Migrate from
OpenAPI Generator
The spec you pass to -i and the package names in your generator config.
Read the guide
How the move works
Upload what you have
Choose Switch to Octri when onboarding asks for your spec, and drop in a .zip of your repository or a single config file, up to 15 MB. For a tool without an importer, upload the OpenAPI file or connect its repository.
Check the preview
Octri shows what it found before anything is created: the spec, SDK languages, package names, theme and every guide in your navigation, with a note for anything it could not carry.
Pull your guides
Connect GitHub and choose Pull from GitHub in the API Studio Files panel. Markdown and MDX land as page drafts, and sync on push keeps them current.
Publish and switch the domain
Release your SDKs under the package names your users already install, add redirects for old paths to
octri.json, publish, and point your domain at Octri last.
Questions
Stainless, Speakeasy, Fern, liblab and Mintlify, from their own config files. For every other tool the move starts from your OpenAPI file and your Markdown, which is all those tools keep.
Try it on your own spec
Bring the spec you already have on the Free plan and see your reference written and your first SDK built.