Migrating in

Zero downtime by design

You are not migrating data — you are repointing where new submissions go. Until you change your form's action attribute, every submission still flows to your current provider exactly as before. The moment you swap the action, new submissions start arriving at Formcrest. There is no window where submissions can fall through the cracks.

Because of this, you can take your time: set up and test the Formcrest side fully, and only flip the action when you are happy. If you ever want to roll back, just change the action back to your old endpoint.

Step 1 — Keep your existing form's HTML

Start from the form you already have. Paste your current form's HTML and keep your fields exactly as they are — Formcrest captures every input with a name, so your existing name attributes carry over with no changes. There are no required field names to rename and no schema to declare.

<!-- Your existing form — unchanged for now -->
<form action="https://old-service.example/f/your-id" method="POST">
  <input type="email" name="email" required />
  <textarea name="message" required></textarea>
  <button type="submit">Send</button>
</form>

Step 2 — Create the equivalent Formcrest form and verify a destination

In the Formcrest dashboard, create a form to mirror this one and verify the destination email that should receive its submissions. You will get a unique endpoint URL like https://api.formcrest.com/v1/submit/<formId>. Submissions are only delivered to verified inboxes, so confirm the verification link before you go live. To route a single form to several inboxes, see Multiple recipients.

Step 3 — Swap the action and add the honeypot

Change the form's action to your Formcrest endpoint and add the hidden _honey honeypot field. That is the entire cutover.

<!-- Now pointing at Formcrest -->
<form action="https://api.formcrest.com/v1/submit/abc123" method="POST">
  <input type="email" name="email" required />
  <textarea name="message" required></textarea>

  <!-- Honeypot: leave empty. Bots fill it in and get rejected. -->
  <input type="text" name="_honey" style="display:none" tabindex="-1" autocomplete="off" />

  <button type="submit">Send</button>
</form>

For the full markup, redirect behavior, and the optional access key, see the HTML installation guide. For how the honeypot and Turnstile catch spam, see Spam protection.

After the swap

• Submit a real test through the live form and confirm it lands in your verified inbox and appears in the dashboard.
• Set your success and error redirects under the form's settings — see Form configuration.
• Once you have confirmed Formcrest is receiving everything, you can close your old account. There is no rush — leaving it open costs you nothing and keeps a safety net.

Coming from a specific service?

The steps are the same regardless of where you are coming from:

• Formcrest vs Web3Forms — feature and pricing comparison.
• Formcrest vs Formspree — feature and pricing comparison.