Wix to Framer Migration: When Templates Stop Scaling

Wix is very good at getting you online. It is much less good at the moment your brand outgrows the template, your SEO structure needs deliberate decisions, and your marketing team wants to ship a landing page without a support ticket. That moment is what this guide is about — how to recognise it, and how to move without losing what the site already earned.

TL;DR

• The Wix ceiling is structural, not aesthetic — it shows up in CMS shape and page-level SEO control.

• Export nothing. There is no clean Wix export; this is a rebuild with content carried across deliberately.

• Crawl the live site before you touch anything. That crawl is your redirect map and your metadata source.

• Watch for Wix's URL patterns — /post/, /blog-1/, and language prefixes generate redirect work.

• Budget 4–8 weeks for a typical marketing site, most of it content decisions rather than build time.

How to tell you have actually hit the ceiling

Wanting a nicer site is not a reason to migrate. These are:

• Every copy change goes through one person because everyone else is afraid of breaking the layout.

• You need a page type the template does not have, and the workaround is a page pretending to be that type.

• Your blog and your case studies are the same collection because splitting them was too hard.

• You cannot set a per-page canonical or a distinct meta description without fighting the editor.

• The mobile layout is a separate site you maintain twice.

Those are workflow costs, and they compound weekly. A prettier homepage does not.

Step one: crawl before you change anything

Before a single pixel moves, crawl the existing site and export every URL with its title, meta description, H1, and inbound internal links. This export is the single most valuable artefact in the project. It becomes your redirect map, your metadata source, and — at the end — the baseline you compare against to prove nothing was lost.

Teams that skip this step end up reconstructing their old URL list from memory and Google Search Console, which finds the top twenty pages and misses the two hundred that collectively carried more traffic.

Step two: decide what survives

A migration is the only sanctioned opportunity to delete things. Go through the crawl and mark each URL: keep, merge, or drop. Merges need a decision about which URL survives and a redirect from the other. Drops need a redirect to the nearest useful page, not to the homepage — a homepage redirect is treated as a soft 404 and wastes the equity you were trying to preserve.

Step three: rebuild, do not port

There is no meaningful Wix export, and that is less of a problem than it sounds. What you are carrying across is content and URLs, not markup. Build the Framer side as a proper system: components with variants, CMS collections shaped around your actual content types, and templates that generate per-item metadata rather than repeating one description across a collection.

The most common mistake here is recreating the Wix structure faithfully, including its compromises. If the blog and case studies were one collection because Wix made splitting hard, split them now.

Step four: Wix URL patterns that generate work

• /post/slug — Wix's blog prefix. Decide whether you keep it or move to /blog/slug, and redirect accordingly. Keeping it is not shameful; changing it for tidiness costs redirect risk for no ranking gain.

• /blog-1/, /copy-of-... — artefacts of the editor. These often have real inbound links, so they still need redirects even though the names are embarrassing.

• Language prefixes — Wix Multilingual generates /es/-style paths. Map each language separately and keep hreflang intact.

• Query-string pages — dynamic pages that rely on parameters need a rethink, because the Framer equivalent is usually a CMS route.

Step five: redirects before DNS, not after

Write the redirects from the crawl, load them, and test them against the staging domain before DNS moves. Then flatten chains: if the Wix site already redirected A to B, your new redirect should point A directly at C, not at B. Chains leak authority and slow crawling, and they are invisible unless you look for them.

The redirect count you can actually ship

Wix sites accumulate redirect volume fast — every /post/ slug, every /copy-of-... artefact, every language prefix is its own line — and Framer's redirect rules are plan-gated, not unlimited. Pro caps out at 100 rules, Scale at 500, with a hard ceiling of 2,500 on the highest tier. A sixty-page Wix blog with a few years of history can burn through the Pro cap on posts alone before you have touched the marketing pages. Count your redirect map against the plan's limit before DNS day, not after — finding out mid-cutover means either upgrading under pressure or triaging which long-tail URLs lose their redirect. Framer also supports wildcard and capture-group syntax (/blog/*, or /blog/*/post/* mapped to /article/:1/entry/:2) for pattern-based Wix slugs, which collapses what would otherwise be dozens of one-off rules into one.

Step six: verify against the baseline

After launch, crawl again and diff line by line against the original export. You are looking for URLs that 404, titles that changed without a decision, descriptions that got regenerated from a template, and internal links still pointing at old paths. This pass takes an hour and catches the failures that otherwise surface in Search Console a month later.

What it costs and how long it takes

A typical Wix marketing site — twenty to sixty URLs, a blog, a few templates — runs four to eight weeks and sits in the middle of the published pricing bands. Most of the elapsed time is content decisions, not build. The build is fast; deciding which of your two hundred pages deserve to survive is not.

What to do next

Start with the crawl, even if you are months from committing — it will tell you how big the job actually is. The Wix to Framer page covers the method in more detail, and the SEO-preserving migration checklist is the same document I run on client projects.