How to move your site and keep the forms you already use

By Ranjit Bhinge, founder of Blur Studio · Updated · 11 min read

Short answer: You can keep a form when you move a website if the form lives in a separate tool. HubSpot (customer relationship software with a form builder), Typeform (an online form builder), Jotform (another online form builder) and Marketo (Adobe's marketing automation software) forms sit on the vendor's servers, so you paste the same embed code into the new page and your leads, fields and follow-up emails stay put. A form built into your old website platform does not move. You rebuild it, and the old entries stay behind. Either way, send a real test through every form before you switch.

Ranjit Bhinge

A form that stops working after a move rarely shows an error. It just stops sending leads, and you notice weeks later. Here is how to move without losing any.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

The short rule: embedded forms travel, built-in forms get rebuilt. An embedded form is one you made inside another tool and show on your page with a snippet of code. A built-in form is one your website platform created and stores itself, such as a Webflow form, a Framer form or a WordPress plugin form. Before you choose any new platform, sort every form on your site into one of those two piles. That list is the whole job.

The cost of skipping the list is simple: leads that never reach your team. If you are weighing a move to an AI platform such as Ploy, which builds and hosts business websites and rebuilds a site from its public address, the same sorting step applies, because Ploy's own docs say forms may need separate work after a migration.

This page may contain affiliate links from which Blur Studio earns commissions.

The two kinds of forms

KindExamplesWhat happens in a move
Embedded (lives in another tool)HubSpot forms, Typeform, Jotform, Marketo formsCopy the embed code to the new page. Leads, fields, notification emails and past entries stay in that tool.
Built into the website platformWebflow forms, Framer forms, WordPress (a widely used website platform) plugin formsRebuild on the new site. Past entries stay in the old platform, so export them first.

Webflow, a visual website builder, makes the point clearly. Its pricing page FAQ says that if you export your site and host it elsewhere, forms will stop working. Framer, a similar design and hosting tool, says in its help that it does not offer HTML export. If your forms are built in, plan to recreate them. The longer guide on moving from Webflow or Framer covers the rest of that move.

Ploy's migration docs say the same thing in their own words. A Ploy move is "a rebuild, not an identical copy", and its WordPress and Webflow pages list forms among the things that may need separate work. The WordPress page adds a useful step: use the migration report to review where each form sends email, what automatic reply it sends and where past submissions stay. That is exactly the inventory you need, whichever platform you pick.

Step 1: make a form inventory

Open every page of your site, not just the contact page. Forms hide in footers, popups, blog posts, pricing pages and thank-you pages. Then fill in one row per form. Copy this table into a spreadsheet.

Form namePage it sits onKind (embedded or built in)Where entries are storedWho gets the emailGoes to which CRM or listTracking eventLast test date
Quote request/get-a-quoteEmbedded (HubSpot)HubSpot contactsSales inboxHubSpotKey event "quote_submit"
Contact us/contactBuilt inOld platformOwnerNoneNone yet

A CRM is a customer relationship management tool, the place where your contacts and deals live. If a form has no CRM, write "none", because that is the form most likely to be forgotten.

Also write down the old entries you want to keep. Wix, another website builder, says spam submissions stay in its Spam tab for 30 days and trashed ones are kept 180 days. Webflow stores submissions automatically and offers a CSV export, but Webflow's help page does not state how long it keeps them, so check with Webflow. Export every built-in form's entries before you cancel anything.

Step 2: move the embedded forms

For each embedded form, copy the embed code from the form tool and paste it into the same spot on the new page. Then check four things that often break.

  1. Allowed domains. Some connections between a site and a form tool only accept submissions from listed website addresses. Look for an allowed-domains or additional-domains setting in the form tool and add your new address. Do this before the test, or the test will fail and you will not know why.
  2. The tracking script. Forms usually pair with a tracking script on the page. HubSpot's developer docs describe an optional tracking-cookie value, called hutk, that a form submission can carry for lead activity tracking. A submission can be accepted without it, so a form can look fine while the contact record shows no page history or source. After your test, open the contact in HubSpot and check that the page and source are filled in.
  3. Forms from other tools feeding HubSpot. If you run a Typeform or Jotform and rely on HubSpot's tracking code to catch it, check HubSpot's own list of reasons that capture fails for non-HubSpot forms. It includes forms inside an iframe, forms whose submit button is wired up by custom JavaScript, forms added after the page finished loading, and single-page apps. Use the form tool's own HubSpot connection instead of relying on the tracking code.
  4. Consent and cookies. Your new site needs the same cookie banner and privacy notice wiring, or the tracking script may load before consent or not at all. Check local law, and see website visitor tracking and privacy law.

For a Marketo form, the steps are the same: copy the embed snippet, add the new domain wherever Marketo asks for allowed domains, and test. Ploy's feature pages say it supports third-party embeds from HubSpot and Marketo, so the embed route is one to test on any new platform, not just Ploy.

Step 3: rebuild the built-in forms

A built-in form needs three things on the new site: the fields, a place where entries are saved, and a notification that reaches a real person. Keep the fields the same at first. Changing field names and the platform in one go makes it hard to tell what broke.

Check what the new platform does with a submission. On Webflow, the pricing page shows the free Starter plan allows 50 form submissions, while Basic at $15 a month billed yearly shows unlimited form submissions. Check Webflow's pricing page before you rely on either. On Ploy, forms built into a Ploy site save submissions automatically, show them under Sites, then Dashboard, then Submissions, and email the addresses you add under Notifications. If the form has the submitter's own email field, the notification's reply-to uses it, so you can answer by pressing reply.

Limits matter here. Ploy's docs say built-in submissions are text only and each one can be up to 128 KB. A form that accepts a file goes to a database table instead, and those rows do not show in the Submissions list or in the notification emails. The docs say a public form that accepts files should have spam protection and tell you to ask Ploy's Agent, its built-in AI assistant, to add it. Whether Ploy forms include a built-in spam check, an automatic reply to the person who filled in the form, or a consent tick box is not stated in the docs, so ask before you rely on any of them.

Step 4: re-check tracking after the move

Your analytics usually counts a form submit as an event. In GA4, which is Google Analytics 4, Google's free website traffic tool, an event you mark as a key event is the one Google counts as important to your business. Mark only the two or three events that equal a real lead. After the move, compare three numbers for the same week: form entries in your inbox or CRM, key events in GA4, and the count you had before. They will never match exactly, because some visitors block tracking scripts. But a drop to zero, or a big gap that did not exist before, means a form or tag broke. The longer fix list is in website forms not sending leads: fix checklist.

If you use campaign links, keep your tags the same. Google's guidance is to always use utm_source, utm_medium and utm_campaign, with lowercase values, because the values are case sensitive and missing ones show as "(not set)".

Your options, from least to most effort

OptionCost as of November 2026Forms: what you get
No tool: a weekly testFree (your time)Send a test through every form each week and check where it lands. Catches silent breaks.
HubSpot forms embedded on any siteHubSpot's pricing page shows a Free plan at $0 for up to 2 users. Check the page for paid plans, which vary by product and seats.Entries stay in HubSpot whatever site shows the form.
WordPressCheck the vendor page and your host; form plugins and hosting are priced separately.Plugin forms are built in, so they do not move to another platform.
WebflowStarter free (50 form submissions); Basic $15 a month billed yearly (unlimited form submissions); Premium $25 a month billed yearlyBuilt-in forms. Embeds are possible.
FramerFree $0; Basic $10 a month billed yearly ($15 monthly); Pro $30 a month billed yearly ($45 monthly); extra editors $20 eachBuilt-in forms and embeds. No HTML export.
PloyFree $0, Starter $50 a month, Pro $300 a month, Enterprise by quote. AI credits do not roll over.Built-in forms with a Submissions list, plus embeds. See below.

All prices are US dollars on the vendors' pages in November 2026 and can change. Yearly and monthly billing differ, so read the label.

Where Ploy fits, as one option

Ploy is an AI platform: you describe a page to its Agent and it builds and hosts it. You can start on Ploy's free plan to test one page and one form before you commit. On forms specifically, Ploy gives you these things, per its own docs:

  • Submissions saved automatically, a Submissions tab for review and email notifications to any addresses you add. Preview submissions are saved and emailed like live ones, so you can test before launch.
  • A copy of each submission can be sent to another tool, such as a CRM or a Clay table (Clay is a lead data and outreach tool), while the original stays in Ploy. The docs give the example of keeping the form working if the other tool is down.
  • CRM routing. Ploy's pricing page lists HubSpot and Attio (a CRM) from the Pro plan up, and Salesforce (large CRM software) on Enterprise. Some Ploy marketing pages describe integrations without plan limits, so rely on the pricing page.
  • Third-party embeds from HubSpot or Marketo, as Ploy describes them.

What it does not do: it is not a storefront, it has no built-in booking tool, and its migration rebuilds your pages instead of copying them. A move from a URL uses AI credits, and Ploy publishes no price per action, so run one page first and read your usage under Settings, then Organization, then Usage. The deeper walkthrough is in Ploy site migration, and plan details are in Ploy AI pricing.

Who should skip Ploy for this

  • You are only changing hosts and keeping the same platform. A host move keeps forms as they are, so a rebuild is extra work.
  • Your forms take payments, bookings or long multi-step answers. Keep them in a dedicated tool and embed them. Read forms, booking and payments on your website.
  • You need an exact copy of every page and widget. A rebuild is not that.
  • Embedded forms keep their own cost and tracking rules, and no new platform changes that. If the problem is the form tool, switching the website will not fix it.

Worked example with made-up numbers

These numbers are invented to show the method. A landscape design studio sends 60 leads a month through three forms: a quote request (HubSpot embed, 35 leads), a contact form (built into Webflow, 20) and an event sign-up (Typeform, 5). It moves to a new platform on a Tuesday.

FormTest result on stagingFixRetest
Quote requestArrives in HubSpot, but the contact has no page historyAdd the HubSpot tracking script to the new sitePass: page and source filled in
Contact usNo email arrivesRebuild with the owner's address under notificationsPass: email in 20 seconds
Event sign-upEntry saved in Typeform, no HubSpot contactTurn on Typeform's own HubSpot connectionPass: contact created

If the studio had switched without testing, the contact form alone would have lost about 20 leads in the first month. The test took under an hour.

Copy-ready test plan with pass and fail rules

  1. Use a test email you control and a clearly fake name such as "Test Move 1". Submit every form on the new site while it is still on its staging address.
  2. Check three places for each one: the inbox, the spam folder and the CRM or form tool.
  3. Add a backup alert: a second notification address, or a rule that tells you when a week passes with no new entries.
  4. Switch the domain only when every form passes. Then test again the same day on the live address, from a phone as well as a computer.
  5. Test again after any site change, after a plugin or script update, and once a week for the first month.

Pass: the entry appears where your team works within a few minutes, with every field filled in, and the notification reaches a human. Fail: missing email, missing fields, a duplicate contact, no source on the record, or an error shown to the visitor. Any fail means do not switch.

How I'd approach this

I would treat the form list as the first deliverable of any move, ahead of design. In the first week: list every form (day 1), export old entries and copy embed codes (day 2), build or rebuild forms on the new site and add a backup alert (days 3 and 4), run the test plan above and fix what fails (day 5), and only then set a switch date.

Decision rule: if most of your forms are embedded from one tool, keep that tool and move the site freely. If most are built in, pick the new platform partly on how it stores and routes entries. If you want to see how an AI-built site handles this, try one page and one form on Ploy, run the test plan, and compare the credits used. If a form keeps failing, or you need a custom quote or booking flow tied to your CRM, Blur Studio builds the custom version, including CRM and calendar connections and finishing a half-built form flow: see what that includes. For the wider move, read best website migration tools and services and what to do if rankings drop after a migration.

Related guide: How to Move Your Website One Section at a Time.

Related guide: Can My Site Be Moved? How to Check Before You Commit.

A closely related page covers the same ground from another angle: How to Move a Client Domain With Zero Downtime.

For the next step, see How to Move Your CMS Content Into One Place.

Questions people ask

Will my HubSpot forms still work on a new website?

Yes, if the form is a HubSpot embed. The form and its entries stay in HubSpot, so you paste the same embed code into the new page. Then check the allowed domains, add HubSpot's tracking script and open the test contact to confirm the page and source are filled in.

Do my old form entries move with the site?

Entries stored in a separate tool, such as HubSpot or Typeform, do not move because they never left. Entries stored by your old website platform stay there. Export them as a CSV file before you cancel, and check whether the platform deletes old entries on a schedule.

Can I keep Typeform or Jotform forms on a new site?

Yes. Both are embedded tools, so you copy the embed code to the new page. If you want the contact to reach a CRM, use the form tool's own connection to that CRM, because tracking-code capture can miss forms that sit inside an iframe.

How do I know a form has broken after a move?

Send a test entry through it and look in the inbox, spam folder and CRM. Also compare weekly form entries with your key events in Google Analytics. A sudden drop to zero is the usual sign. Do the test again after any site change.

Does Ploy keep my third-party forms?

Ploy says its pages can host third-party embeds from tools like HubSpot and Marketo, and its migration docs say forms may need separate work after a rebuild. Treat every form as something to test, and check Ploy's current docs for your plan before you move.

Do Ploy forms send leads to a CRM?

Ploy's docs say a copy of each submission can go to another tool, and its pricing page and integrations docs list HubSpot and Attio from the Pro plan up. Some marketing pages describe integrations without plan limits, so rely on the pricing page.

Do forms built in Ploy have spam protection or a consent tick box?

Ploy's docs say a public form that accepts files should have spam protection and that you can ask its Agent to add it. They do not state built-in spam protection, an automatic reply or a consent tick box for ordinary forms, so ask Ploy before you depend on them.

How often should I test my website forms?

Test once a week for the first month after a move, then monthly, and always after a site, plugin or tracking change. A weekly test is free and catches silent failures before they cost you leads.

More in this topic: Websites: moving a site without losing traffic (5 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…