Migrate
Move your forms to Formward
For most form backends the move is one attribute: the URL your form posts to. Each guide below shows the snippet you have today next to the Formward version, maps the special fields, and lists the behaviour differences worth testing before you switch the live form. Your submission history, integrations and provider settings do not move by themselves; each guide says what you can bring along and what you recreate.
Migrate from Formspree
One attribute, one rename
Change formspree.io/f/ to your Formward endpoint. subject becomes _subject, and the redirect moves from Formspree's dashboard to a field or form setting.
Read guide →Migrate from Getform
One attribute
Getform became Forminit in January 2026. The action URL changes; fi- prefixed field names can stay as they are or be simplified.
Read guide →Migrate from Basin
One attribute
Change usebasin.com/f/ to your Formward endpoint. _gotcha and the email field carry over; the redirect needs a hidden field or a form setting.
Read guide →Migrate from Web3Forms
One attribute, drop the access key
Swap api.web3forms.com/submit for your endpoint and remove access_key. botcheck becomes _gotcha; subject and redirect get underscores.
Read guide →Migrate from Formcarry
One attribute, plus _next
Plain HTML forms change one URL. _next becomes _redirect, and the email field keeps working as Reply-To.
Read guide →Migrate from Formspark
One attribute, two renames
Same POST model. _email.subject becomes _subject, _honeypot becomes _gotcha, and Formward can store uploaded files itself.
Read guide →Migrate from Netlify Forms
Swap Netlify attributes for an action
Remove data-netlify and the form-name input, add an action. Forms then work on any host, and JavaScript forms need no static copy.
Read guide →Migrate from EmailJS
Swap the submit handler
Remove the SDK, public key and template IDs. The form posts to Formward, which stores the submission and sends the notification.
Read guide →Coming from somewhere else?
Any form that sends a standard POST can point at Formward. The migration reference covers the parts that are the same for every provider: special fields, JSON responses and status codes, allowed origins, and importing old submissions from CSV. If you are still deciding, the comparisons set Formward against each tool on data location, pricing and features.