Framer is the fastest way to a good-looking site. It's slower when the site needs to do more.
This site started on Framer too. I moved it when I needed more than the platform gives, and I do the same with yours: pages, animations, CMS and Google rankings move to a custom website.
Where it starts to cost. Not on day one, but as the business grows.
- CMS
A CMS with a ceiling
The number of CMS collections and items depends on your plan. It's enough for a portfolio, but a growing blog or a filterable catalogue soon feels cramped.
- Backend
A beautiful shop window with nothing behind it
A form that sends an email works. User accounts, bookings with rules, a link to your CRM or accounting all call for outside tools and embeds, if they can be put together at all.
- Dependence
The site only lives on Framer
Framer doesn't export your site as code you can run anywhere else. Hosting, CMS and editor come as one package, and the site exists for as long as you pay for it.
What moves animations included.
- Content
Pages and CMS move into code
I take the CMS collections out of Framer, and rewrite pages, layout and animations in code from the published site. The animations stay, now in code that is yours.
- URLs
Every old URL leads to a new one
Where a URL changes, it gets a 301 redirect, with meta titles, descriptions and share images. The rankings the site built on Google come with it.
- Switchover
The old site runs until the new one is ready
I build the new site alongside, on a preview address. Once you approve it, only the DNS records change. You cancel your Framer plan once everything is checked.
Send me your website. You'll get advice and two time slots.
Enter your address and a few details. An email with advice for your platform and two open slots for a call arrives straight away, and I'll look at your site personally and get back to you.
- Advice for your platform you can act on right now, without me
- An idea of what a website could do in your line of business
- Two open slots for a 30-minute call, one click to book
Frequently asked questions
I needed a blog in two languages, a client portal and a proposal system behind the site. Framer is excellent at what it was made for, and that wasn't it.
Yes. I rewrite them in code, so they behave as they did on Framer. Along the way, whatever never quite worked on mobile is easy to fix.
Yes. The editor has only the fields your site has, in plain language, with no canvas where a whole section moves by accident.
Not if the migration is done properly. Every old URL gets a 301 redirect, meta titles and descriptions move with it, and after the switch I watch Search Console until the index settles. A drop in traffic after a migration is a sign nobody did that work, not a consequence of the migration.
It depends on the scope and on whether a redesign comes with it. Roughly the same as a build: a website 3–6 weeks, a web shop 6–12 weeks. The exact timeline is in the proposal, before work starts.
No. You cancel the old platform only once the new site is live and we've checked that content, redirects and, for a shop, orders are all in place. Until then the old site runs as it always has.
Because migrating a five-page website and a shop with thousands of products are not the same job. After a call and a look at your site you get a fixed proposal, and that figure holds until the end of the project.
The site comes with maintenance: updates, security monitoring, daily backups and uptime monitoring. Alongside it comes SEO + AEO, so after the move the site doesn't stand still but gets found by search engines and AI models.