Gravity Import

Gravity Import is built for moving structured data into WordPress without relying on manual entry for every record. Its clearest use case is adding data to Gravity Forms, while the broader feature set covers imports from CSV, XML, and JSON files, field matching, recurring jobs, and reporting when something goes wrong.

Importing into forms

The plugin addresses a practical admin task: taking information that already exists in a file and placing it into the fields used by a WordPress site. That is useful for site owners managing lists, records, or other form-based data that would be slow and error-prone to recreate by hand. Support for three common file formats gives the import process some flexibility instead of tying it to one export source.

Gravity Import is aimed at developers, site owners, and content managers rather than only at people comfortable writing import scripts. The user interface is described as suitable for beginners as well as advanced users, so the main appeal is a guided import workflow rather than a code-first tool.

Mapping and templates

Field mapping is the feature that determines how useful an importer becomes in day-to-day work. Gravity Import lets you match incoming fields to existing WordPress fields, giving you a way to align a file’s column names with the structure already in use on the site. That matters when the source system and the WordPress form do not use identical labels.

Customisable import templates support repeat jobs. A template can preserve the choices made for a recurring task, reducing the amount of setup required each time a similar file arrives. This is more valuable for regular data maintenance than for a single small import, where manual configuration may be quicker than preparing a reusable workflow.

Scheduled updates and reports

Scheduled imports extend the plugin beyond one-off data transfers. Automatic updates at specified intervals suit sites that receive refreshed source files or need WordPress data kept current on a timetable. The scheduling feature is particularly relevant when an administrator should not have to start every import by hand.

Built-in error handling produces reports about issues encountered during an import. Those reports give an administrator a defined place to look when records do not transfer as expected, instead of leaving a partially completed job without explanation. The available description does not specify the report format or the range of errors covered, so its practical value will depend on how much detail each report provides.

Where it falls short

The feature list is broad but does not explain the depth of its data handling. There is no stated detail about transformations, duplicate handling, validation rules, or how complex relationships between imported fields are managed. Sites with demanding migration rules should not assume that file support and field mapping alone will replace a purpose-built migration process.

Scheduled imports also introduce an operational responsibility: recurring jobs need suitable source files and occasional review when the source structure changes. Compatibility with Elementor and WPBakery is useful context for sites using those builders, but the listing does not describe which builder data can be imported or how that integration works. The plugin therefore looks strongest for structured, repeatable imports rather than as a universal content migration system.

Who it suits

Gravity Import fits a WordPress administrator who regularly receives structured data and needs it placed into Gravity Forms or existing WordPress fields. It is a sensible candidate for teams that value reusable mappings, scheduled updates, and an error report over repeated manual entry.

It is less clearly suited to a migration with complicated data relationships or requirements that go beyond the advertised file formats and field matching. For routine imports with a predictable structure, though, the combination of mapping, templates, scheduling, and reporting covers the main stages of the job in one WordPress-focused workflow.