Does GravityImport support importing Nested Form fields?
Short answer #
No. GravityImport doesn’t import Nested Form fields from a CSV. The structure of nested forms — where each parent entry has multiple child entries on a separate form — doesn’t fit cleanly into the flat row-and-column shape of a CSV file. Adding it is on our roadmap, but for now there’s almost always a better tool for the underlying job.
What you’re trying to do → what to use #
“I’m moving a Gravity Forms setup from one site to another, and it has Nested Form fields”
Use GravityMigrate. GravityMigrate is built for site-to-site transfers of Gravity Forms data, and Nested Forms is one of the third-party add-ons it explicitly supports. When you bundle your source site into a GravityMigrate ZIP and import it on the destination, the parent forms, child forms, and the parent/child entry relationships all carry across — no CSV mapping required.
This is the right tool for staging-to-production deploys, domain moves, host migrations, and demo-to-live workflows. For a fuller side-by-side, see GravityImport vs GravityMigrate: which one do you need?.
“I want to display Nested Form data on the front end of my site”
Use GravityView. GravityView integrates with GP Nested Forms so you can display child entries inline on a parent entry View. See Does GravityView support GP Nested Forms? for a working demo.
“I have CSV data outside Gravity Forms that I want to load as nested entries”
There’s no supported path for this today. If you have a one-off case with a small number of parent entries, the most reliable route is to recreate the relationships manually in the Gravity Forms admin after importing the child entries with GravityImport. For larger jobs, contact support — we’d rather hear about your specific use case than have you build something fragile.
Why GravityImport can’t do this directly #
Nested Forms creates a parent-child relationship between two separate forms — not a multi-value field on a single form. A CSV row represents one flat record. Importing a “Nested Form field” cleanly would require GravityImport to detect that a column contains structured sub-records, parse each sub-record’s columns, create separate entries on the child form, and link those child IDs back to the parent. That’s a sizeable feature on its own — and it’s something the tools above (GravityMigrate for migrations, GravityView for display) already handle natively.
