# What happens to contact forms after migration? > When you migrate off WordPress, your contact forms do not carry over on their own, because a WordPress form is run by a plugin rather than stored as page content, so it has to be rebuilt as a feature on the new site. That is straightforward: you recreate the same fields, connect the form to reliable email delivery so submissions reach your inbox, add spam protection, and reconnect any CRM or newsletter integration it fed. The one thing that can be genuinely lost is the archive of past submissions, since those live in the WordPress database, so export them before you leave. Handled this way, visitors see the same form and you keep receiving enquiries without interruption. WPBuildAI rebuilds each form with its fields, delivery, and spam protection wired up, and flags the stored submissions to export first, so no enquiry is missed in the move. Source: https://wpbuildai.com/what-happens-to-contact-forms-after-migration/ By lawrence-arya ยท 2026-06-14 --- When you migrate off WordPress, your contact forms do not carry over on their own, because a WordPress form is run by a plugin rather than stored as page content, so it has to be rebuilt as a feature on the new site. That is straightforward: you recreate the same fields, connect the form to reliable email delivery so submissions reach your inbox, add spam protection, and reconnect any CRM or newsletter integration it fed. The one thing that can be genuinely lost is the archive of past submissions, since those live in the WordPress database, so export them before you leave. Handled this way, visitors see the same form and you keep receiving enquiries without interruption. WPBuildAI rebuilds each form with its fields, delivery, and spam protection wired up, and flags the stored submissions to export first, so no enquiry is missed in the move. Form plugins deserve particular scrutiny on the way out: Patchstack recorded [11,334 new WordPress vulnerabilities in 2025 with 91 percent in plugins and 43 percent of high-impact issues exploited within a day of disclosure](https://patchstack.com/whitepaper/state-of-wordpress-security-in-2026/), and a form left running on the old site is an unattended entry point as well as a lost lead. ## A form is a feature, not page content The distinction that makes this clear is between what a page shows and what a plugin does. The text and images of your pages are content, and a capture of the live site brings them across. A contact form is different: it is behavior, run by a plugin that renders the fields, validates them, sends the email, and often records the entry in the database. That behavior is not part of the published content, so it does not travel the way text does. This is why a form has to be rebuilt rather than copied, and it is also why treating it as a feature to reconstruct, with the same fields and the same delivery, is the reliable approach. ## What comes across, and what does not It helps to split the form into two parts, because they migrate differently. The live form itself, the visible fields and the act of submitting, is rebuilt on the new site and works from launch. The historical submissions already collected are the part at risk, because they sit in the database behind the login, not on the public pages, so they are exactly the kind of thing a [front-end capture cannot reach](/will-an-ai-website-builder-import-my-existing-content). So the plan splits cleanly: rebuild the live form as a feature, and export the stored entries as data before you lose admin access. Keeping those two tasks separate in your mind is what prevents the quiet loss of past enquiries. ## Rebuilding the form on the new site On the new platform the form becomes part of the page, and submitting sends the data to a form endpoint or a small serverless function that emails you and can pass the data on to your CRM. You recreate each field exactly as it was, the required ones, the dropdowns, the file upload if you had one, so nothing changes for the visitor. Because there is no form plugin loading on every page, the rebuilt form is lighter, which helps the [page experience](https://web.dev/articles/vitals) that supports both conversions and rankings. The goal is a form that looks and behaves the same to anyone filling it in, while being simpler to run underneath. ## Do not lose the submissions you already have The single mistake that actually loses data is leaving the stored submissions behind. Most form plugins keep entries in the database and can export them to CSV, so while you still have admin access, run that export and save the file. If your form only ever emailed you and never stored entries, then your inbox already holds the history and there is nothing extra to rescue. Either way, decide this deliberately before launch rather than discovering after the fact that months of enquiries were only ever in a database you no longer control. The live form and every future submission come across through the rebuild; it is only the archive that depends on you exporting it in time. ## Delivery, spam, and integrations A form is only useful if the messages arrive, so delivery is the part to get right. Point the rebuilt form at a reliable transactional email service rather than trusting a raw server mail function, so submissions land in your inbox and not in spam, which ties into [keeping your email working through the move](/keep-email-working-when-changing-web-host). Add spam protection, such as [reCAPTCHA](https://developers.google.com/recaptcha) or a honeypot field, so the new form is not immediately buried in junk. Then reconnect any integration the old form fed, the newsletter signup, the CRM, the notification to your team, and confirm that a real test submission flows all the way through. Delivery, spam protection, and integrations are the three things that quietly break if no one checks them, so test each one before launch. ## Steps to migrate a contact form safely 1. **Export stored submissions to CSV** while you still have WordPress admin access. 2. **List every form and its fields**, including required rules, dropdowns, and uploads. 3. **Rebuild each form** on the new site with the identical fields. 4. **Wire up reliable delivery** through a transactional email service, not raw server mail. 5. **Add spam protection** and reconnect any CRM or newsletter integration. 6. **Send a real test submission** and confirm it reaches every destination before launch. ## Worked example: a studio that missed no enquiries Consider a design studio whose only lead source was a contact form on WordPress, run by a popular plugin that stored every entry. Before migrating, they exported the stored entries to CSV so the year of past enquiries was safe. The rebuild recreated the form with the same name, email, budget, and message fields, pointed it at a transactional email service, added a honeypot for spam, and reconnected the notification to their shared inbox. They sent a test enquiry and watched it arrive, then launched. Visitors filling in the form noticed nothing different, the studio kept receiving leads without a gap, and the site was faster because the form plugin and its per-page scripts were gone. ## Limitation: complex form logic needs deliberate rebuilding It is honest to bound this. A standard contact or enquiry form rebuilds cleanly, but a heavily conditional form, one with multi-step logic, calculated fields, payment steps, or deep third-party workflows, is more than a set of fields and takes deliberate reconstruction and testing. The data still moves and the form can still be rebuilt, but budget time to recreate and verify the logic rather than assuming it comes across for free. And no rebuild can recover stored submissions that were never exported, so the export step is not optional if that history matters to you. ## Common mistakes - Assuming the form copies over with the pages, when it is plugin behavior, not content. - Leaving stored submissions in the database and losing them with admin access. - Rebuilding the fields but forgetting to wire up reliable delivery, so messages vanish. - Launching without spam protection and drowning in junk on day one. - Never sending a real test submission, so a broken integration is found by a lost lead. ## Key points When you migrate off WordPress, your contact forms are rebuilt as a feature rather than copied, because a form is plugin behavior, not page content. Recreate the same fields, wire the form to reliable email delivery, add spam protection, and reconnect any CRM or newsletter it fed, and visitors see no change while you keep receiving enquiries. The one part that can be truly lost is the archive of past submissions, since those live in the database behind the login, so export them to CSV before you give up admin access. Test a real submission end to end before launch, because delivery, spam, and integrations are what quietly break. Complex conditional forms take deliberate rebuilding, but they still move. WPBuildAI rebuilds each form with its fields, delivery, and spam protection wired up, and flags the stored submissions to export first, so no enquiry is missed in the move. Send your web address for a free analysis. Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.