Skip to main content
Theme

Explanation

How forms move

A form is the part of a site most likely to fail quietly: it can look right and still email nobody, or email the wrong people. This page explains what the tool builds for each form, what happens when a visitor sends one, and what happens to a form you change after the move. Test a moved form safely says how to check one, and What the tool does not do with forms lists every gap with what to do instead.

What a moved form is made of

A form from Webflow, Squarespace or Siteglide, or one you rebuild from another service, is built the way the Insites form builder builds one: the database first, then the form on top of it, then its emails. It opens in the instance's admin under Forms like a form someone made there.

  1. The form on the old siteIts fields, button and messages
  2. A database for itOne column a field, made first
  3. A form-builder formSaves to that database
  4. The page draws itWhere the old form was
  5. Its two emailsWorkflow on, autoresponder off
  6. A CRM contactFound or made for each enquiry
The diagram as a list
  1. The tool reads the form on the old site: its fields, its button and the messages it shows.
  2. It makes a database for it first, one column a field.
  3. It builds a form in the form builder that saves to that database.
  4. The page draws that form where the old form was.
  5. The form gets its two emails: a workflow email to the site's owner, switched on, and an autoresponder to the person who sent it, switched off.
  6. When the form asks for an email address, each enquiry finds or makes a CRM contact.
PartWhat it is
The databaseOne column for each field, labeled, grouped and with a tooltip, plus Sent from, the address of the page each submission came from. On a collection's item pages that is the item's own address, such as /portfolio/st-kilda-fc. A form from Webflow or Squarespace also has a column that finds each past submission again on a later sync, so the same submission is never added twice. Its name is in the plan, such as contact.
The formA form-builder form named after the old one, in the builder's own folder, modules/ins_forms/. Its Form Code is the old page's own markup, with the old classes, labels and button, inside the platform's form tag, so the page looks as it did and posts to the database.
The pageDraws the form where the old one was. Insites v6 refuses to draw a form on a page its site search reads, so each such page is copied with site search off. It stays in /sitemap.xml.
After sendingThe visitor goes back to the page they sent it from, which shows the old site's thank-you message. When the old form sent people to another page of the site, they go there instead.
The workflow emailTo the people you name on the Forms step of Transform, with every field of the submission and a link to it in the admin. Its Reply-To is the address the visitor gave, so replying answers them. It is made only once someone is named: Insites cannot keep an email with nobody to send to.
The autoresponderTo the address the visitor gave, made switched off, so nobody gets an email you have not read. Replies to it go to the first person the workflow email goes to, or the address the old site links to. Where replies go.
The senderBoth emails are sent from the instance's own sender, chosen when the email is sent from the list in Insites Console. The form's name is the From Name. This needs the Insites CRM module 6.1.2 or later on the new instance. Why.
The CRM contactOn by default for a form that asks for an email address: each enquiry finds the CRM contact with that address, or makes one with the name and phone number it gives, and is linked to it. How it works.
Spam protectionThe platform's hCaptcha, where the old form checked for spam with reCAPTCHA or a captcha of its own. hCaptcha needs no keys of your own. A form that checked nothing on the old site checks nothing on the new one until you turn it on.

How each source's forms move

Webflow

Rebuilds each form on a copied page in the form builder. One form on many pages, such as a sign-up in the footer, is one form with one database, and each submission records its page. A form styled differently on some pages keeps each look. A field that asks for a file is left off and named. A form whose Webflow settings send it to another service with an Action of its own, such as a Mailchimp list or a Zapier webhook, is kept as it is, still sending there. Webflow forms.

  • Past submissions: copied from Webflow's API, into the form's database.
  • Who the workflow email goes to: Webflow does not say, so the Forms step asks.

Squarespace

Rebuilds each form block and newsletter block from the definition Squarespace writes into the page, with Squarespace's own classes. A name field becomes first and last name columns, an address field one column a line, and a checkbox field with several choices keeps every choice ticked. File and image fields are left off and named. Squarespace forms.

  • Past submissions: from each form's export, which you add on the Forms step. How.
  • Who the workflow email goes to: Squarespace does not say, so the Forms step asks.

Siteglide

Each form a copied page shows is already a platform form. It moves into the form builder, saving to its moved database and drawing the site's own form layout. Siteglide's own emails are copied for reference but not sent: the form builder's emails send instead. A form Siteglide checked for spam uses hCaptcha. A form only some people could send keeps that rule when the rule is the site's own: it is copied as a policy file the form names. A rule that is part of Siteglide's own code cannot run on Insites, so the plan names it and the To do list says how to add it again. A form that takes a payment stays on Siteglide with its page. Siteglide.

  • Past submissions: copied with the form's database.
  • Who the workflow email goes to: filled in from the form's staff email on Siteglide. You can change it.

Insites v4, v5 and v6

Each form is copied as it is, at the same file, with its spam protection, its callbacks and the emails it sends. Its emails send from the new instance's sender. An Insites v4 form that adds a CRM contact when it is sent now calls the v6 CRM's own modules/insites_crm/crm/create_contact_on_submit, which needs CRM 6.1.6 or later, and its two CRM emails (insites_external_email and insites_internal_email) stay on the form under the v6 CRM's names. The v4 CRM activity is not recreated, because a submission is kept on its contact under Related data instead. Any other v4 notification has no v6 copy: it is taken off the form and named on the To do list. Moved emails.

  • Past submissions: copied with the form's database.
  • Who the workflow email goes to: as on the old instance.

A form from another service

A JotForm, HubSpot, Typeform, Google Forms or similar form embedded in a Webflow page is kept as it is, still sending to that service. You can choose to rebuild it as an Insites form instead, for every service but HubSpot and Gravity Forms, whose forms the tool cannot read. Rebuild it as an Insites form.

  • Past submissions: they stay with the service.
  • Who the workflow email goes to: the people you name when you confirm the rebuild.
  • What it will not do: the rebuilt form is one page of fields, with no rules, hidden values or calculations, and it sends nothing on to other services. The tool reads the form's page for rules that show or hide questions, pages, hidden or prefilled fields and calculated fields, and the proposal lists what it finds before you confirm, so you can keep the service's form instead. Confirm anyway and the To do list says how to do each one again. Form limits.

When a visitor sends a moved form

  1. A visitor sends the formFrom the page on the new site
  2. Spam checkhCaptcha, when the form has it
  3. Fields checkedRequired fields and email addresses
  4. SavedA row in the form's database
  5. CRM contactFound or made, and linked
  6. Emails sentWorkflow, and autoresponder if on
  7. Thank-you messageBack on the page they sent it from
The diagram as a list
  1. A visitor sends the form from the page on the new site.
  2. When the form has spam protection, Insites checks the hCaptcha first.
  3. Insites checks the required fields are filled in and that an email field holds an email address.
  4. The submission is saved as a row in the form's database.
  5. When the form asks for an email address, the CRM contact for it is found or made, and the row is linked to it.
  6. The workflow email goes to the people named on the form, and the autoresponder goes to the visitor if you switched it on.
  7. The visitor is sent back to the page, which shows the thank-you message.

When a check fails, nothing is saved and nobody is emailed. The page is drawn again with a line asking the visitor to check each field and try again. Insites checks the fields itself, so the check holds even when a visitor's browser skips its own.

A spam check that is on must be on the page too. A form whose spam protection is switched on, but whose Form Code has no spam_protection "hcaptcha" tag refuses every submission and says nothing. We measured this on a test instance on October 23, 2026. If you edit Form Code, keep that tag, and if you turn spam protection off, take the tag out too.

What you choose on the Forms step

The Forms step of Transform lists every form the move builds, with the database it saves to, its fields, and what it sends. For each one you can:

  • Say who the workflow email goes to. Up to 20 addresses, separated by commas. The answer is a rule in the plan, so every later sync keeps it. A form with nobody named saves every submission and emails nobody, and the plan warns about it.
  • Choose whether each enquiry adds a CRM contact. Ticked by default when the form asks for an email address. Each enquiry adds a CRM contact.
  • Check the forms before the load. A review that names a field with no label, a form with nobody to email, a form with no spam protection, and similar faults, each with a one-click fix such as Turn on hCaptcha. The review.
  • Rebuild a form from another service as an Insites form, from a proposal you read and change before you confirm it.
  • Add past submissions for a source that keeps them only in an export, such as Squarespace.

What Verify checks, and what it does not

The CODE check compares every moved form and every email with the plan, field by field, including who each email goes to, whether it is switched on, and its sender. It fails when a form no longer sends an email it sent on the old site. Another check confirms every past submission arrived identical, and LOGS names errors a form causes on the new site, such as a missing reCAPTCHA set-up or a form on a page site search reads. The checks.

No check sends a form, and none checks an email arrives. CODE proves the form is what the plan says, not that the plan names the right people. That is why the To do list asks you to send a test from each form, and why Test a moved form safely exists.

The To do jobs for forms

JobWhen it appears
Check the forms rebuilt in the form builderAny form was rebuilt. Check who each workflow email goes to, read and switch on each autoresponder, and send a test.
Check the file upload fieldsA Webflow form asked for a file. The field uploads to an upload column of the form's table on Insites: send a test with a file.
Add back the file upload fieldsA Squarespace form asked for a file.
Check the forms that send to another serviceA Webflow form has an Action of its own.
Decide where the form from another service sendsA JotForm, HubSpot or similar form is still embedded.
Decide on spam protection for the copied formsA Siteglide form checks nothing for spam on the new site.
Add the access rules back to the copied formsA Siteglide form only some people could send had a rule that could not be copied, so anyone can send it until you add a policy on its Security tab.
Add the past submissionsA Squarespace form has submissions that only its export holds.
Set up the spam check (reCAPTCHA) on the new site's forms and Set spam protection on the formAn Insites form uses reCAPTCHA, whose keys never move. The job names each form that checks it and the page it is on: have Insites set the keys up on the new instance, with the site's domains added to them, or switch the form to hCaptcha, which needs no keys. You do not have to come back to tick the reCAPTCHA job: each time you press Check again on Verify, the tool opens every page the job names on the new instance, as a visitor would. When they all open, none shows "can't find configuration for CAPTCHA", and the new site's log has no such error, it marks the job done by the migration tool. reCAPTCHA.
Do not save the hCaptcha form in the Form BuilderA form protected by hCaptcha. The Form Builder cannot show hCaptcha yet, so saving the form there may clear the setting.
Test the CRM contact and emails of formsAn Insites v4 form added a CRM contact or sent the CRM's emails. Submit each one and check the thank-you page, the contact and the emails.
Set up the notifications of forms againAn Insites v4 form sent a notification the new instance does not have. The job names each form and what it no longer sends.
Attach the notifications to the forms that send themAn email a form sent on the old instance is not on the new one.
Set the sender of emails that choose their sender in codeAn email's From is worked out in code, so the tool left it as it was.

Every one of these sits in Before cutover, because a form has to work from its first visitor.

Changing a form after the move

A load, a nightly sync and the final sync all write the forms and emails again from the old site and the plan. So until the final sync is done, a change you make to a moved form in the form builder is written back, unless you keep it:

  1. You change a formIn the form builder, before the final sync
  2. Verify shows itA CODE difference for that form
  3. You press KeepThe new site's version is kept
  4. Every later syncLeaves that form as you made it
The diagram as a list
  1. You change a form in the form builder before the final sync.
  2. The next Verify shows a CODE difference for that form or its email.
  3. You press Keep on that difference.
  4. Every later load, nightly sync and final sync leaves that file as you made it.
  • Who the workflow email goes to: change it on the Forms step of Transform instead. The plan keeps it, so it is never written back.
  • Switching the autoresponder on: do it last, after the final sync, or press Keep on its CODE difference.
  • After cutover: the nightly sync switches itself off once the final sync or the domain move is marked done, so a change made after that stays. Copy first, then cut over.
  • Generate Form Code in the form builder replaces the old page's markup with the builder's own, so the form loses the old site's look. The builder asks first.
  • Submissions people send on the new site are never touched by a sync. A row changed on the new site after the move stops that night of the nightly sync until a person chooses, on Load, to keep the new site's rows or take the old site's.

Rolling back

A rollback deletes the forms and emails the load made and puts back any it changed. It deletes a form's database only when it is empty: a database that holds submissions sent after the load stays, so nothing a visitor sent is lost. Roll back a migration.