0 items
Sign in
Buy

Docs

Best practices to follow when moving data using GravityMigrate

Estimated reading: 2 minutes

Updated on September 10, 2026

GravityMigrate makes a complex process, the exporting and importing of Gravity Forms data, extremely simple. While we’ve built GravityMigrate to ensure compatibility with a range of website configurations and data types, following the below “best practices” will help ensure a smooth migration, and reduce the chance of error.

  • Ensure that you’re running Gravity Forms 2.5 or later: GravityMigrate requires at least Gravity Forms 2.5 and is not compatible with earlier versions.
  • Ensure you’re running the latest version of GravityMigrate on both your old and new website: Keeping GravityMigrate up to date will ensure that you benefit from the latest fixes and improvements to the plugin.
  • Ensure you have the required plugins installed and activated on your new site: For example, if you’re migrating Views, you should ensure that GravityView is installed and activated on your new site.
  • Ensure you’re running the same plugin versions on each site: While not critical, making sure your old and new websites are running similar plugin versions will help reduce the likelihood of issues arising during migration.
  • Import a GravityMigrate file, or bring forms in from a form plugin on the same site: The wizard’s Source step takes a ZIP file that GravityMigrate created on another site. It can also recreate forms from Contact Form 7, Fluent Forms, Formidable Forms, Forminator, Ninja Forms, WPForms or WS Form, when that plugin is active on the site you are importing into. A CSV of entries exported from Gravity Forms is not a migration file. To bring entries in from a CSV, use GravityImport.
  • Double and triple check your data before running the import: Once an import has finished, it cannot be undone or reversed, that’s why it’s important to check you have the right data before importing.
  • Give a large migration the time it needs: A migration with many entries or uploaded files can take a while, and the wizard shows its progress as it goes. On a site that can run background jobs, the migration keeps going after you close the tab. A notice then follows you around the admin screens until it finishes. On a site that cannot, keep the page open until the wizard reaches its Done step. If a migration stops partway, the same migration runs from the command line: Migrating Gravity Forms from the command line with WP-CLI.

Was this page helpful?