Which feeds and add-ons migrate

Gravity Forms add-ons store their per-form configuration as feeds: the Zap a form triggers, the mailing list it subscribes people to, the payment it takes, the workflow it starts. This article explains what GravityMigrate does with those feeds, what the new site needs for them to work, and which add-on files do not travel.

What “Add-on Feeds” carries #

Selecting Add-on Feeds on the export exports every feed attached to the forms you selected, whichever add-on owns it. GravityMigrate does not treat any add-on specially. Zapier, Mailchimp, User Registration, Stripe, PayPal, Authorize.Net, Webhooks, Fillable PDFs and Gravity Flow feeds all travel the same way, as rows of feed configuration that arrive on the new site with new feed IDs.

Two things do not travel with the feeds:

• The add-on’s own settings. API keys, connected accounts and everything else under the add-on’s tab in Gravity Forms’ settings are not part of a migration file. That holds even when Gravity Forms Settings is selected, because the option carries a handful of global settings such as the currency and the logging switch. Connect each add-on on the new site before its feeds can do anything.
• The add-on itself. GravityMigrate does not check whether an add-on is installed on the new site, and shows no warning. A feed whose add-on is missing sits unused until the add-on is installed and activated.

Feeds do not run for imported entries #

Imported entries are copied into the new site’s tables; they are not submitted again. No notification is sent, no Zap fires, nobody is subscribed to a list, no payment is taken and no workflow starts for an entry that arrived through a migration. Feeds start working for the submissions the new site receives from then on.

Feed IDs change #

Feeds are renumbered on the new site. GravityMigrate updates the references it knows about: a GravityView widget that names a feed, and GravityCharts charts embedded in the pages that travel with the migration. Two kinds of reference keep the old number and need updating by hand. One is a View field that stores a feed ID. The other is a merge tag in a notification or confirmation that names a feed by its ID, such as a Fillable PDFs document tag. What changes when you import has the full list.

Add-ons with more than feeds #

• Zapier. The feed travels, but each Zap stores the old site’s address and has to be repointed inside Zapier: Migrating Zapier feeds.
• Gravity Flow. The workflow steps are feeds and travel with Add-on Feeds. The per-entry history of what happened in those workflows is a separate option, Gravity Flow Data, which needs the entries to come along. A workflow can be moved without its history; the history cannot be moved without its entries.
• Signature Add-On. The feed-less signature field migrates, and the signature images people drew are fetched with their entries, or packaged when the export includes the files. The new site needs the add-on active before the import, because the images are saved into its folder; without it the import reports “Cannot import signature files: no signatures folder. Is the Gravity Forms Signature Add-On active on the destination site?”
• Fillable PDFs. The feed travels and is renumbered. The PDF documents it generated stay on the old site, and a View field or merge tag that named the feed by ID points at the old number.
• Payment add-ons (Stripe, PayPal, Authorize.Net). The feed’s configuration travels; the gateway credentials do not, and no payment is re-processed for imported entries. The payment details recorded on each entry travel with the entry.

Related articles #

• What changes when you import
• Where uploaded files go during a migration
• Migrating Zapier feeds