Migrate from an AI-built site. Edit your content without another prompt.
AI built your site and now nobody can manage it? Sites from Lovable, Bolt, v0, Replit or code generated in Cursor keep their copy inside the code. I move it to Webflow, or to custom development in Astro with Sanity, with proper SEO, and keep or redirect every existing URL.
WHY LEAVE
Why people leave an AI-built site.
When the prototype became the business site.
AI builders are great for a quick prototype and for testing an idea. A business site needs more: a CMS so marketing can change content, and a foundation that search engines and the next developer can understand.
Every text change is a new prompt
Copy, offers and contact details live inside components. Changing them means prompting the AI again and hoping nothing else breaks.
Content tangled with code
Headings, paragraphs and images sit inside React components. Without separating them, the content can't be translated or reused.
Search engines see an empty page
Many of these sites render only in the browser and send almost no HTML. Google and AI search get little to read.
SEO basics are missing
Page titles and descriptions, a sitemap, canonical URLs, redirects and structured data are often absent.
Unclear security
API keys in browser code, an open database or a form with no spam protection. Nobody has checked what the site exposes.
Code nobody knows
Nobody wrote or read the generated code, and in a larger project it's hard to find your way around it.
MIGRATION TARGET
Where to from an AI-built site?
Depends on who runs the site.
Not sure? I'll recommend one after an audit.
WHAT CARRIES OVER
What carries over.
And what replaces copy in the code.
I take the content from the source code, from the database if the site has one, and from the published pages, and move it into the new structure. Here's where everything goes.
| AI-BUILT SITE | WEBFLOW | SANITY CMS |
|---|---|---|
| Copy written into components | Text you edit right on the page | Fields and blocks in Sanity |
| Pages and sections | Pages built from ready sections | Pages built from blocks |
| Images in the project folder | Assets, compressed | Sanity media library |
| Database records (Supabase and similar) | CMS collections with custom fields | Documents in Sanity, or connected via API |
| Page titles and descriptions | Title, description, OG, canonical URL | The same fields on every document |
| Forms | Webflow forms | Forms connected to your system |
| Design and layout | Rebuilt in Webflow, responsive | Carried over to the new build, or refined |
| Login and app logic | Not migrated, handled separately | Not migrated, handled separately |
What replaces the add-ons
| FEATURE | WEBFLOW | SANITY CMS |
|---|---|---|
| Editing copy with a prompt | The Webflow editor on the page | Sanity Studio with a live preview |
| Rendering in the browser | Ready pages from Webflow hosting | Pages prebuilt by Astro |
| Meta tags by hand, or none | SEO settings for pages and CMS templates | SEO fields in Sanity, metadata in Astro |
| No sitemap, no redirects | Automatic sitemap and 301 redirects in settings | Sitemap from content and 301 rules on Vercel |
| API keys in browser code | No custom server code to expose | Server functions, keys kept out of the browser |
| Hosting with the builder | Managed Webflow hosting | Code in Git, hosting on your own Vercel account |
PROCESS
How an AI-built site migration works.
From code to content you manage yourself.
Code and site audit
I go through the source code, the published site and any database, and list where the content lives, what the site sends to the browser and what SEO is missing.
URL map and redirects
I list every URL the site has or Google knows, including routes that exist only in the app's JavaScript. Where a URL changes, it gets a 301 redirect.
Content out of the code
I pull copy, images and data out of the components and the database, give them a clean content structure and import them into the new CMS.
Your content review
You compare the new site with the old one on a private preview and try editing content yourself. You leave comments right on the page, and I fix them.
Launch
I switch the domain, check redirects, forms and analytics, and submit the new sitemap. The original builder project stays until you cancel it.
Post-launch monitoring
I watch Search Console for indexing and 404 errors. Pages that used to look empty to Google now show up in full.
Send me your site's URL. I'll tell you what it takes.
I'll look at what the site was built with, where its content lives, what search engines see and whether anything leaks out, and suggest Webflow or a custom build. No commitment, no sales pitch.
STATUS:OPEN FOR PROJECTS· REPLY WITHIN 2 DAYS· NO COMMITMENT
FAQ
What people ask
about leaving an AI-built site.
Which AI builders can you migrate from?
Lovable, Bolt, v0, Replit, and projects generated in Cursor or a similar editor. What matters is access to the source code, or at least to the published site.
What do you need from us to get started?
Your site's URL. Access to the GitHub repository or a project export from the builder speeds things up, and if the site uses a database, I'll need access to that too.
Can't you just add a CMS to the existing site?
Sometimes you can, and I'll say so after the audit. Often the content is so tied to the components, and the site so dependent on browser rendering, that a clean build on a CMS is the more reliable path.
Will the design stay the same?
It can. I carry the layout, colours and type over to the new site, or refine them with you. Separating content from code doesn't require a new look.
Will we keep our URLs and rankings?
URLs that Google knows either stay or get a 301 redirect. Because the new pages are rendered before they reach the browser, search engines will see more of your content than before.
The site has logins and a database. What happens to that?
The marketing site moves to Webflow or a custom build. Login, users and app logic I review separately and suggest whether to keep them, connect them, or rebuild them as a custom app.
Can we edit the site without a developer, or AI, afterwards?
Yes. In Webflow you edit pages directly, in Sanity in an editor with a preview. You only need a developer for new features.
DIDN'T FIND YOUR ANSWER? .
MORE PLATFORMS