Will your contact form still work after a website move? A test you can run

The short answer
Your contact form will work after a website move only if someone rebuilds it on the new site and you see a real test message arrive from it, because WordPress form plugins do not move with your pages. The test is simple: write down every form and where it sends, submit each one before the move, then submit it again on the new site's private preview and once more on launch day.
You need three things before you start: a list of your site's pages (your menu and your sitemap are enough to begin), access to every inbox your forms send to, and a phone as well as a computer, so you can test the way your visitors do.
- List every form and where it sends. The list is the test the new site has to pass.
- Send a test from each form before the move. This records what "working" looks like today.
- Test each form on the private preview. Same fields, same inbox, not in spam.
- Check the spam protection. It should stop bots and let people through.
- Re-test on launch day. On your real domain, after the switch.
- Save the old messages before the old site goes. They do not move.
If your form is already failing today, fix that first. Our guide to a WordPress contact form that stopped sending email walks through it, and a move is a bad time to find a problem that was already there.
1. List every form and where it sends
Write one line for every form on your site: the page it is on, what it asks for, which inbox receives it, and anything else it feeds, such as a CRM or a mailing list. Forms hide in more places than the contact page, so walk the whole site, including the footer and sidebar.
Write down | Example | Why it matters |
|---|---|---|
The page | /contact/, /quote/, the footer on every page | A form in a sidebar or footer is the one most often missed |
What it asks for | Name, email, phone, message, a "service" dropdown | The new form must ask the same things, with the same required fields |
Where messages go | hello@yourbusiness.com and the office manager | Every inbox gets a test later |
What else it does | Adds people to a mailing list, sends to a CRM or Zapier, emails the visitor a copy | These connections live in plugins and settings, not in your pages |
The confirmation | "Thanks, we will reply within one business day", or a thank-you page | Visitors notice when this changes |
Where old messages are kept | In the WordPress dashboard, or only in email | Step 6 depends on it |
To find the inboxes, open each form's settings in WordPress. Contact Form 7 keeps them on the form's Mail tab, and Gravity Forms under the form's notifications. If you cannot log in to WordPress, ask whoever looks after the site to send you the list. It is a reasonable request, and the answer tells you how well the site is documented.
The "what else it does" column is the one people skip. A form that quietly fed your mailing list for years will stop doing it the day it is rebuilt without that connection, and nothing on the page will look different.
2. Send a test from each form before the move
Submit every form on your current site as a visitor would, from a logged-out browser on your phone and on your computer, and write down what happened: the time, the confirmation you saw, and where the message arrived. This is your baseline, the proof of what "working" meant before anything changed.
For each form, record:
- The confirmation on screen. The exact message or the thank-you page.
- Where the message landed. Inbox, spam, or not at all, for every address on your list.
- What the message looks like. The subject line, the sender, and whether pressing reply answers the visitor.
- How long it took. A few seconds or a few minutes; either is fine, but write it down.
Use a personal address outside your business domain as the visitor's email, and type "TEST" in the message so nobody on your team treats it as a lead. If any form fails this test, stop here and fix it on the current site first. Moving a broken form only moves the problem.
3. Test each form on the new site's private preview
Before launch, the new site should exist at a private preview address while your live site stays untouched. Submit every form on the preview, using the list from step 1, and compare each result with your baseline from step 2: same fields, same required fields, same confirmation, and a message in every inbox, not in spam.
Check | What has to be true |
|---|---|
Fields match | Every field from your list is there, with the same labels, options and required fields |
Every inbox receives it | Each address on your list gets the test message |
Not in spam | The message lands in the inbox, not the spam or junk folder |
Reply works | Pressing reply in your inbox answers the visitor, not the website |
Confirmation matches | The visitor sees the same message or the same thank-you page |
Mistakes are explained | Leave a required field empty and submit: the form should say which field, and keep what you typed |
Phone works | The whole form is easy to fill in and send on a phone |
Connections | Anything from the "what else it does" column is either working or written down as a gap you agreed to |
If a message lands in spam on the preview, say so before launch. It usually means the new site's email is not yet set up to prove it comes from your domain, which is fixable, and much cheaper to fix now than after a month of missed leads.
If the form fed a CRM or a mailing list and the new form does not, that can be fine, as long as you know and agree before launch. Finding out three months later, when the mailing list has stopped growing, is the expensive version.
4. Check the spam protection
Spam protection is the part of a form most likely to change in a move, because it often comes from a separate plugin or service tied to your old setup. Check two things on the preview: that a real person can send the form without a fight, and that you know what happens to messages the protection holds back.
- A person gets through. Fill in the form on your phone and on your computer. If a puzzle or checkbox appears, it should be quick. If you have to try twice, so will your visitors.
- The protection is there. Ask what replaced your old CAPTCHA or spam plugin. A form with no protection at all fills up with junk quickly, and the real messages get lost in it.
- Held messages are visible. Ask where suspicious messages go. A message that is blocked silently is a lead you never see. You want a place to check them, or a notice that some were held.
Spam checks such as Google's reCAPTCHA are usually set up for specific web addresses. A check that works on the preview address can behave differently on your real domain, which is one reason step 5 exists.
5. Re-test every form on launch day
On launch day, after your domain points to the new site, run the step 3 test again on your real domain: every form, every inbox, phone and computer. Then send an ordinary email from your personal account to your business address, to confirm your inbox still receives mail after the change.
Your domain's settings (its DNS) say where your website lives and also where your email is delivered. When a move changes those settings, the email records have to be carried over exactly. If they are not, your website looks fine and your inbox goes quiet, and form messages stop arriving with everything else.
When | What to test |
|---|---|
Launch day | Every form on the real domain, plus one ordinary email to your business address |
The first week | One form submission every couple of days, and a look at the spam folder |
Every month after | One test through every form, and after any change to the site or your email |
The monthly test is the habit that protects you long term. Sites change after launch: a setting gets switched, an email account is renamed, a staff member leaves and their inbox is closed. A quick test finds the break before a customer does.
6. Save the old messages before the old site goes
Messages your forms received before the move stay on the old WordPress site; they are not part of the move. Before the old site is switched off or its hosting ends, export them or confirm you do not need them.
How much there is depends on your form plugin:
- Gravity Forms keeps every entry in the WordPress dashboard and has a built-in export for them.
- Contact Form 7 keeps no copy on its own. If an add-on such as Flamingo was installed, it may hold years of messages that need exporting.
- Most other form plugins keep entries in the dashboard too. Look for an "Entries" or "Messages" menu next to the form settings.
If your form only ever sent email and nothing was stored on the site, your inbox already holds the history, and there is nothing to export. Write down which case you are in, so nobody has to guess once the old site is gone.
Who should keep their forms on WordPress
Some forms are applications, not contact forms, and moving them means rebuilding a feature. Stay on WordPress, or move those pages last, if a form takes payments, runs across several pages, shows or hides questions based on earlier answers, or is the core of what the site does, such as a booking or quoting system.
The same goes for whole sites. If your site is a store, has members or courses, or is built around one plugin feature, a contact form test is not the deciding question, and staying is usually the right answer for now. Our guide to whether you should move off WordPress covers that decision. And if the site works, your forms deliver, and nobody touches it, there is no reason to move just for the sake of it.
How we rebuild forms on EmDash
We move WordPress sites to EmDash, the open-source CMS from Cloudflare that its makers call "the spiritual successor to WordPress", built on Astro. EmDash's own guide treats forms as something to prove, not assume: it says to keep the original WordPress site available until "old URLs, redirects, SEO metadata, forms, and plugin-dependent pages have been verified in the new deployment" (EmDash docs).
So forms get their own work on every move, and the steps above are the same checks, run by us:
- Rebuilt from the original. Each form is rebuilt on the new site with the same fields, required fields, recipients and confirmation message.
- Checked against the live site. Each rebuilt form is compared with the one on your live page before anything changes.
- Tested before launch. A real test message has to reach its recipients before the form goes live.
- Spam protection included. Old CAPTCHA fields are replaced, and messages flagged as spam are kept for you to review, not deleted.
- Every message kept. Messages are saved on your site as well as emailed, so an email problem never loses a lead. You can read and export them from the site's admin.
- Gaps in writing. Connections to a CRM, a mailing list, Zapier or a webhook are listed and confirmed with you. A form we cannot rebuild yet, such as one with payments, several pages or conditional questions, keeps its page on WordPress until it is rebuilt or you agree in writing to go without it.
- Old messages flagged. Before launch we tell you which forms hold earlier messages in WordPress, so you can export them before the old hosting ends.
Forms are one line of a longer list. Our website migration SEO checklist covers the rest: every URL, redirect and search detail, with the proof to ask for at each step.
Bring your WordPress site into the AI era on EmDash and Astro. A free, read-only check of your public pages shows whether your site is a good fit and the exact price before you ask, with every option listed under pricing.
Want to see where your site stands first? Check your site for free.
Frequently asked questions
Will my contact form still work after I move my website?
Only if it is rebuilt on the new site and tested there. WordPress form plugins do not move with your pages, so each form needs rebuilding, then a real test message from the private preview and again on launch day, checked in every inbox it sends to.
Does Contact Form 7 move with my site?
Not to a site that no longer runs WordPress. Contact Form 7 is a WordPress plugin, so its forms have to be rebuilt on the new platform with the same fields, recipients and confirmation message. Contact Form 7 also keeps no copy of messages on its own, unless an add-on such as Flamingo was installed.
How do I test a contact form without confusing my team?
Submit it from a logged-out browser using a personal email address outside your business domain, and type TEST in the message. Tell whoever reads the inbox to expect it. Check every address the form sends to, including the spam folder, and note the time each message arrived.
Why do form emails go to spam after a website move?
Usually because the new site's email is not yet set up to prove it comes from your domain, so inboxes treat it as suspicious. It is fixable before launch. That is why the test on the private preview checks the spam folder as well as the inbox, every time.
What happens to the messages my old forms received?
They stay on the old WordPress site and do not move. Gravity Forms keeps entries in the dashboard with a built-in export. Contact Form 7 keeps none unless an add-on stored them. Export what you need before the old site is switched off or its hosting ends.
How often should I test my contact form after launch?
On launch day, every couple of days for the first week, then once a month. Also test after any change to the site, your email provider or the people whose inboxes receive the form. Each test is quick and catches a break before a customer does.