How to migrate from Fluent Forms to Gravity Forms without rebuilding your forms

Fluent Forms has a built-in migrator that pulls forms in from Gravity Forms, WPForms, Ninja Forms, and a few others. Going the other way, from Fluent Forms to Gravity Forms, has meant building each form again by hand and bringing the entries across in a CSV file.

GravityMigrate does that rebuild for you. It reads the forms on your site, recreates each one in Gravity Forms with its fields, conditional logic, confirmation, and email notifications, and shows you a report of what changed before it writes anything. I’ll walk you through it in two parts: the forms first, then the entries. Let’s dive in!

What you’ll need

• Gravity Forms – the form plugin you’re moving to. GravityMigrate needs it active for every migration.
• GravityMigrate – reads your Fluent Forms forms and recreates them in Gravity Forms.
• Fluent Forms, free or Pro, still active on the same site – GravityMigrate reads the forms straight from it.
• GravityImport (optional) – brings your old entries across from a CSV file. (Not sure which you need? Here’s how GravityImport and GravityMigrate differ.)

Why move from Fluent Forms to Gravity Forms?

Fluent Forms is a capable plugin. Its free version saves your entries, every paid plan includes all of its features, and it sells lifetime licenses, so for many sites it costs less. If it covers what your forms do, there’s no reason to move. The case for Gravity Forms comes down to what’s built around it:

• A large add-on ecosystem – official and certified third-party add-ons (here are the best ones), Gravity Flow for review workflows, and GravityKit’s add-ons for displaying entries on the front end.
• Room for developers – a REST API, plus hooks and filters documented in the Gravity Forms docs.
• Accessible forms – Gravity Forms is built to meet WCAG 2.1 AA.

For a side-by-side look at Fluent Forms vs Gravity Forms, Gravity Forms has published its own comparison. If you’ve decided, here’s how to move.

Step 1: Install GravityMigrate on the site with your Fluent Forms forms

GravityMigrate reads your forms directly from Fluent Forms, so you don’t need to export anything first. That also means it has to run on the site where your Fluent Forms forms live. It works with the free version of Fluent Forms and with Fluent Forms Pro.

Download GravityMigrate from your GravityKit account, then upload and activate it like any other plugin (here’s how). Before you move on, check that Gravity Forms and Fluent Forms are both active on the same site.

Step 2: Migrate your Fluent Forms forms into Gravity Forms

In your WordPress dashboard, hover over GravityKit and click GravityMigrate. The wizard first asks which direction you’re going. Click Import into Gravity Forms.

On the Source step, the right-hand column lists every form plugin on your site and how many forms each one holds. Click Fluent Forms.

Step 3: Pick your forms and check the report

The Choose Forms step shows a card for each of your Fluent Forms forms. Tick the ones you want to move, or click Select all to bring every form across in one run.

Not every part of a Fluent Forms form has an exact match in Gravity Forms, so before anything is written, each card tells you what’s going to happen. A card can show up to three lists, and each one only appears when it has something to say:

• Won’t migrate – fields with no Gravity Forms counterpart. The rest of the form still migrates.
• Modifications – changes made on the way across. In the booking form below, a date field that also collected a time comes across as a Date field, and the “Catering team” email will send for every entry until you rebuild its rules.
• Before you use the form – setup you’ll need to do in Gravity Forms before the form goes live.

For the full picture, click Show what happens to each field. The table has one row per field: its name in Fluent Forms, what it becomes in Gravity Forms, and what happens to it.

Pro tipThe Fluent Forms reference page lists what happens to every Fluent Forms field type, and Migrating forms from another form plugin covers each step of the wizard.

Step 4: Run the migration

Click Continue. The Confirm step lists the forms you picked and where they’re coming from. Click the import button, which shows how many forms you picked (for example, Import 1 form).

When it’s done, you’ll see Import complete, with each new form listed under What was added, linked to its page in Gravity Forms. Your confirmations and notifications come across with every form. If part of either couldn’t be rebuilt, it’s listed under that form. Your Fluent Forms forms stay exactly where they were, so you can compare old and new side by side.

What changes when a Fluent Forms form moves to Gravity Forms

Every Fluent Forms field type has a Gravity Forms counterpart, so most of a form maps straight across with its conditional logic, calculations, confirmation, and email notifications. Smart codes become Gravity Forms merge tags. Here are the main changes to look out for:

• Changed fields – a date field that also collects a time keeps only the date, and containers and accordions become Section fields, with every field inside them kept.
• Spam protection – reCAPTCHA, hCaptcha, and Turnstile fields come across, but you’ll need to add your CAPTCHA keys in Gravity Forms (more on stopping Gravity Forms spam).
• Add-ons – rating, Net Promoter Score, and Checkable Grid fields need the Gravity Forms Survey Add-On (here’s how to build surveys with it), and payment fields need a payment add-on such as Stripe or PayPal.

For every Fluent Forms field type and what it becomes, see the Fluent Forms reference page.

Pro tipCheck any email that only goes out for certain answers, such as when a box is ticked. GravityMigrate doesn’t bring those send conditions across, so the email sends after every entry until you turn on conditional logic for the notification in Gravity Forms and rebuild the rule (see Gravity Forms’ guide to notifications). The report names each email affected.

Step 5: Export your Fluent Forms entries and import them with GravityImport

GravityMigrate moves the form. Your entries stay in Fluent Forms until you export them, and bringing them across needs GravityImport, which imports the CSV file into the form you just created.

Export your entries from Fluent Forms

The free version of Fluent Forms can export entries:

1. Hover over Fluent Forms and click Forms.
2. Hover over your form and click Entries.
3. Click Export, then Export as CSV.
4. In the Select fields for export window, click Export to save every entry as a CSV file.

The CSV has a column for each field, plus entry_id, created_at, and entry_status columns at the end. Fluent Forms puts each person’s whole name in one column, while Gravity Forms keeps first and last names in separate parts of its Name field. Before you import, open the CSV in a spreadsheet and split the Name column into first name and last name columns.

For more on filtering entries before you export, see Fluent Forms’ guide to managing entries.

Import them with GravityImport

1. Install and activate GravityImport.
2. Hover over Forms, click Import/Export, and open the Import Entries tab.
3. Upload your CSV file.
4. When GravityImport asks where to import the entries, click An Existing Form and pick the form GravityMigrate just created.
5. Map each column to a field on that form (here’s how mapping works). Map the first and last name columns to First and Last. A checkbox column holds every ticked choice, separated by commas, so map it to (Any Choice). To keep the original submission dates, map created_at to Entry Date, and untick entry_id and entry_status.
6. Click Continue With Import, review the options on the Configure step, then click Continue With Import again.

Pro tipFluent Forms saves a date field’s date and time together, such as 12/19/2026 05:00 PM, so GravityImport marks the column “Date Not Recognized.” Click the gear icon next to it, choose Custom Format, and enter %M/%D/%Y^. The live preview then shows the date, which is all a Gravity Forms Date field stores. For other date formats, see formatting dates for Gravity Forms.

Our guide to importing entries into Gravity Forms covers every import option in detail.

Step 6: Swap the form on your pages and retire Fluent Forms

Last, point your pages at the new forms. Edit each page that shows a Fluent Forms form, remove its block or shortcode, and add the Gravity Forms Form block in its place. Then pick your new form in the block settings. Our guide to embedding a Gravity Forms form covers the other ways to add it.

Submit a test entry to make sure your notifications arrive. Once your entries are safely across, you can deactivate Fluent Forms.

Pro tipMoving to a new site as well? Run the migration on the old site first, while Fluent Forms is still there to read from. Then move your whole Gravity Forms setup, forms and entries included, to the new site with a GravityMigrate file. Read Getting started with GravityMigrate for the full walkthrough.

Frequently asked questions

Ready to switch?

GravityMigrate turns a form-by-form rebuild into one guided migration, and the report tells you what changed before anything is written. It also works with Ninja Forms, WPForms, Formidable Forms, Contact Form 7, Forminator, and WS Form, if you have forms in more than one plugin.

Get GravityMigrate, or try the GravityMigrate demo to see it before you install anything.