Skip to main content
Migration brings an existing website into Fimo without silently dropping content. It inventories your source, rebuilds pages with Fimo conventions, and imports your media, content, and forms — so the result is a real Fimo project your team can keep editing.

​
How it works

fimo migrate prepares an agent-ready migration draft from a published URL. The bare command runs the full pipeline; each stage is also a subcommand you can run on its own:
The output is a draft and an evidence pack, not the final visual rebuild — your coding agent does the source-faithful rebuild pass from the handoff the CLI writes.
Migration and deployment are separate. Importing content is part of migration; fimo deploy / fimo publish are a single, final, owner-approved step — never run them just to “check” rendering.

​
What’s preserved

Routes & redirects

Every source route is rebuilt, redirected, or listed as unresolved — nothing disappears silently.

CMS & content

Collections and entries are modelled as Fimo schemas, with source IDs, slugs, dates, and authors preserved.

Media

Referenced assets are uploaded into the Fimo media library and rewired from the originals.

Forms

Forms become Fimo-native forms, a third-party plan, or a documented unsupported note.

SEO

Titles, descriptions, canonical URLs, share images, and metadata carry over when present.

Locales

Localized routes and content are kept, not collapsed into a single language.
A verifiable QA gate confirms coverage before a migration is called complete: source counts must match imported counts, and any gap is recorded as an explicit, owner-visible unresolved item.

​
What’s next

Supported sources

Webflow, Framer, Squarespace, Wix, Carrd, and generic exports.

Wrap mode

Bring an existing codebase or framework site into Fimo.

Build with the CLI

The schema, entry, media, and form commands migration relies on.