How-to
Test a moved form safely
Send each moved form once before cutover, and check three things: the submission is saved, the right people get the workflow email, and the page says thank you. Do it without emailing the site's owner or their customers by surprise.
Before you send anything
Unless the plan holds them, a moved form sends its emails for real. On a production instance a moved form sends its workflow email from the moment it loads, to the people the plan names. To test with nothing sent at all, tick Hold emails and outside connections until cutover on the plan: see Test on a live instance safely. A held form saves each submission and says thank you, and sends none of its own emails or API calls, so test them after you turn them on. A submission made while they are held is never emailed later. The hold does not cover everything that can send, such as a form from another service or code that writes a send out in full: the plan names those under Not held. Otherwise, decide where test emails go first:
| New instance | Where a form's emails go | What to do |
|---|---|---|
On the Insites staging stack (its address ends staging-insites.io) | To the Insites team's test inbox, never to the people named on the form. | Test that each submission is saved and the page says thank you. Test the email again once the site is on a production instance. |
| On a production instance | To the people named on the form, for real. | While you test, name yourself as the workflow email's recipient on the Forms step of Transform, and name the site's owner again before cutover. Or tell the owner a test is coming. |
- The autoresponder is made switched off on every form the tool rebuilds, so a test never emails the address you type in the form unless you switch it on.
- Never test with a customer's address. Use your own, so the autoresponder and the CRM contact land on you. Each test enquiry adds a CRM contact for the address you give: delete it afterwards.
- A form moved from an Insites site keeps its emails as they were, recipients and all, and switched on if they were on. Test it on the staging stack, or tell its recipients first.
Send a test from each form
- Open the plan's Forms step and note each form and the page it is on.
- Open the page on the new instance in a normal browser window, not an automated one: hCaptcha may ask a robot-like browser to prove itself.
- Fill in every field with test values and your own email address, and send it.
- Check the page shows the old site's thank-you message, or goes to the page the old form sent people to.
- In the instance's admin, open Data, then the form's database, and check the submission is there with every field filled in and Sent from naming the page.
- Check the workflow email arrived where you expect, with every field listed. Reply to it once: the reply goes to the address you typed in the form.
- When the form adds CRM contacts, check the contact for your address is in the CRM with the name you gave, and the enquiry is linked to it.
- Try once with a required field left empty. Nothing is saved: the browser, or the page, asks you to fill it in.
- For a form rebuilt from another service, read its job on the To do list. It names what the service's form did that the rebuilt one does not, such as rules that show questions, pages or hidden fields. A question that was required only when a rule showed it is required for everyone until you change it, so test the form as a visitor who would never have seen that question.
- Delete your test rows and the test contact.
Then get it ready for its first visitor
- On the Forms step, name the people who should get each workflow email, and run the plan again.
- In the instance's admin, open Forms, open each form, read its autoresponder on Email Notifications, change the words if you want, and switch it on. Do this after the final sync, or press Keep on its CODE difference, so a sync does not switch it off again. Why.
- Check each form that should check for spam does. A spam check that is on must be on the page too.
- A form protected by hCaptcha has a To do job that says so. Do not save it in the Form Builder: the Form Builder offers only None, reCAPTCHA v2 and reCAPTCHA v3, so the form looks unprotected there, and saving it there may clear the hCaptcha setting.
- Close the form jobs on the To do list.
From staging to production, and the final sync
- Load the copyStaging or production instance
- Test each formAs on this page
- Name the recipientsOn the Forms step of Transform
- Freeze the old siteStop changes and new submissions
- Final syncBrings anything sent since
- Move the domainInsites Console, then DNS
- Switch autoresponders onAnd send one more test
The diagram as a list
- Load a copy onto a staging or production instance.
- Test each form as this page says.
- Name who each workflow email goes to on the Forms step of Transform.
- Freeze the old site: stop changes, and new submissions where you can.
- Run the final sync, which brings anything sent on the old site since the copy.
- Move the domain in Insites Console, then DNS.
- Switch the autoresponders on, and send one more test from each form.
When you tested on the staging stack, test each form again once the site is on a production instance, because only there does the email reach real people. Copy first, then cut over.
A submission sent on the old site during the freeze is copied by the final sync when the source keeps its submissions in a way the tool reads: Webflow's API, or a Siteglide or Insites database. For Squarespace, past submissions come only from each form's export, so add the newest export once the freeze starts: a submission given twice is added once. A form from another service keeps its submissions with that service.