FNJ / Reconnect forms
Make forms work after an HTML export
Audit form actions, connect your own submission service and verify delivery, validation and error feedback after moving hosts.
Start with the outcome
A form whose submissions reach the intended inbox or system from the new website origin. The exported fields are the interface; message delivery, abuse controls and stored submissions belong to the service you connect.
Choose your original builder below. The task is shared, but the dependencies, URL structure and missing features to check depend on the platform. Each guide includes a reviewed platform note, a full procedure and a prompt you can adapt for your agent.
Choose your website builder
Framer / Reconnect forms
Make forms work after an HTML export
Check Framer contact forms and their confirmation behavior after the HTML converter removes runtime code. A form can still look correct while its submit handler no longer exists. Reconnect delivery to a service you own and test from the deployed domain, including the success state and a deliberately rejected submission.
Read the guide →Webflow / Reconnect forms
Make forms work after an HTML export
Inspect Webflow's generated form wrappers, endpoint and success/error elements together. The copied markup is not Webflow's form inbox, and its handler may depend on original scripts. Test your replacement from the new origin and preserve field names only when they match the receiving service's documented format.
Read the guide →Gamma / Reconnect forms
Make forms work after an HTML export
A Gamma card may embed a third-party contact or signup tool rather than a local form. Identify whether the input lives inside an iframe before editing the surrounding HTML. Configure delivery and allowed origins in that provider, then test the embedded tool on the exported page as well as its standalone URL.
Read the guide →systeme.io / Reconnect forms
Make forms work after an HTML export
An opt-in form is part of a systeme.io automation flow. Test whether the contact reaches the intended list and whether the agreed follow-up runs, not only whether a thank-you page opens. Keep checkout and member authentication with suitable services; never reconstruct those controls from public HTML alone.
Read the guide →Carrd / Reconnect forms
Make forms work after an HTML export
Audit Carrd contact forms and embedded booking tools independently. Some inputs submit directly to an external provider; others rely on page scripts. Keep or replace that service intentionally, test the deployed origin, and confirm the inbox receives your synthetic submission rather than relying on the on-page success message.
Read the guide →Duda / Reconnect forms
Make forms work after an HTML export
Duda contact and appointment widgets need a receiving service even when their fields are visible in the export. Record whether each widget submits to Duda or another provider. Test a synthetic contact and booking on the preview, including validation and confirmation, before replacing the original site's customer flow.
Read the guide →Elementor / Reconnect forms
Make forms work after an HTML export
Elementor and WordPress form plugins often call WordPress endpoints and may use request tokens tied to the original site. Inspect those calls before deployment. Retain a supported backend or replace it deliberately; copied PHP plugin settings, logins and form delivery do not run on static hosting.
Read the guide →Squarespace / Reconnect forms
Make forms work after an HTML export
Squarespace forms, scheduling and commerce have different receiving systems. Inventory them separately so a working booking link is not mistaken for a migrated form inbox. Verify a test submission and a booking through the service you intend to keep, using the new origin and its final success destination.
Read the guide →Strikingly / Reconnect forms
Make forms work after an HTML export
Audit Strikingly contact, store and member widgets independently. A static contact layout is not a submissions inbox, and a login-looking section does not enforce permissions. Test the intended receiving service and preserve working store destinations until a complete replacement flow has been demonstrated.
Read the guide →Tilda / Reconnect forms
Make forms work after an HTML export
Tilda forms can connect to CRM or notification integrations that do not transfer with their visual fields. Record field names, original receiver and success behavior before replacing them. Submit a synthetic lead on the deployed domain and confirm that the chosen CRM or inbox receives it exactly once.
Read the guide →Weebly / Reconnect forms
Make forms work after an HTML export
Weebly contact delivery and Square commerce should be tested as separate flows. A captured product page cannot process inventory or orders by itself. Keep purchase actions with a supported commerce service, and confirm both form receipt and the actual checkout destination from the exported preview.
Read the guide →Wix / Reconnect forms
Make forms work after an HTML export
Wix Forms, bookings and store actions rely on hosted systems. A copied input or booking button is not a migrated backend. Inspect every action and choose retained or replacement services; if key controls are missing from the capture, rebuild them before claiming the form or purchase journey is usable.
Read the guide →What a completed task should demonstrate
- A test submission reaches the intended destination.
- Invalid fields and failed requests produce useful feedback.
- The browser bundle contains no server-side credentials.