Framer to Wix Studio: the complete migration guide

Not the site itself, and this is the thing most people don't know until they try. Framer states it doesn't provide a way to export published sites as HTML files or static website bundles, because published sites are not fully static and depend on its own infrastructure. Your content is different: CMS collections export to CSV through Framer's own plugin, and so do your redirects. So the content moves and the build is recreated. Worth knowing that a newer Framer page written for EU data portability rules says site files can be downloaded at any time, but it names no method and links back to the article saying export isn't available, so check your own account before assuming either.

It becomes a Wix CMS collection, and the two systems line up closely enough that this is translation rather than redesign. Framer's official CMS Export plugin writes each collection to a CSV, and Wix imports up to 50,000 items per file, so volume stops being the constraint it was. Two cautions. Framer doesn't document how reference and multi-reference fields serialise into the export, so the file gets opened and inspected rather than assumed. And the plugin was last updated before Framer rebuilt its CMS in June 2026, so its output is checked against the live collection before anything is imported.

Not if the URLs are handled deliberately, and most of them don't need to change. Neither Framer nor Wix Studio forces a path structure on standard pages, so /about stays /about, and Wix's dynamic page prefix is editable so collection page paths can be preserved too. Where a Framer site is on a plan that includes redirects, that list exports to CSV and merges straight into the new map. The real risk is metadata: titles, descriptions and Open Graph live in Framer's page settings, appear in no export, and have to be captured from a crawl and diffed against the new site before the domain moves.

The forms get rebuilt natively and the destinations keep working. Framer routes submissions out to email, a Google Sheet or a webhook rather than storing them in a queryable inbox, so on cutover the Wix form points at the same place and nothing downstream notices. Framer documents no submissions export and no submissions database, which means there's no historical record inside Framer to migrate. If your submissions were only ever going to an inbox, that inbox is your archive.

They get rebuilt, matched to intent rather than copied frame for frame. Framer's motion is defined inside the project and there's no export path for it, so there's nothing to port even in principle. In practice this is the stage worth spending time on, because the animation is usually why the site was built in Framer. The upside is that Studio's motion tools live in the same interface as the rest of the site, so the person updating the page next year can adjust it without needing whoever designed it.

It depends on whether the next tier actually solves it or just delays it. Framer's Basic plan allows 30 pages and two CMS collections, and Pro raises both, with paid add-ons above that. If you're publishing content regularly, the pattern to watch for is designing the site around the ceiling: merging pages that should be separate, or squeezing two content types into one collection. That's the point where the plan is shaping the site rather than supporting it. Check the current numbers on Framer's pricing page before deciding, because they move.

Yes, and without the seat cost. Framer's on-page editing lets collaborators with content permissions update text, images and CMS content from the published site, with changes reviewed and published by someone with publishing rights. Framer bills additional editors monthly and content editors on top of that. On a Wix Studio site, giving someone the ability to edit content is a permissions setting rather than a purchase, which is usually the practical difference for a team where more than two or three people touch the site.

Mostly not. Standard pages keep their paths because neither platform imposes a structure on them. Collection pages come down to how the Wix CMS is set up: the dynamic page prefix is a default you can edit, so an existing /blog/post-name or /work/project-name structure carries across rather than being redirected. One Framer detail worth knowing if you were planning any consolidation: Framer only lets you redirect sub-paths within your current domain, so anything cross-domain was never handled there anyway.

From €1,750, quoted as a fixed price before anything starts, and two to five weeks from kickoff to launch plus a 30-day monitoring window that runs while you're already live. The number moves on page count first, because with no code export every page is rebuilt from the live site, then on how many CMS collections need modelling and how much of the motion work has to be recreated rather than simplified. Worth putting against it: your current Framer plan, any add-ons you bought to raise a ceiling, and what you pay per editor seat.

For a small site, yes, and the CMS export makes the content half straightforward. Where it turns is specific to Framer. There's no code export, so you're recreating every page from what's on screen rather than from a file, and anything you miss is gone once the subscription ends. Framer documents no bulk media download, so images come down by hand. Reference fields may or may not survive the export in a usable shape and you won't know until you open the CSV. And metadata across a large site has to be lifted from a crawl, which is where organic traffic actually gets lost. The reliable signal is page count: ten pages and one collection is a weekend, and sixty pages with three collections and real motion work is not. Whatever you decide, do the crawl before you cancel anything.