Love your Framer design? Keep it. Own the code.
Framer is a beautiful place to design. When the site needs to do more, or your team wants an agent making the changes, we rebuild it page for page on code you own, with the motion that matters.
In short
A Framer migration keeps the design and moves it onto code you own. ZINC rebuilds your pages, components, and motion on Astro or Next.js, moves your CMS content, and keeps or redirects every URL.
Your team then updates the site by asking its AI agent, with every change previewed and approved through Dispatch.
25+ years of strategy, design, and digital delivery for brands including:
When the site has to do more than look good.
Own every line.
The site lives in your repository and runs on any modern host. No platform decides what you can build next.
Logic a canvas cannot hold.
Calculators, integrations, gated content, and pages that share code with your product.
Motion with restraint.
We keep the animation that serves the story and cut what slows the page, so the site feels just as alive and loads faster.
Every Framer feature gets a destination.
Before cutover, each thing your site does has an agreed replacement, an owner, and a test.
| On Framer | After the move |
|---|---|
| Pages and layouts | Rebuilt page for page and verified at every breakpoint you use. |
| Components and variants | Rebuilt as reusable components your agent uses for new pages. |
| Effects and animations | Rebuilt with CSS and light scripts, honoring reduced-motion settings. |
| CMS collections | Exported and imported into structured content, with every item checked. |
| Forms | Rebuilt and routed to your CRM, tested to the inbox. |
| Redirects and locales | Carried into your host’s rules and verified before launch. |
Your design, content, and URLs come with you.
The site moves page for page onto Astro or Next.js on Cloudflare, Vercel, or Netlify. We recommend the stack because we sell none of them.
- Design preserved and verified at representative pages and viewports
- Pages, posts, images, PDFs, and media
- URLs preserved where possible, every other one mapped with a 301
- Forms, CRM delivery, analytics, and consent, each tested end to end
- Your code in your own repository, on your own hosting account
- Dispatch connected at cutover, so every agent change is previewed and approved
Nothing gets designed until every URL has a plan.
The same six steps on every move, written down while we moved our own website. The boring part comes first, because the boring part is what protects your traffic and your leads.
- Step 01
Inventory every URL.
We crawl the live site and list every page by template before anything is designed or built.
On our own moveOur site: 49 live URLs across six templates, each with a destination before a line of code.
- Step 02
Keep the URLs.
Same paths, same slugs. An address only changes when a 301 redirect is in place for it.
On our own move44 kept their exact address. 5 retired pages got 301s. Our highest-traffic page never moved.
- Step 03
Export everything.
CMS content, every file on the old platform’s CDN, and the rendered HTML of every page as the reference copy.
On our own move549 files moved off the old CDN. 4 CMS collections, 45 items, imported and checked.
- Step 04
Parity first. Then improve.
The first version is a faithful copy: same pages, same copy, same metadata. Changes come after sign-off, so any traffic shift has one cause to look at, not ten.
On our own moveOur first complete build took one day, compared page by page against the original by screenshot.
- Step 05
Prove the business paths.
Forms, CRM delivery, notifications, analytics, and consent are tested end to end, from the visitor’s click to the right person’s inbox.
On our own moveLesson we learned: a form that saves a lead is not a form that tells anyone. We test to the inbox now.
- Step 06
Govern, launch, and watch.
Dispatch is connected before the agent touches production. Redirects go live at cutover, the sitemap is submitted, and 404s and indexing are watched closely.
On our own moveSince our launch: 36 reviewed changes in six weeks, each one previewed before release.
We moved our own website first.
wearezinc.com moved from Webflow to Next.js in August 2026, using the same six steps. Here is what that looked like.
- live URLs kept or redirected
- 49 of 49
- files moved off the old CDN
- 549
- to the first complete build
- 1 day
- reviewed changes in the first six weeks
- 36
When staying on Framer is the right call.
A move should pay for itself. Sometimes it will not, and we will tell you.
- A small team that redesigns often and loves the canvas
- A marketing site with no custom logic or integrations
- No need for an agent to work on the site
See your Framer design on code you own.
Give us your URL. We rebuild two pages on an agent-ready stack, run one real change through Dispatch, and send back a stack recommendation and a migration map. No commitment.
Questions about leaving Framer.
The design is rebuilt page for page and verified at the breakpoints you use. Motion is rebuilt where it serves the story, with reduced-motion support, and anything we propose to simplify is agreed with you first.
Yes. Designers keep working where they like. New designs become components, and your agent uses those components for future pages, so the site stays on brand.
Not if the move is done with discipline. Rankings slip after a migration for three reasons: URLs that break, page signals that get dropped, and crawl problems after launch. We keep URLs wherever we can, redirect the rest one to one, carry over every title, description, and heading before changing anything, and watch 404s and indexing closely after cutover. Some fluctuation while search engines re-crawl is normal, so we do not promise unchanged rankings. We do promise not to guess.
You do. The code lives in your own repository, the hosting account and domain stay in your name, and the content is yours. Turn Dispatch off and the website keeps running.