Migrating from Formspree to Formhook: the ten-minute guide

The best thing about the form-backend category is that switching providers is trivial by design: your site's only integration point is one URL. Here's the complete migration, including the parts people forget.

(Why migrate at all? The honest comparison - pricing, retention, EU hosting - lives on the Formhook vs Formspree page. This guide assumes you've decided.)

Step 1: export your existing submissions

If you're on a paid Formspree plan, export your submission history first - per their pricing page, export is included from the Personal plan up. Check your form's submissions view for the export option and download everything before touching anything else. If you're on their free plan, copy anything you need manually; their free tier is positioned for testing, so ideally there's little production data in it.

Keep this export regardless of where you land - provider-agnostic backups of lead data are just good hygiene.

Step 2: create the Formhook form

Sign up, create a form, and copy its key. Two settings to configure while you're there:

• CORS allowlist - add your site's domain(s), including the www variant if you serve both.
• Turnstile - if you had CAPTCHA-style protection before, enable Turnstile now so protection is continuous through the switch. Honeypot and rate limiting are already on.

Step 3: the one-line change

Field names don't need to change - both services accept standard form-encoded POSTs, and Formhook also takes JSON and multipart. If you used fetch/AJAX, the same one-line swap applies to the URL in your code.

Things to grep for so you catch every instance: the old URL in components, environment variables like FORM_ENDPOINT, and any hardcoded endpoint in per-page templates. Multi-form sites: Formhook's free tier includes multiple forms, so map each old form to its own key rather than merging - per-form notifications and settings stay clean that way.

Step 4: test from the deployed site

Deploy, then submit a real test from the production URL, not localhost - that's the only place CORS, DNS, and TLS are all exercised together. Confirm three things: the success state shows in the browser, the submission appears in your Formhook dashboard, and the notification arrives on your device. Run the full pre-launch checklist while you're at it.

Step 5: decommission the old form

Leave the old Formspree form live for a few days as a safety net, then disable it once you've confirmed submissions are flowing to Formhook. Keep your export archived. That's the entire migration - one attribute, a couple of settings, and a test. The reason it's this easy is the same reason leaving any form backend is easy: your site depends on a single URL, not a lock-in.