Migrate from Formcarry
Formcarry and Formtorch both accept standard HTML form submissions. Migration involves updating your endpoint URLs and any reserved field names.
What changes
| Formcarry | Formtorch | |
|---|---|---|
| Endpoint format | https://formcarry.com/s/YOUR_ID | https://formtorch.com/f/YOUR_ID |
| Redirect field | _redirect | _redirect (same) |
| Honeypot field | _gotcha | _honeypot |
| Form name field | _formname | _formName |
| Dashboard | formcarry.com | app.formtorch.com |
| Spam protection | reCAPTCHA / honeypot | TorchWarden (automatic) |
Migration steps
Create your forms in Formtorch
Sign in to app.formtorch.com . Create a project, then one form for each Formcarry form you’re migrating. Copy the endpoint URLs.
Update endpoint URLs
<!-- Before -->
<form action="https://formcarry.com/s/YOUR_FORMCARRY_ID" method="POST">
<!-- After -->
<form action="https://formtorch.com/f/YOUR_FORM_ID" method="POST"></form>
</form>Update reserved field names
The _redirect field works the same. Update the honeypot field name if you were using _gotcha:
<!-- Before -->
<input type="text" name="_gotcha" style="display:none" />
<!-- After -->
<input
type="text"
name="_honeypot"
style="display:none"
tabindex="-1"
autocomplete="off"
/>If you used _formname to label submissions, Formtorch uses _formName (camelCase):
<!-- Before -->
<input type="hidden" name="_formname" value="Contact Form" />
<!-- After -->
<input type="hidden" name="_formName" value="Contact Form" />Remove reCAPTCHA
Formtorch’s TorchWarden filter runs automatically on every submission. No reCAPTCHA setup or tokens are needed. Remove any reCAPTCHA scripts and response fields from your forms.
Configure notifications
In each form’s Settings → Notifications, add your email. Unlike Formcarry’s account-level notification address, Formtorch lets you set different recipients per form.
Export your Formcarry data
Download a CSV from your Formcarry dashboard before switching. Existing submissions cannot be imported into Formtorch.
Go live
Send a test submission to verify your new endpoint is working, then update your live forms.
Key differences
Endpoint path: Formcarry uses /s/ in the path; Formtorch uses /f/. Make sure to update the full URL, not just the ID.
Spam protection: Formtorch’s TorchWarden provides automatic, always-on spam filtering. No configuration required.
Webhooks: Formtorch webhooks include a cryptographic signature for verification. Formcarry did not provide this. See Webhook Processing.
Keep both endpoints live simultaneously during testing. Formcarry and Formtorch can run in parallel until you confirm everything is working.
Learn more
- HTML Quickstart — full integration guide for HTML forms
- Email Notifications — per-form recipients and verification
- Spam Protection — TorchWarden signal reference
- Custom Redirects — using the
_redirectfield