The short verdict
- The visible site is the easy part of a move. The connections behind it are where data gets lost.
- List every integration before you start, including the ones nobody remembers adding.
- Run old and new side by side for a few days where you can.
01Make the list first
Generated sites gather integrations over time: each prompt that said “add a newsletter signup” or “connect this to Supabase” left something behind. Before moving anything, find all of it.
- Read the code or project settings for API keys, environment variables and service names.
- Check the page source for script tags: analytics, pixels, chat, heatmaps.
- Submit every form and follow where the data goes.
- Ask the team what they get from the site: which emails, which Slack alerts, which spreadsheet rows.
02The usual integrations, and how they move
Forms
On generated sites, forms often write straight to a database like Supabase, or call an email API. On Webflow, native forms store submissions and email them, and can send data on with webhooks or tools like Zapier and Make. Map every field, and keep the same destination where people rely on it. If sales reads leads from a spreadsheet, the new form should fill the same spreadsheet.
Analytics
Reuse the same Google Analytics property or other analytics account so your history continues. Recreate any custom events: form submits, button clicks, sign-ups. Check that conversions still fire after launch, because this is the integration most often half-moved.
Ad and social pixels
Meta, LinkedIn and Google Ads tags need to be in place on day one, or campaigns lose tracking and optimisation. Check with whoever runs the ads.
Embeds
Booking tools, video players, maps, review widgets. Most give you an embed code that works anywhere. Use this as a chance to load them only when needed, which helps speed.
Newsletter and CRM
Signup forms connected to Mailchimp, HubSpot or similar. Make sure new signups still land in the right list with the right tags.
Anything with logins
If the generated site has user accounts, that is an app, not a marketing site. Keep it where it is, or plan it as its own project. Do not try to move it with the marketing pages.
03Consent comes too
If you need cookie consent where your visitors are, every tracking script must respect it on the new site. Check that optional scripts stay off until someone accepts, and that the banner’s choices actually change what loads.
“Nobody notices a broken integration on launch day. They notice it three weeks later, when the numbers look odd.”
04Testing after launch
Go through your list on launch day and tick each item off by testing it, not by checking it is installed. Submit each form and see the data arrive. Trigger each analytics event and see it in the real-time view. Then check again a week later, when real traffic has had time to show gaps.
05Questions people ask
Can Webflow forms send data to Supabase or a CRM?
Yes, through webhooks or an automation tool. Many CRMs also have direct Webflow integrations.
Will I lose my analytics history?
Not if you keep the same analytics property. Data from before and after the move sits in one place.
What should we do with the old Supabase project?
Keep it until you are sure nothing depends on it, export the data you need, then remove anything holding personal data you no longer use.
Can you map our integrations for us?
Yes. Send us the link and we will list everything we can find connected to it.
