Skip to main content
Fimo migrates from published URLs, website-builder exports, static exports, CMS exports, and source repositories. The golden rule: source exports beat inferred crawls. If you have CSV/XML/JSON exports, a media folder, or source code, those are the truth and the public URL is visual and SEO reference.

​
Website builders

The strongest source-backed path when you have a code export plus CMS CSVs. Treat CMS CSVs as authoritative for entries and exported template pages as visual references. CMS, ecommerce, search, form backends, and password protection are not preserved by the code export. Slugs, rich text, images, dates, categories, authors, SEO fields, and locales carry over when present.
Framer has no official source-code export for normal hosted sites, so the CMS CSV export is the useful asset. Use the public site and screenshots for layout, animation intent, and SEO. Animations are rebuilt with restraint — content and editability matter more than matching Framer’s runtime internals.
Expect WordPress XML for pages and posts, and CSV for products. The XML is the content source of truth; product CSVs become product schemas and entries. Design, custom template behavior, forms, search, and many assets do not export cleanly, and manually downloaded assets often need filename reconciliation.
Expect CSV exports for collections, posts, and products — image URLs may appear in the CSVs while the files themselves are not local. Velo app logic, dynamic pages, search, forms, ecommerce, and member areas need explicit replacement plans. Large collections may be split across files; stable IDs are preserved so references can be rebuilt.
Usually HTML, CSS, and media only, with no CMS unless you have separate data. A good fit for one-page or small brochure rebuilds. Repeated sections are turned into Fimo components only where it improves maintainability.

​
Source repositories & unknown platforms

For an existing codebase or an unrecognized platform, Fimo searches for structured data before assuming static content: CSV, JSON, MD/MDX with frontmatter, CMS SDK calls, route loaders, and API fixtures. The current framework is identified only to understand routing and data — not to copy its implementation into Fimo.
Builder HTML is treated as evidence, not the final runtime. Whatever the source, pages are rebuilt with Fimo conventions — schemas, forms, media primitives, and routes — so they stay editable afterward.

​
What’s next

Migrate to Fimo

The migration pipeline and what’s preserved.

Wrap mode

Bring an existing codebase into Fimo.

CMS content

Model your migrated collections as Fimo schemas.