# Migration

Migrate a form from Formspree, Web3Forms, or Formcarry to Form Plume in five steps, with a temporary bridge that copies submissions to your old provider.

Do you already have a form running on Formspree, Web3Forms, or Formcarry? Form Plume gives
you an easy way to switch while keeping your current provider as a temporary
safety net. **You can verify that Form Plume works for your real form before you
fully commit, without putting new leads at unnecessary risk.**

- **Formspree**
- **Web3Forms**
- **Formcarry**

> For 14 days, Form Plume receives each accepted submission and sends a copy to
> your current provider. You can stop the bridge at any time.

## 1. Create your Form Plume form

[Create your Form Plume account](/signup), then create your first form. The
form's Setup page gives you a new endpoint:

```text
https://api.formplume.com/f/{public_slug}
```

This is the URL your website will use after the migration is ready.

## 2. Open the Migration page

On the Setup page, you will see a card asking whether you are migrating from
another provider. Select **Yes, set it up**.
You can also open it directly from **Settings → Migration**.

## 3. Connect your current provider

Choose the service your form uses today, then enter the requested value.

### Formspree

Paste your existing endpoint or just the form ID:

```text
https://formspree.io/f/xkD2Abcd
```

### Web3Forms

Paste the `access_key` currently used by your form. Form Plume encrypts it and
does not show it again after setup.

### Formcarry

Paste your existing endpoint or just the form ID:

```text
https://formcarry.com/s/abc123
```

Select **Start safe migration** when you are done.

## 4. Point your form to Form Plume

Replace the current provider URL with your new Form Plume endpoint. Your field
names, labels, and submit button can stay the same.

### From Formspree

```diff
- <form action="https://formspree.io/f/xkD2Abcd" method="POST">
+ <form action="https://api.formplume.com/f/{public_slug}" method="POST">
```

### From Web3Forms

Change the request URL and remove the hidden `access_key` input. Form Plume no
longer needs it in the public form.

```diff
- <form action="https://api.web3forms.com/submit" method="POST">
-   <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY">
+ <form action="https://api.formplume.com/f/{public_slug}" method="POST">
```

### From Formcarry

```diff
- <form action="https://formcarry.com/s/abc123" method="POST">
+ <form action="https://api.formplume.com/f/{public_slug}" method="POST">
```

Deploy the website as you normally would.

## 5. Send a real test

Submit the form from the published website. Confirm that:

- ✅ The visitor sees the correct success page or message.
- 📥 The submission appears in the Form Plume inbox.
- ✉️ Your Form Plume email notification arrives.
- ⚡ Any Form Plume integrations you configured trigger successfully.
- 🔁 A copy appears in your previous provider.

The Migration page shows when the last copy was delivered and when the bridge
will expire. If the previous provider is temporarily unavailable, Form Plume
retries the copy in the background.

## What happens during the 14 days

Form Plume becomes the main destination for the form. It stores the submission,
runs spam checks, and sends your Form Plume notifications. The migration bridge
then copies the ordinary form fields to your previous provider.

This setup is intentionally limited:

- It can send only to Formspree, Web3Forms, or Formcarry.
- The destination host is fixed by Form Plume, not supplied as an arbitrary URL.
- Suspected spam is quarantined instead of being copied.
- The bridge stops automatically after 14 days.
- Form Plume never deletes or changes the form in your old account.

When you are comfortable with the new setup, select **Stop forwarding** in
**Settings → Migration**. If you need to roll back, restore the old form action
and deploy the website again.

## A few things to check

1. **You may receive duplicate notifications.**

   Both services can send notifications during the transition. That is
   expected. You can disable the old notification after Form Plume's delivery
   is confirmed.

2. **Configure CAPTCHA in Form Plume.**

   CAPTCHA settings do not transfer between providers. Configure yours under
   Spam Protection and test the live form. See
   [Spam Protection](/docs/spam-protection) for the supported options.

3. **Files are not copied back.**

   Files received by Form Plume stay in Form Plume. They are not uploaded again
   to the previous provider. If your form accepts attachments, follow the
   [File Uploads guide](/docs/forms/file-uploads) and test one real file.

4. **Old submissions are not imported.**

   The bridge covers new submissions during the transition. Your previous inbox
   stays where it is, so [export](/docs/submissions/export) anything you want to
   keep before closing that account.

Ready to try it? [Create your first Form Plume form](/signup) and follow the five
steps above.