🎉 Celebrate with 10% OFF on All Products! Use Code: GFEX10 Or Buy Any 2+ Items for 30% OFF with Code: GFEX30!
Guides & Tutorials October 15, 2026

Gravity Forms Staging to Production: Sync Forms with Git, Safely

GravityExtra
Gravity Forms Staging to Production: Sync Forms with Git, Safely

Every agency that builds Gravity Forms on a staging site knows the moment: the form is finished and approved, and now it has to go to production. The built-in export and import look like the answer, until the import creates a brand-new form with a new ID, the shortcode on the live page still points to the old form, the CRM feed is missing, and the old entries sit on a form nobody uses any more.

This guide explains why moving Gravity Forms between sites goes wrong, how a Git-based workflow fixes it, and how to set it up with the Gravity Forms Form Sync & Network Forms Premium Add-on — including multisite networks and fields shared by many forms.

Why Moving Gravity Forms Between Sites Is Hard

  • Form IDs are per site. Form 7 on staging can be form 12 on production. Shortcodes, blocks, page builders and custom code that reference an ID break.
  • Imports create, they do not update. Importing a changed form gives you a second copy instead of updating the live one, so its entries are split over two forms.
  • Feeds are separate. Mailchimp, HubSpot, Stripe or webhook feeds live in their own table and are easy to forget.
  • Secrets must not travel. Copying everything blindly can push staging API keys to production, or production keys into a Git repository.
  • Nobody sees the difference. Without a preview, an import is a leap of faith on a live site.

The Fix: Forms as Files, Matched by a Sync Key

Form Sync gives every form a permanent sync key the first time it is saved to the sync folder. The key, not the ID, identifies the form on every site. When you import the form on another site, the add-on finds the form with the same key and updates it in place: same ID, same shortcodes, same entries. A form that does not exist yet is created, and it can even keep the ID it had on the source site when that ID is free.

Each form is stored as one readable JSON file, with keys in a stable order, so a change to one field label is a one-line change in Git. Notifications, confirmations and feeds are in the same file; secret feed settings such as API keys are left out and stay on each site.

Sync folder screen with one form marked File changed and another In sync
The sync folder shows which side changed: this site, the file, or both.

Step by Step: Staging to Production with Git

1. Save the forms on staging

Install the add-on on every site. On staging, open Forms → Form Sync and click Save all forms to the folder. From then on, each form’s file is updated automatically whenever you save the form, a notification, a confirmation or a feed.

2. Commit and deploy

Add wp-content/gravityextra-form-sync to your repository next to your theme, commit, and deploy as you normally do — with a Git-based host, a CI pipeline, or a simple pull on the server. The folder blocks web access on Apache; on Nginx, point the GFXSYNC_FOLDER constant at a path outside the web root.

3. Review on production

On production, the Form Sync screen marks the deployed forms as File changed. Select them and click Review import. The review lists every field, notification, confirmation and feed that will be added, changed or removed — before anything is written.

Review import listing a changed field label, an added Phone field, an added notification and a changed feed setting, with a note about secret settings
Every change is visible before the import.

4. Import

Click Import selected forms. Each form is backed up first and then updated in place. If anything looks wrong afterwards, Backups restores the previous version of the form and its feeds in one click. Entries are never touched.

What Travels and What Stays

Part of the form Synced Notes
Fields, settings, button, layout Yes Updated in place, same form ID
Notifications and confirmations Yes Confirmation pages matched by slug
Feeds of any add-on Yes Order and on/off state included
API keys and secret feed settings No Kept on each site
Entries With a site package (1.1) Skipped or updated on a second import, never doubled
Add-on settings pages With a site package (1.1), without keys API keys, tokens and passwords stay on each site

Handling Conflicts

Sometimes a client edits a notification on production while you change the same form on staging. Form Sync remembers both sides at the last sync and shows Changed on both sides instead of silently overwriting. Open the review to see exactly what the file would change, then decide: import the file, or click Save to folder on production, commit, and merge the change back into staging. The backup taken before any import is your safety net either way.

Multisite: One Form, Many Sites

Franchise networks, universities and multi-brand companies often need the same form on dozens of sites: a contact form, a job application, a privacy request. On the main site, the Network forms tab shares a form with the sites you choose. Every site gets its own copy, with notifications and feeds, and its own entries. Tick Keep the copies in sync, and each save of the main form updates every copy. Editors on the sites see a note that the form is managed by the network, so nobody wonders why their changes disappeared.

Shared Fields: the Field Library

Even on a single site, the same fields repeat across forms: the consent checkbox, the country drop-down, the opt-in text that legal wants to change. Put them in the field library and add linked copies to your forms. When you save the library, every copy is updated, while each one keeps its own position, page, conditional logic and column layout. Need one copy to be different? Unlink it.

Field library with two library fields and their linked copies in two forms
One consent text, updated in every form at once.

Good Practice for Form Deployments

  • Edit forms in one place. Make changes on staging and deploy them; treat production edits as hotfixes you save back to the folder.
  • Keep secrets out of Git. Form Sync never writes API keys to files; keep plugin-wide keys in each site’s settings or environment.
  • Review before every import. A removed field disappears from the form (its old values stay in entries), so read the review.
  • Keep the original IDs. Leave “use the same form ID when it is free” ticked for new forms so shortcodes match across sites.
  • Test notifications on staging with a mail catcher, so test submissions never reach customers.

Deploy Gravity Forms Like Code

Forms, notifications and feeds in Git, a review of every change, backups, network forms and a shared field library.

What’s New in 1.1: Move Entries, Files and Settings Too

Sometimes the whole setup has to move, not only the forms: a client goes to a new host, a site is rebuilt, or two sites become one. Version 1.1 adds the site package: one zip file with the forms and, if you want, their entries, the files uploaded with them, the Gravity Forms settings and the settings of your add-ons.

1. Export the package

On the old site, open Forms → Form Sync → Site package, keep All forms ticked, choose entries, uploaded files and the settings you want to take along, and click Download site package (.zip). API keys, tokens, passwords and licence keys are never put in the file.

2. Review on the new site

On the new site, choose the zip under Import a site package. The review lists the forms it creates or updates, the entries per form (and how many were imported before), the uploaded files and the settings that differ. Nothing is saved until you click Import.

Review of a site package with three new forms, 457 entries, uploaded files and changed settings
The review shows every form, entry count and setting before the import.

3. Import in batches

Entries are imported 200 at a time with a progress bar, so large forms do not time out. Forms are matched by their sync key and fields by ID and type, so entries reach the right fields even when the IDs on the new site are different. Uploaded files are copied into the new site’s upload folder and the entries link to them there.

4. Import again without duplicates, or undo

Every imported entry remembers where it came from. Import a newer package later and the entries already there are skipped (or updated, if you choose), never added twice. If something is not right, Backups restores the settings and removes the imported entries in one click.

Read the step-by-step guide in the Form Sync documentation or get the add-on on the Form Sync & Network Forms page.

Frequently Asked Questions

Do I need Git?

No. Without Git, export a file on one site and import it on the other; you get the same review, backups and in-place updates.

Does it copy entries?

Not with the sync folder or an export file: those move the form only. Since version 1.1, a site package also moves the entries (with notes, starred, read and status) and their uploaded files, and never adds an entry twice.

What about payment and CRM feeds?

They travel with the form. Secret settings such as API keys are never exported; the values already stored on the target site are kept.

Will my form IDs change?

Existing forms keep their ID. New forms can use the same ID as on the source site when it is free.

Can I undo an import?

Yes. Every form is backed up before Form Sync changes it, and Backups restores it in one click.

Does it work on multisite?

Yes. Network-activate it to share forms from the main site with other sites of the network.

Is the sync folder safe on a public server?

The folder ships with a file that blocks web access on Apache servers. On Nginx, or if you prefer, move the folder outside the web root with one constant in wp-config.php. The files never contain API keys or other secret feed settings.

Do I need a particular Gravity Forms licence?

No. Any Gravity Forms licence, version 2.9 or newer, works.

0
0
Your Cart
Your cart is emptyReturn to Shop
🔥 FREQUENTLY BOUGHT TOGETHER
Complete Combo & Save 40%!
ITEM IN YOUR CART
Gravity Forms Klaviyo Add-on
$39.00/yr
+
🎁 RECOMMENDED ADD-ON SAVE 40% OFF
Original Price: $39.00/yr
Bundle Special Price: $23.40/yr