Skip to main content
In-place “wrap mode” — adopting an existing framework app without rebuilding it — is rolling out. This page covers the source-backed migration available today. It will expand as wrap mode ships.
When you already have your site’s source — a repository, a framework export, or a builder code export — Fimo adopts it through a source-backed migration rather than a URL crawl. Your own files become the source of truth, and the site is rebuilt with Fimo conventions so it stays editable by your team and operable by agents, on real git you own.

​
Source-backed vs. URL-only

Source-backed

You have the code, CMS exports, or media folder. Fimo inspects them directly and treats them as authoritative; a public URL is only visual and SEO reference.

URL-only

Only a published URL exists. Fimo starts from fimo migrate <url> to crawl the site and build a draft evidence pack.
Most real projects are hybrid — source files plus a live URL — and Fimo uses the source as truth while comparing routes, SEO, and visuals against the URL.

​
What “wrap” means here

Adopting an existing site is still a rebuild into Fimo, not a wrapper around your framework’s runtime. Fimo identifies your current framework only to understand routing and data, then re-expresses pages with Fimo primitives: schemas for content, Fimo forms, the media library, routes, and locales. That is what keeps the result editable in Studio and by scheduled agents afterward — and what makes “no lock-in” real, since it’s your repo and your git the whole way.
Nothing is dropped silently. Every route, entry, asset, form, redirect, locale, and SEO field is imported, deliberately ignored with a reason, or listed as unresolved.

​
The verifiable gate

A migration is only “complete” once the QA gate passes: source counts must match imported counts, every referenced asset must be uploaded to the Fimo media library, and every form must have a Fimo replacement or a documented plan. Any remaining gap becomes an explicit, owner-visible unresolved item rather than a silent omission.

​
What’s next

Migrate to Fimo

The full migration pipeline and what’s preserved.

Supported sources

What Fimo can migrate from, platform by platform.

No lock-in

Why your code and repo stay yours.