Skip to main content
Theme

Reference

What the tool does not do with forms

Everything a moved form does not carry, and what to do instead. The plan, the run's log and the To do list name each case on your site. How forms move explains what the tool does.

Testing and checking

The tool does notDo this instead
Have a test mode, or hold back any form email while you test.Test on the Insites staging stack, or name yourself as the recipient on the Forms step while you test. Test a moved form safely.
Send a form, or check that an email arrives. Verify proves each form matches the plan, not that the plan names the right people.Send a test from each form before cutover, as the To do list asks.
Check that each workflow email has someone to go to after the load.The plan warns about each form with nobody named. Name them on the Forms step before cutover.

Fields and behavior

The tool does notDo this instead
Rebuild a field that asks for a file, from Webflow, Squarespace or another service. The field is left off and named.Add a file field in the form builder, on a database column of type Media, or ask people to email the file.
Check an upload field on a form copied from Siteglide or an Insites site.Send a test with a file. Insites accepts the file types the instance's upload settings allow, under Assets, Configuration.
Carry show-and-hide rules, several pages or steps, calculated fields, or hidden fields filled in from the address or a campaign, from another service's form. The rebuilt form is one page of fields, and shows every question. The tool finds these in a JotForm form's own page (all four) and a Google Forms page (pages, and answers filled in from the address), and AI can add one the page does not show. The proposal lists each one before you confirm.Keep the service's form, or confirm and do each one again: the To do list names them. Use Form Steps, Conditional Visibility and hidden fields in the form builder, then Generate Form Code. The form builder has no calculated fields: ask a developer.
Carry a script the old page ran to check fields before sending.Insites checks required fields and email addresses itself. Add other rules in the form builder's Fields, such as a length or a format.
Keep one value for a field Squarespace drew as several checkboxes under one name, the way it stored them.Nothing to do: every choice ticked is saved, as a list. A submission from the export keeps the words Squarespace wrote.
Rebuild a HubSpot or Gravity Forms form. HubSpot draws its form from your HubSpot account, and Gravity Forms lives on a WordPress site, so the tool cannot read either form's fields from another site's page. A Gravity Forms form on a WordPress site you move with the WordPress connector is rebuilt.Keep the service's form, or build the form in the form builder and put it on the page in its place.
Rebuild a form from another service that sits in a shared section of the site, such as the footer, rather than in a page.Keep the service's form, or build the form in the form builder and put it in that section.

Where submissions go

The tool does notDo this instead
Know who a Webflow or Squarespace form emailed. Their APIs do not say.Name the people on the Forms step. Until you do, the form saves every submission and emails nobody.
Move a Webflow form whose own Action sends it to another service, such as a Mailchimp list or a Zapier or Make webhook, into Insites.It is kept as it is and still sends there. To keep its submissions in Insites instead, build the form in the form builder and put it on the page in its place.
Recreate what another service did with a submission: its own emails, its connection to a CRM, a mailing list or Zapier. These are set in the service's account and are never on the form's page, so the tool cannot see them. The proposal and the To do list say to check them.Before you confirm, open the form's integrations in the service. When you rebuild such a form, ask a developer to send each submission on from the form's code, or keep the service's form.
Move the past submissions of a form from another service.They stay with the service. Export them there if you need them.
Send Siteglide's own form emails. They are copied for reference only.The form builder's workflow email sends instead, to the staff Siteglide emailed. Read the copies and change the workflow email to match.
Copy a Siteglide form's answers onto the person's own record, as Siteglide did.The answers stay with the submission. The CRM contact each enquiry adds is linked to it.
Move an Insites v4 form's own emails and CRM activity, which no v6 module has.They are taken off the form and named on the plan. Set the form's emails up again in Forms on the new instance.
Send an email from a sender that is not on the new instance's sender list in Insites Console, or from the address a visitor typed.Add the site's own sending address in Insites Console. The visitor's address is the Reply-To instead.
Set the sender of an email whose From is worked out in code with a choice, such as one sender for one office and another for the next.It is left as it was and named on the To do list. Give it one sender, or make one email for each choice.

Spam protection

The tool does notDo this instead
Move reCAPTCHA keys. A key is the old site's and is tied to its domains.A form from Webflow, Squarespace or Siteglide uses the platform's hCaptcha, which needs no keys. A form copied from an Insites site keeps reCAPTCHA: add the keys on the new instance and the site's domains to them. How.
Add spam protection to a form that had none on the old site.Use Turn on hCaptcha in the review on the Forms step. For a Siteglide form it puts the check in each layout the form is shown with, then turns the form's spam protection on. When a layout cannot take it, nothing changes and the review says which layout to add it to. After the load, the To do list says how.
Show hCaptcha as a choice in the form builder. The builder offers reCAPTCHA v2 and v3 only, so a form with hCaptcha shows no choice on Details.Leave it as it is: saving the form keeps hCaptcha. Choosing reCAPTCHA there needs keys and a reCAPTCHA line in Form Code.
Stop you turning spam protection on without the check on the page. Such a form refuses every submission, without a message.Keep the spam_protection "hcaptcha" tag in Form Code whenever spam protection is on.
Send an autoresponder from a form with no spam protection, unless the sender is at the site's own domain on the Console sender list.Turn on hCaptcha, or add the site's own sending address in Insites Console.

After the move

The tool does notDo this instead
Notice a form you changed in the form builder before the final sync. A load, nightly sync or final sync writes it again.Change recipients on the Forms step, make other changes after the final sync, or press Keep on the CODE difference. Changing a form after the move.
Keep the old site's look if you press Generate Form Code in the form builder.Do not press it on a moved form unless you want the builder's own markup.
Move a Siteglide form's access rule that is part of Siteglide's own code, or that calls it. The site's own rule moves with the form, as a policy file the form names, so a members-only form stays members-only. Siteglide's own submission guard is left behind on purpose: it refuses anything a visitor's browser sends.The plan names each rule that did not move, and the To do job Add the access rules back gives its code and the steps: create the rule in CMS, Auth Policies, then choose it on the form's Security tab in the form builder, and add it to the page if the page was members-only too.
Move a Siteglide form that takes a payment.Its page stays on Siteglide and is named on the To do list. Rebuild the page and its payment on the new site, or leave it on Siteglide.
Make a CRM contact for a form with no email field, or for an enquiry whose email is not an address. A callback someone wrote on the form is never replaced.Add the person in the CRM yourself when you need them there.