Not today, and the importer names any generator it skips. Octri generates SDKs in TypeScript, Python, Go, Java, Kotlin, Ruby, PHP, Rust, Swift and Dart.

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 Fern to Octri

Zip the repository that holds your fern folder and upload it. Your SDK languages, package name, spec, accent colour, logo and favicon come across, and every page in docs.yml is listed with its path.

Start on the Free plan Book a call

Written by Octri · Checked 25 October 2026

What to have to hand

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

fern/generators.yml
fern/docs.yml
fern/fern.config.json
openapi.yml

What comes across

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

What	In Octri	From Fern
Spec	The project’s spec	api.specs in generators.yml
SDK languages	One SDK per generator	groups in generators.yml
Package name	SDK package name	output.package-name
Project name	Project name	organization in fern.config.json
Accent colour, logo, favicon	Docs appearance	docs.yml
Guide pages	Listed with their paths	navigation in docs.yml
Method names, pagination, streaming	Per-endpoint settings	x-fern extensions in your spec
Guide content	Page drafts, by Pull from GitHub	Your MDX files

Step by step

Export your definition
Octri reads OpenAPI. If your API is written as a Fern Definition, run fern export first and keep the OpenAPI file it writes beside the fern folder.
Bring it in
Sign up, choose Switch to Octri when onboarding asks for your spec, and drop in a .zip of the repository with the fern folder and the OpenAPI file.
Check the preview
Before anything is created, Octri shows what it found: the spec, each generator as an SDK language, the package name, your theme, and every page in docs.yml 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 fern folder, 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 a few tags
Most Fern components render as written. The handful that differ are in the table below, and the page preview shows each one as you fix it.
Set up your SDKs
Check each language in SDK Studio, where the preview shows every call, including the method names your x-fern extensions set. 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.
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.