--- title: Which fields migrate between Gravity Forms and each form plugin url: "https://www.gravitykit.com/docs/gravitymigrate/field-support-by-form-plugin/" updated: "2026-09-11" category: GravityMigrate --- # Which fields migrate between Gravity Forms and each form plugin GravityMigrate migrates forms between Gravity Forms and seven other form plugins. Because each plugin has its own set of field types, some fields migrate in both directions, some in one direction only, and a few have no counterpart at all. This page is the reference for which is which. **Gravity Forms is required for every migration**, including one between two other plugins: the form is converted into a real Gravity Forms form on the way through. Entries never cross between form plugins, only forms do. ## How to read the table - **Both** – The field migrates into Gravity Forms and back to that plugin. - **Import only** – The plugin’s field is read into Gravity Forms, but Gravity Forms has nothing that writes one back. - **Export only** – A Gravity Forms field is written to that plugin, but the plugin has no field of that kind to read back in. - **—** – Neither direction. The field is named in the migration report and skipped. A field that migrates is not always the same type on the other side. Where a plugin has no equal, GravityMigrate writes the closest thing it does have and says so during the migration. Those conversions are listed under the table. ## Field support by plugin Gravity Forms fieldContact Form 7Fluent FormsFormidableForminatorNinja FormsWPFormsWS FormAddressExport onlyBothBothBothBothBothImport onlyCAPTCHAImport onlyBothImport onlyBothImport onlyBothBothCheckboxesBothBothBothBothBothBothBothConsentBothBothBothBothBothBothBothCredit CardImport onlyExport onlyImport onlyBothImport onlyBoth—DateBothBothBothBothBothBothBothDropdownBothBothBothBothBothBothBothEmailBothBothBothBothBothBothBothFile UploadBothBothBothBothBothBothBothHTML—BothBothBothBothBothBothHiddenBothBothBothBothBothBothBothLikert—BothImport only——Both—List—Export only—Export only—Export only—Multi SelectExport onlyExport onlyExport onlyExport onlyBothExport onlyExport onlyNameExport onlyBothBothBothBothBoth—NumberBothBothBothBothBothBothBothOption—Export only———Export only—Page Break—BothBothBoth—Both—Paragraph TextBothBothBothBothBothBothBothPasswordExport onlyBothBothBothBothBothBothPhoneBothBothBothBothBothBothBothPoll—Export only———Export only—Post Body—Both—Both—Export only—Post Category—Export only———Export only—Post Custom Field—Export only———Export only—Post Excerpt—Both———Export only—Post Image—Both———Export only—Post Tags—Export onlyImport only——Export only—Post Title—Both—Export only—Export only—Product—BothBothExport onlyBothBothBothQuantity—BothBoth—BothExport onlyBothQuiz—————Export only—Radio ButtonsBothBothBothBothBothBothBothRank——Import only——Export only—Rating—BothImport onlyBothBothBothBothRepeater—BothImport onlyBothBothBoth—Section Break—BothBothBothBothBothBothShipping—Export only——BothExport only—Signature——Import onlyBothImport onlyBothBothSingle Line TextBothBothBothBothBothBothBothSurvey—BothImport only——Export only—TimeExport onlyExport onlyBothBothExport onlyExport onlyExport onlyTotal—BothBothExport onlyBothBothBothWebsiteBothBothBothBothExport onlyBothBoth ## Fields that arrive as a different type When a Gravity Forms form is migrated to another plugin, these fields are recreated as the closest type that plugin has. Each conversion is reported on screen while you choose the forms. ### Contact Form 7 - Name becomes a text field - Address becomes a text field - Password becomes a text field - Time becomes a text field - Multi Select becomes a dropdown ### Fluent Forms - Time becomes a date field - Survey becomes a tabular grid - Poll becomes radio buttons - List becomes a repeater field - Multi Select becomes a dropdown - Option and Shipping become a multi-payment component - Credit Card becomes a payment method field - Post Category, Post Tags, and Post Custom Field each become a text field ### Formidable - Multi Select becomes a dropdown. Every other field that migrates keeps its type. ### Forminator - Total becomes a calculation field - Product becomes a currency field - List becomes a group - Post Title becomes a post data field - Multi Select becomes a dropdown ### Ninja Forms - Time becomes a text box - Website becomes a text box ### WPForms - Time becomes a date and time field - Quiz becomes radio buttons - Poll becomes radio buttons - Rank becomes radio buttons - Survey becomes radio buttons - List becomes a text field - Quantity becomes a number field - Option becomes checkboxes - Credit Card and Shipping each become a single item payment field - Post Title, Post Tags, and Post Custom Field each become a text field - Post Body and Post Excerpt each become a paragraph text field - Post Category becomes a dropdown - Post Image becomes a file upload field ### WS Form - Time becomes a date and time field - Multi Select becomes a dropdown ## Fields that cannot migrate, and why Some fields are deliberately left behind, because migrating them would produce something broken rather than something useful. - **Spam protection** – CAPTCHA, reCAPTCHA, hCaptcha, and Turnstile fields are configured with keys that live in the other plugin’s own settings. A migrated field would reject the submissions it exists to protect, so it is not written out to Contact Form 7, Formidable, or Ninja Forms. - **Credit card fields** – Gravity Forms takes payment through an add-on feed rather than a field, so a card field is read on the way in but never written back out to Formidable or Ninja Forms. - **Ninja Forms card parts** – The card number, security code, expiry, name, and ZIP are parts of one card field. They are imported as part of the whole field, never on their own, where each would be a text box collecting card details. - **Embedded forms** – Formidable’s embedded form field has no Gravity Forms counterpart, in either direction. - **Survey and signature fields** – These migrate into Gravity Forms, and writing them back out needs the Gravity Forms Survey or Signature add-on. GravityMigrate flags the requirement before the migration runs. - **Third-party fields** – WS Form’s Google address field, Formidable’s appointment field, and Fluent Forms’ Pro-only elements can only be created by the plugin or service that owns them. ## Versions this was checked against PluginVersionContact Form 76.1.4Fluent Forms6.1.14Formidable Forms6.22Forminator1.57.0Ninja Forms3.8.25.1WPForms1.10.0.2WS Form1.9.242Gravity Forms2.10.5.1 ## What migrates besides fields Along with the fields themselves, a form migration moves labels, required fields, choices and their stored values, placeholders, default values, conditional logic, notifications, and confirmations, wherever the destination plugin supports them. Contact Form 7 has no conditional logic of its own, for example, so rules are reported as they are dropped rather than silently lost. Entries, uploaded files, GravityView Views, add-on feeds, and plugin settings do not migrate between form plugins. To move those, export a GravityMigrate file and import it on the other site.