Command line (WP-CLI)

GravityMigrate registers a wp gk migrate command for running migrations without the browser. It exports a portable ZIP bundle, imports one, inspects one, moves forms between Gravity Forms and another form plugin, and clears stuck migration state.

Every command drives the same code the admin screens use, run to completion synchronously in a single command. The admin screens can hand a long migration to the background scheduler; the CLI does not, because the command already survives the browser being closed.

The commands are available once GravityMigrate is active. GravityKit Foundation, bundled with the plugin, registers the top-level wp gk namespace.

Commands​

wp gk migrate export​

Exports Gravity Forms and GravityKit data to a portable ZIP bundle.

# Export one form with entries, Views, and the pages that embed them
wp gk migrate export --forms=2 --user=admin

# Export everything, encrypted, to a specific path
wp gk migrate export --forms=all --data=all --password=s3cret \
  --output=/srv/bundles/site.zip --user=admin

# Export from a demo clone whose stored URL is not publicly reachable
wp gk migrate export --forms=2 --public-url=https://example.demo.gravitykit.com \
  --output=/srv/bundles/demo.zip --porcelain --user=admin

wp gk migrate import​

Imports a GravityMigrate ZIP bundle into this site.

# Import a bundle
wp gk migrate import bundle.zip --user=admin --yes

# Import only two of the bundle's forms, without downloading uploads
wp gk migrate import bundle.zip --forms=2,5 --skip-uploads --user=admin --yes

# Raise the dump-size limit for one very large bundle
wp gk migrate import big.zip --max-dump-file-size=1073741824 --user=admin --yes

Entry file uploads are downloaded from the source site during import, so importing uploads pulls entries in with it. If a download fails because the source URL is unreachable, the entry keeps pointing at the source; re-export with --public-url set to an address the importing server can reach.

wp gk migrate inspect​

Prints a bundle's forms, data types, and source URL without importing it, and reports whether its upload URLs will resolve from this site and whether its database dump is within the size limit.

wp gk migrate inspect bundle.zip
wp gk migrate inspect bundle.zip --format=json

wp gk migrate status​

Reports current migration state: whether an import lock is held (and whether it is stale), whether a crashed import is saved for the admin screens to resume, and whether an export left state to clean up.

While an import is running, it also reports live progress from the record each step writes: the phase, current and total counts with a percentage, how many seconds since the record last advanced (the is-it-stuck signal), and a rough estimate of the time remaining.

wp gk migrate status
wp gk migrate status --format=json

# Follow a running import to completion
wp gk migrate status --watch

wp gk migrate reset​

Clears stuck migration state: the temporary tables, the extracted import files, and the import and export progress options. Use it when an interrupted migration leaves a later one refused.

wp gk migrate reset --user=admin --yes

wp gk migrate plugins​

Lists the form plugins GravityMigrate supports, whether this site can migrate to and from each one, and the reason where it cannot.

wp gk migrate plugins

# Just the slugs this site can migrate with, for scripting
wp gk migrate plugins --available --format=ids

wp gk migrate from​

Brings forms from another form plugin into Gravity Forms, running the same migration as the wizard's "Bring forms into Gravity Forms" path.

# See what a migration would do, field by field, without writing anything
wp gk migrate from ninja-forms --forms=all --dry-run

wp gk migrate from contact-form-7 --forms=2 --user=admin --yes

wp gk migrate to​

Writes Gravity Forms forms out to another form plugin, running the same migration as the wizard's "Move forms to another plugin" path.

wp gk migrate to contact-form-7 --forms=all --dry-run

wp gk migrate to ninja-forms --forms=3,5 --user=admin --yes

Data types​

--data accepts a comma-separated list of these types, or all:

Scripting​

--format=json prints a machine-readable summary. --porcelain prints only the essential value: the ZIP path from export, or the newly created form IDs (one per line) from import. Together they let you chain a migration between two servers:

#!/bin/bash
set -e

# Export on the source site and capture just the ZIP path
ZIP=$(wp gk migrate export --forms=all --data=all --porcelain --user=admin)

# Copy it to the destination and import it there
scp "$ZIP" deploy@destination:/tmp/migration.zip
ssh deploy@destination "wp gk migrate import /tmp/migration.zip --user=admin --yes --porcelain"

Tuning import safety limits​

The import command caps download time, download size, and the bundle's database-dump size to protect the server. Each cap has a filter, and each filter has a matching import flag that overrides it for a single run:

Set a filter to change the limit for every import on a site that legitimately migrates very large amounts of data:

add_filter( 'gk/gravitymigrate/import/max-dump-file-size', function () {
	return 1073741824; // 1 GB
} );

gk/gravitymigrate/background/enabled turns background migrations off for the admin screens, or forces the browser-driven path; it has no effect on the CLI, which always runs synchronously.

See the Filters reference for the full list, including gk/gravitymigrate/export/row and gk/gravitymigrate/export/info for reshaping exported data, and gk/gravitymigrate/import/upload-url for redirecting where a linked upload is downloaded from.

Related​

• GravityMigrate filters
• GravityMigrate actions
• Migrating from the command line (user guide)