Migrate from Web3Forms to Formboost
A practical, step-by-step guide to moving your forms over — most teams finish in under 30 minutes.
1. Your Existing Web3Forms Implementation
A typical Web3Forms form looks like this:
<form action="https://api.web3forms.com/submit" method="POST">
<input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
<input type="email" name="email" required />
<textarea name="message"></textarea>
<button type="submit">Send</button>
</form>2. The Formboost Implementation
Create a form endpoint in the Formboost dashboard, then update your form's action URL:
<form action="https://formboost.app/f/YOUR_ENDPOINT_ID" method="POST">
<input type="email" name="email" required />
<textarea name="message"></textarea>
<button type="submit">Send</button>
</form>3–4. Endpoint & Configuration Changes
Web3Forms posts to one shared endpoint, https://api.web3forms.com/submit, and identifies your form with a hidden `access_key` input — Formboost gives each form its own endpoint URL instead, so the action changes and the access_key input is deleted
Remove Web3Forms' hidden helper fields (`access_key`, and `subject`/`from_name` if you set them); the equivalents are configured per form in the Formboost dashboard
Formboost keeps the same `_redirect` idea: point it at your thank-you page and an HTML form submit will land there
If you relied on a Pro webhook, recreate it as a Formboost webhook — note that custom webhooks start on Formboost's Starter plan, while Slack, Discord and Telegram are available on Free
hCaptcha or reCAPTCHA markup can come out: Formboost screens submissions server-side, and the honeypot is handled for you
Formboost does not accept file uploads yet, so a Web3Forms Pro form with attachments has no direct equivalent
Send one real submission through the new endpoint before deleting the old access key
5–7. Feature Mapping, Testing & Deployment
Feature Mapping
Review the full comparison to confirm every Web3Forms feature you use has a Formboost equivalent before cutting over.
Testing
Submit a real test entry to your new Formboost endpoint and confirm it arrives with email/webhook/Slack notifications intact before removing the old endpoint.
Deployment
Deploy the updated form action URL, monitor the Formboost dashboard for the first live submissions, then decommission the old Web3Forms form.
Migration FAQ
Common questions about moving from Web3Forms to Formboost
Will I lose my Web3Forms submission history?
Formboost only stores submissions that come in after you switch. Export your existing history from Web3Forms first if you need to keep it.
Do I need to change my form's HTML structure?
No. Only the form's action URL (or the endpoint your JavaScript posts to) needs to change. Field names, validation, and styling stay exactly the same.
Can I test before fully switching over?
Yes. Both endpoints can run side by side — point a staging form or a single test submission at Formboost first, confirm it arrives correctly, then update production.
What if I use a feature Formboost doesn't have yet?
Reach out to support before migrating — most core form backend features (webhooks, spam protection, file uploads, integrations) are covered, but it's worth confirming for anything specialized.
Start your migration today
Create your Formboost account and set up your first endpoint in minutes.