Migration guide
Migrate from OpenAPI Generator to Octri
The move starts from two things your build already has: the spec you generate from, and the package names in your generator config.
Written by Octri · Checked 25 October 2026
What to have to hand
Your OpenAPI file, and your Markdown in a GitHub repository. Everything else is set in API Studio and SDK Studio.
- openapi.yaml
- config.yaml
What comes across
OpenAPI Generator has no config for Octri to read, so the move runs on files you already have. Rows marked “By hand” are what is left for you.
| What | In Octri | From OpenAPI Generator |
|---|---|---|
| SDKs | One repository per language, generated for you | Your OpenAPI file |
| Package names | SDK package settings | packageName or npmName, by hand |
| Templates and patches | Custom code in the SDK repository | By hand |
| API reference | A page for every endpoint, written for you | Your OpenAPI file |
Step by step
Bring the spec
Sign up and upload the OpenAPI file you pass to
-i, or connect the repository it lives in. Octri scores the spec and writes a reference page for every endpoint.Set the packages
Pick your languages and enter the package names from your generator config, such as
packageNameornpmName. Octri generates each SDK, with its tests and mock server, into a repository of its own.Move your patches
Code you patch in after each run, or carry in custom templates, moves into the SDK repository, where custom code is kept through each regeneration by a normal merge.
Release
Publish the first Octri version as a new major version, since method names and types change, then retire the CI job that ran the generator. Each merged spec change regenerates and releases from then on.
Questions
Yes. Octri generates the client libraries, docs and MCP server, so keep OpenAPI Generator for server stubs if you use them. Both read the same spec.
Still deciding?
The comparison sets Octri against OpenAPI Generator row by row, from each product’s own pages, with Octri’s prices beside them.
Other migration guides
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
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
Try it on your own spec
Bring what you have from OpenAPI Generator on the Free plan and see your reference written and your first SDK built.