UAU Ready
Description
The GravityMigrate addon – Migrate Your Gravity Forms Data transfers licenses, settings, entries, and forms from Gravity Forms between WordPress installations, automating domain switching without manual reactivations. Aimed at administrators who need to migrate projects between staging and production, the extension preserves form IDs, maps upload paths, and keeps integrations active during the complete environment transfer process.
Main Features
- License migration
Moves Gravity Forms and GravityKit addon license keys between domains. - Entry transfer
Exports and imports form submissions preserving original IDs, metadata, and timestamps. - URL mapping
Rewrites internal URLs in fields, notifications, and confirmations when migrating to the new domain. - Automatic backup
Creates restore points before the operation to revert changes if necessary. - Compatibility with GravityView
Migrates views, layouts, and display settings linked to transferred forms.
Benefits of GravityMigrate – Migrate Your Gravity Forms Data
- Saves operational hours
Reduces the migration window from a full day of manual work to minutes. - History continuity
Preserves entries and accumulated statistics with no data loss when switching servers. - Less risk of human error
Automates the critical process, avoiding misconfigurations of notifications and integrations. - Staging to production transition
Facilitates development cycles with consistent migrations between testing and live environments.
Who Is It For?
- Administrators managing multiple WordPress sites with complex forms.
- Agencies delivering projects moving from client staging to production.
- Developers needing to clone Gravity Forms environments between servers.
- Teams restructuring domains wanting to preserve submission history.
As an additional resource to the GravityKit ecosystem, the addon solves one of the most sensitive challenges for those working with Gravity Forms in production: data migration without breaking integrations or losing accumulated entries. For agencies and developers operating frequent staging and production cycles, process automation eliminates rework and ensures consistency across environments.
Frequently asked questions
Is GravityMigrate – Migrate Your Gravity Forms Data GPL-licensed?
Yes. GravityMigrate – Migrate Your Gravity Forms Data 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 GravityMigrate – Migrate Your Gravity Forms Data on multiple sites?
Yes. You can install GravityMigrate – Migrate Your Gravity Forms Data on as many sites as you want. Only automatic updates through Ultrapack Auto Updater have a limit: from 3 to 80 sites, depending on the plan.
How much does GravityMigrate – Migrate Your Gravity Forms Data cost at Ultrapack?
GravityMigrate – Migrate Your Gravity Forms Data 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 GravityMigrate – Migrate Your Gravity Forms Data include updates?
Yes. The current version of GravityMigrate – Migrate Your Gravity Forms Data is 2.1.0, published at Ultrapack on Sep 18, 2026. Subscribers update straight from the WordPress dashboard with UAU (Ultrapack Auto Updater).
Is GravityMigrate – Migrate Your Gravity Forms Data scanned before publication?
Yes. Every version of GravityMigrate – Migrate Your Gravity Forms Data goes through a malware scan (ClamAV and YARA rules, at UltraHub) before it is published.
What are the requirements for the plugin GravityMigrate – Migrate Your Gravity Forms Data?
Requires WordPress 6.2 or higher and PHP 7.4 or higher. Tested up to WordPress 7.1.1.
What changed in this version
Version 2.1.0
- This release adds support for using AI to fully handle your migration. Note: GravityMigrate now requires WordPress 6.2 or newer.
- Ask an AI assistant to do your migration. If you use an AI assistant like Claude, you can now connect it to your site with the [GravityKit MCP]
- 💻 Developer Updates
- Added eleven new WordPress Abilities, registered through GravityKit Foundation, each prefixed with `gk-gravitymigrate/`.
Version 2.0.0
- You can now migrate forms between Gravity Forms and seven top form plugins (import and export), the interface has been fully redesigned, migrations can now run in the background, and exports can include uploaded files in the downloaded bundle. The release also includes security enhancements; we recommend updating to the latest version. [Read the 2.0 release post]
- Migrate forms between Gravity Forms and seven other form plugins, in both directions: Contact Form 7, Fluent Forms, Formidable Forms, Forminator, Ninja Forms, WPForms, and WS Form. Field types, labels, required fields, choices and their stored values, placeholders, default values, conditional logic, notifications and confirmations are all migrated where the destination supports them. [Learn more about migrating from other forms]
- Anything the destination plugin cannot represent is reported on screen during the migration rather than dropped silently. Contact Form 7, for example, has no conditional logic, time field or password field, so those are named as they are converted
- Background migrations. Imports and exports no longer need you to keep the tab open.
- Exports can carry the uploaded files inside them. This allows you to generate migration files from sites that are unreachable. [Read about bundling files]
- Gravity Forms Signature Add-On files are now migrated with their entries.
- ✨ Improved
- Keyboard navigation and screen reader accessibility. The new interface features much-improved keyboard focus behavior and aria live announcements.
- The browser's Back and Forward buttons move through the wizard, and a step can be linked to or reloaded without losing your place.
- Settings are no longer carried across by default, and overwriting the destination's settings asks for confirmation first.
- Gravity Flow activity history now imports on destinations that do not have Gravity Flow installed yet.
- 🔒 Security
- Migrating forms now requires full administrator access. The wizard, the background jobs and the WP-CLI commands all now require the `manage_options` capability.
- Improved file naming to prevent guessing file paths.
- Hardens access control on the migration endpoints.
- Secures how a migration file's contents are handled when they are written into the destination site, so a file from an untrusted source cannot modify the site.
- Refuses a file whose name hides a disallowed extension behind an allowed one, such as `photo.php.png`, wherever a migration file names the files it carries.
- Leaving the page during a migration your browser is running now frees the site immediately, instead of refusing the next import for two minutes with "an import is already in progress". If a run was interrupted some other way, the Confirm step says so and counts down, rather than letting you press Import and be turned away. Your uploaded file is kept either way.
- Reloading or closing the tab during a migration your browser is running now asks you to confirm first, and says so on the screen instead of describing every migration as running in the background. A migration that cannot be resumed no longer keeps asking on every later page, and a migration that was refused before it started is no longer offered for resume.
- Canceling an import that was running in the browser could leave "an import is already in progress" showing for two minutes if the server stopped the request while it was still deleting the uploaded file. The site is now free for a new import before the file is removed.
- A form submitted by a visitor during an import could conflict with the migration entry IDs.
- An export that was abandoned part way left its record of processed posts behind, so every later export silently left those pages and posts out while still reporting success.
- A Gravity Wiz Nested Forms field pointing at a form that was not in the migration file could halt the import.
- An export carried some settings that were not selected.
- An export could stop partway when a single uploaded file could not be read. That file is now left out of the migration file and named as left out after the export finishes.
- 💻 Developer Updates
- Added filters
- `gk/gravitymigrate/background/enabled` turns background migrations off, or forces the browser-driven path.
- `gk/gravitymigrate/export/batch-size` adjusts how much an export processes per step.
- `gk/gravitymigrate/cron/clear-import-interval` and `gk/gravitymigrate/cron/clear-export-interval` change how long staged import files and finished exports are kept.
- `gk/gravitymigrate/import/signature/source-url` modifies the URL a Signature Add-On image is fetched from during import.
- `gk/gravitymigrate/export/file-size-limit` sets how many bytes of uploaded files an export packages inside the migration file. Files past the limit stay on the source site and are downloaded during the import.
- `gk/gravitymigrate/export/max-candidate-files` caps how many uploaded files an export considers packaging (default: 20,000).
- `gk/gravitymigrate/import/packaged-file-types` widens the file types an import will accept out of a migration file. It cannot widen what counts as safe: the disallowed extensions are not filterable.
- WP CLI adds `--include-files` to the `wp gk migrate export` command to package the uploaded files inside the migration file. [See the CLI docs]
Version 1.4.0
- This release adds live progress reporting to the WP-CLI migration commands, improves security, and fixes exporting on some hosting configurations. We recommend updating to the latest version.
- 🔒 Security
- Hardens access control on the migration endpoints.
- Fixes exporting on sites where WordPress cannot write files directly as the web user, such as running the WP-CLI commands as a user other than the one that owns the site's files.
- 💻 Developer Updates
- `wp gk migrate status` now reports a running import's progress, including the current phase, how much has been processed, percent complete, and an estimated time remaining.
- Use `wp gk migrate status --watch` to follow a running import until it finishes.
- 🔄 Updated
- [Foundation]
Version 1.3.1
- This release fixes data-integrity issues when importing entries, including wrong Gravity Wiz Nested Forms references and duplicated entries after resuming an interrupted import.
- Imported entry meta and notes could attach to the wrong entries when the destination site's new entry IDs overlapped the imported entries' original IDs — breaking Gravity Wiz Nested Forms parent references, among other data.
- Issues with imports that were interrupted and resumed
- Gravity Wiz Nested Forms child entries could end up pointing at the wrong parent entry and parent form
- The same batch of entries could be imported twice after the connection dropped mid-transfer.
- Importing Gravity Flow data without selecting entries skipped the Gravity Wiz Nested Forms relationship update for the entries it brought along.
- 🔄 Updated
- [Foundation]
Version 1.3.0
- This release adds WP-CLI support for running migrations from the command line and dramatically speeds up imports and exports, fixes a range of import and export bugs, and patches several security issues. We recommend updating to the latest version.
- Note: GravityMigrate now requires PHP 7.4 or newer.
- [WP-CLI commands]
- `wp gk migrate export` exports forms, entries, Views, and other data to a portable ZIP, with options to filter by form or data type, limit by date range, encrypt the ZIP, and rewrite URLs for the destination site.
- `wp gk migrate import` imports a bundle, with options to filter forms/data or skip file uploads.
- `wp gk migrate inspect` previews a bundle's forms, data types, and source URL without importing it.
- `wp gk migrate status` reports migration state, including whether an import is in progress or a previous import stalled.
- `wp gk migrate reset` clears stuck migration state.
- ✨ Improved
- Imports and exports are now up to 28x faster, especially for large migrations on sites with many posts.
- The ZIP uploader now explains why an import file cannot be read.
- 🔒 Security
- Fixed multiple security issues, including one that could allow unintended access under certain conditions.
- Nested Forms (Gravity Wiz) parent/child relationships could be remapped using entries from other forms during import.
- Multiple files uploaded to the same field could overwrite each other during import, resulting in lost files.
- Gravity Flow workflow step history was not updated to reference the correct feed after import.
- A PHP warning could occur while exporting posts whose GravityView content (Views, widgets) referenced a form.
- Entry references in imported Views or pages could point at the wrong entries, including when an imported form failed to import and left a gap in entry IDs.
- Gravity Forms and GravityKit plugin settings migration could fail.
- Import no longer aborts entirely when a form, GravityView View, or Multiple Forms join references a form that was deleted at the source or wasn't included in the import.
- A View whose connected form was not included in the export was dropped during import, leaving its page showing a shortcode for a View that no longer existed. The View now imports with its form connection cleared.
- Imported entries kept a link to a post (where the entry was submitted from) that was not part of the export, which could attach the entry to an unrelated imported View or page.
- An import that stops part way no longer leaves the importer locked, so a corrected file can be imported right away.
- The export screen offered Gravity Flow data on sites that have Gravity Flow feeds but no workflow history to export.
- 💻 Developer Updates
- Added filters
- [`gk/gravitymigrate/import/max-download-bytes`]
- [`gk/gravitymigrate/export/row`]( modifies a data row's values before it's written to the export dump (e.g. to remap file-upload URLs).
- [`gk/gravitymigrate/export/info`]
- [`gk/gravitymigrate/import/upload-url`]
- 🔄 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
gravitymigrate.zip. - In the WordPress dashboard, go to Plugins > Add New > Upload Plugin.
- Select the file
gravitymigrate.zipand click Install Now. - Click Activate.
Requirements: Requires WordPress 6.2 or higher and PHP 7.4 or higher. Tested up to WordPress 7.1.1.
Stuck on a step? Open a ticket telling us which one you stopped at.
