7 versions
GravityMigrate history.
Every release of GravityMigrate is archived here with its changelog, file size, and security scan result. Use the archive to roll back to a stable release or audit what changed between updates.
6 of 7 releases scanned clean
v1.4.0Latest
August 27, 20263.0 MBScanned
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.
#### 🐛 Fixed
* 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](https://www.gravitykit.com/foundation/) to version 1.30.0.
August 7, 20262.9 MBScanned
This release fixes data-integrity issues when importing entries, including wrong Gravity Wiz Nested Forms references and duplicated entries after resuming an interrupted import.
#### 🐛 Fixed
* 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](https://www.gravitykit.com/foundation/) to version 1.28.0.
v1.3.0Unavailable
July 24, 20263.2 MBScanned
Other
- 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.**
- #### 🚀 Added
- [WP-CLI commands](https://www.gravitykit.com/docs/gravitymigrate/migrating-from-the-command-line-with-wp-cli/) for scripting migrations without the browser UI:
- `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
- 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
- [`gk/gravitymigrate/import/max-download-bytes`](https://www.gravitykit.dev/docs/gravitymigrate/filters/gk-gravitymigrate-import-max-download-bytes/), [`gk/gravitymigrate/import/max-dump-file-size`](https://www.gravitykit.dev/docs/gravitymigrate/filters/gk-gravitymigrate-import-max-dump-file-size/), and [`gk/gravitymigrate/import/download-timeout`](https://www.gravitykit.dev/docs/gravitymigrate/filters/gk-gravitymigrate-import-download-timeout/) adjust the import safety limits for sites that legitimately migrate very large amounts of data.
- [`gk/gravitymigrate/export/row`](https://www.gravitykit.dev/docs/gravitymigrate/filters/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`](https://www.gravitykit.dev/docs/gravitymigrate/filters/gk-gravitymigrate-export-info/) modifies the export's `info.json` metadata before it's written.
- [`gk/gravitymigrate/import/upload-url`](https://www.gravitykit.dev/docs/gravitymigrate/filters/gk-gravitymigrate-import-upload-url/) modifies the source URL a linked upload is downloaded from during import.
- #### 🔄 Updated
- [Foundation](https://www.gravitykit.com/foundation/) to version 1.26.0.
Fixed
- multiple security issues, including one that could allow unintended access under certain conditions.
Added
- filters:
May 15, 20262.8 MBScanned
This release resolves a fatal error caused by reactivating other GravityKit plugins alongside GravityMigrate, an export failure on certain configurations, and import files that wouldn't fully clear on the first click.
#### 🐛 Fixed
* Exporting could fail with a "Server returned an invalid response" error on certain configurations.
* The Remove button for uploaded import files could require a second page reload to fully clear them.
* A PHP fatal error in the admin menu could occur when another GravityKit product was reactivated while GravityMigrate was active.
#### 🔄 Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.18.0.
v1.1.4Unavailable
November 18, 20252.5 MBUnknown
Other
- This update resolves several issues affecting export and import functionality.
- #### 🐛 Fixed
- Forms in the Trash being shown in the Export Forms list.
- Forms were being eagerly loaded on unrelated requests.
- "Uploads & Files" may be inaccessible if the source site has a redirect (for example, HTTP to HTTPS).
- PHP error "Undefined array key 0" when database query returns no results during import.
- Source URL accessibility check now falls back to GET request when HEAD request returns 400 or 405 status codes.
- Broken export file link when WordPress is configured to use remote storage (e.g., Amazon S3) for uploads.
- #### 💻 Developer Updates
- #### 🔄 Updated
- [Foundation](https://www.gravitykit.com/foundation/) to version 1.6.1.
Added
- `gk/gravitymigrate/remote-request-args` filter to modify arguments used in remote `HEAD` and `GET` requests when testing source URL accessibility.
v1.1.3Unavailable
November 27, 20242.3 MBScanned
This hotfix update addresses a non-critical PHP notice in WordPress 6.7 and newer.
#### 🐛 Fixed
* PHP notice in WordPress 6.7 caused by initializing product translations too early.
#### 🔄 Updated
* [Foundation](https://www.gravitykit.com/foundation/) to version 1.2.21.
Why archive
Sometimes the latest release isn't the one you need. The archive lets you pin GravityMigrate to a known-good version, or roll back while a bug is investigated. Every release stays scanned and reachable.