UAU Ready
Description
The GravityImport – Import entries from a CSV add-on imports records in bulk from CSV files directly into Gravity Forms forms, with field mapping, conditional rules to filter which rows are imported, and automatic validation that blocks invalid entries. Within the GravityKit ecosystem, the component supports all Gravity Forms field types, updates existing entries via the Entry ID column, and exports failed rows to a separate CSV for review and re-import.
Key Features
- Complete field mapping
Covers all Gravity Forms field types, as well as entry metadata. - Update via Entry ID
Includes an Entry ID column in the CSV to overwrite existing entries instead of duplicating them. - Conditional import rules
Filters which CSV rows will be imported based on configurable conditions. - Automatic data validation
Blocks incomplete or invalid entries during the process, keeping the database clean. - Failed row export
Generates a CSV with only the rejected records for quick review and correction.
Benefits of GravityImport – Import entries from a CSV
- Large-scale import
Processes CSVs with thousands of entries without freezing the WordPress dashboard. - Quick form creation
Automatically generates a new form from the header of the uploaded CSV file itself. - Compatibility with Gravity Forms add-ons
Runs feeds from compatible add-ons during the import, keeping automations active. - Support for uploaded files
Imports files referenced in Gravity Forms File Upload fields.
Who Is It For?
- Teams that need to migrate entries between Gravity Forms forms or consolidate submission databases.
- Agencies and administrators who manage large volumes of leads, registrations, or orders in external spreadsheets.
- Professionals who work with exports from other systems and want to reuse that data in WordPress forms.
For those who operate Gravity Forms at scale, the component eliminates the friction of populating forms without manual submission, connecting external spreadsheets, CRM exports, and entry backups to a single import flow in the admin. Running compatible feeds during the import keeps notification, payment, and marketing integrations working normally, and the failed-rows CSV gives you immediate control over what was left out.
Frequently asked questions
Is GravityImport – Import entries from a CSV GPL-licensed?
Yes. GravityImport – Import entries from a CSV is distributed under the GPL (GNU General Public License). You may legally use, modify and redistribute it on as many sites as you want.
Can I use GravityImport – Import entries from a CSV on multiple sites?
Yes. You can use GravityImport – Import entries from a CSV on multiple sites. The number of sites connected to Ultrapack Auto Updater is limited by your plan.
How much does GravityImport – Import entries from a CSV cost at Ultrapack?
GravityImport – Import entries from a CSV costs US$2.99 as a single purchase, and it is also included in the subscription plans starting at US$12/mo (VIP I).
Does GravityImport – Import entries from a CSV include updates?
Yes. The current version of GravityImport – Import entries from a CSV is 2.12.2, published at Ultrapack on Sep 24, 2026. Subscribers update straight from the WordPress dashboard with UAU (Ultrapack Auto Updater).
Is GravityImport – Import entries from a CSV scanned before publication?
Yes. Every version of GravityImport – Import entries from a CSV goes through a malware scan (ClamAV and YARA rules, at UltraHub) before it is published.
What are the requirements for the plugin GravityImport – Import entries from a CSV?
Requires WordPress 6.2 or higher and PHP 7.4.0 or higher. Tested up to WordPress 7.1.1.
What changed in this version
Version 2.12.2
- This release fixes issues with importing Consent fields.
- Note: GravityImport now requires WordPress 6.5 or newer.
- Issues when importing Consent fields
- The form's consent text could be overwritten, and imported entries linked to the wrong version of the terms
- Consent terms containing `%` or `_` were saved as a new version on every import.
- 🔧 Updated
- [Foundation]
Version 2.12.1
- This release fixes importing into Multiple Choice and Image Choice fields, and into file upload fields on Gravity Forms 3.1.2 or newer.
- Files were not imported into file upload fields on Gravity Forms 3.1.2 or newer, which rejected every row with "The file is not valid."
- Multiple Choice and Image Choice fields set to "Select One" could not be mapped as a single column — the mapping step offered only their individual choices, and the column was dropped while the import still reported success.
- Existing mappings to an individual choice are now rejected with a message naming the field to map instead, or skipped with a warning when an import profile runs from the command line.
- Multiple Choice and Image Choice fields that allow more than one selection stored cell values such as `1`, `yes`, `0` or `no` as the selected choice instead of treating them as Checkbox columns do.
- `1`, `true` or `yes` selects the choice, while `0`, `false`, `no` or an empty cell leaves it unselected
- "(Any Choice)" is available as a mapping target
- Rows that don't meet an "Exact Number" or "Range" selection limit are reported as errors.
- Row errors showed HTML character codes such as `<` and `&` in the import log and the failed records download, including around formatted text in Gravity Forms messages.
- 🔧 Updated
- [Foundation]
Version 2.12.0
- This release gives clearer reasons when rows fail to import, and fixes file upload imports on Gravity Forms 3.0+, a fatal multi-file upload field error, and compatibility issues with GravityView and WordPress 6.7.
- ✨ Improved
- Rows rejected by a form-level validation failure now report the actual cause instead of "Failed validation: Unknown" — including when Gravity Forms is blocking submissions while its database upgrade is pending (common on freshly cloned staging sites), or when an anti-spam or CAPTCHA plugin rejects the submission.
- Entries imported with an Entry Status column using different capitalization (e.g., `Active`) could not be opened or edited in [GravityView]( the standard statuses (`active`, `spam`, `trash`) are now saved in the lowercase form Gravity Forms expects.
- Resolved a "translation loading was triggered too early" notice on WordPress 6.7+.
- Imports with a file upload column failed on Gravity Forms 3.0+ — downloaded files are now given a temporary name matching the uploaded file's extension, which Gravity Forms 3.0+ requires.
- A row rejected by a multi-file upload field caused a fatal error on PHP 8; on PHP 7.4 the error named the field but left the reason blank.
- 🔧 Updated
- [Foundation]
Version 2.11.3
- This release fixes imports to forms that are connected to a Pod through the Pods Gravity Forms add-on.
- Imports to forms mapped to a Pod via the Pods Gravity Forms add-on now import reliably: every row is saved to the Pod, and a row that leaves a required Pods field empty no longer stops the whole import.
- A feed that errors while importing a row no longer stops the whole import; the row is recorded as an error and the import continues.
- 🔧 Updated
- [Foundation]
Version 2.11.2
- This hotfix resolves an issue affecting the Map Fields step when importing large CSV files.
- The Map Fields step could appear blank when importing very large CSV files.
- 🔧 Updated
- [Foundation]
Release notes published by the developer.
How to install
Automatic updates: this item is updated by the Ultrapack Auto Updater. With it installed, the new version shows up in your dashboard like any other WordPress update (how to set it up).
- Download the file
gravityview-importer.zip. - In the WordPress dashboard, go to Plugins > Add New > Upload Plugin.
- Select the file
gravityview-importer.zipand click Install Now. - Click Activate.
Requirements: Requires WordPress 6.2 or higher and PHP 7.4.0 or higher. Tested up to WordPress 7.1.1.
Stuck on a step? Open a ticket telling us which one you stopped at.
