Description
The Challenge: Feeds Only Fire for New Entries
Gravity Forms Feed Forge bulk processes feeds for entries that already exist in your database. That sounds like a small convenience until you hit the situation it fixes. A Gravity Forms feed is normally triggered at the moment someone submits a form. Any entry collected before you configured the feed, or before the add-on was installed, never passed through it. Those records sit in the Entries list, untouched by the integration you set up later.
The usual workarounds are unpleasant. You can export a spreadsheet and import it into the destination service by hand, with all the column mapping and cleanup that involves. You can ask a developer to write a one-off script. Or you can resubmit entries one at a time, which is tolerable for five records and absurd for five thousand.
Consider a few real cases. A site has collected leads for two years and the team has just moved to a new CRM. A membership form has accumulated hundreds of submissions that were never turned into user accounts. A feed was misconfigured, so a batch of entries went to the wrong place or nowhere at all. In each of these, the data is already there. What is missing is a way to push it through the feeds.
How Gravity Forms Feed Forge Helps
The Gravity Forms Feed Forge WordPress plugin adds a bulk action to the Entries view that runs your configured feeds against entries you choose. The workflow has two primary steps. First, open the Entries screen and select the records you want to process, using the selection tools Gravity Forms already provides. Second, choose which feeds should run for those entries. That is the whole procedure.
The plugin works with nearly any feed-based add-on. Payment add-ons are the exception, which makes sense: re-running a payment feed against old entries is not something anyone should do casually. For everything else, whether it pushes data to a spreadsheet, a CRM, a file storage service, or into WordPress itself, Feed Forge can send existing entries through it.
Background processing for large batches
Feed Forge relies on the background processor built into Gravity Forms. When you start a job, the work is queued and handled behind the scenes rather than inside a single browser request. You can process feeds for thousands of entries and keep working in the WordPress dashboard while the queue runs. There is no need to leave a tab open and hope it does not time out.
Core Features
- Bulk feed processing for existing entries. Select entries in the Entries view and run feeds against them in one action, instead of resubmitting or re-importing records individually.
- Choice of feeds. After selecting entries, you pick which feeds to process, so you can run a single integration without triggering every other feed attached to the form.
- Broad add-on support. Works with nearly any feed-based add-on, with payment add-ons excluded.
- Background processing. Uses the Gravity Forms background processor so large batches run without tying up your session.
- Familiar entry selection. Relies on the entry selection features Gravity Forms already offers, so there is no new interface to learn.
- Two-step workflow. Select entries, select feeds, and let the queue do the rest.
Because the plugin hooks into the feed system rather than replacing it, the feeds behave the way you configured them. Field mappings, conditional logic, and destination settings stay where they are. Feed Forge simply supplies entries that missed their original trigger.
Practical Applications
The value of the plugin depends on which feed-based add-ons you run. The following scenarios show the range.
Sending historic data to a spreadsheet
If you add a Google Sheets feed using GP Google Sheets after a form has been live for months, new submissions will appear in the sheet but older ones will not. Feed Forge lets you select the earlier entries and send them over, giving you a complete dataset in one place.
Registering or updating users in bulk
With GF User Registration, you can create WordPress user accounts from existing form submissions. You can also bulk update users so their profiles reflect changes made to entries. This is useful when a registration feed was added late, or when profile data was corrected in the entries and needs to propagate to the user records.
Migrating between CRMs
Switching CRMs usually means a painful export and import cycle. If your submissions live in Gravity Forms, you can set up a feed for the new platform, such as GF ActiveCampaign, GF Agile CRM, or GF HubSpot, then process it against your stored entries. The contacts arrive through the same field mapping you would use for live submissions.
Moving files into Dropbox
Forms that accept uploads accumulate files inside WordPress. With GF Dropbox, Feed Forge can send those existing uploads to Dropbox, which helps when a team decides to move its file handling out of the media directory.
Generating posts from past entries
GF Advanced Post Creation turns submissions into WordPress posts. If you build that feed after collecting a body of content, such as testimonials, directory listings, or user-submitted stories, Feed Forge can create the posts from entries you already hold.
What Should You Know Before Running a Large Batch?
Re-running feeds has side effects in the destination systems, so a little planning pays off. Test with a small selection first and confirm the results in the target service. Check that the feed you intend to run is the only one you have selected. If a feed creates records rather than updating them, running it twice against the same entry may create duplicates, depending on how the add-on behaves.
Feed Forge is a tool for deliberate, one-time or occasional jobs. It does not change how your forms behave on new submissions. It also does not alter entry data. It sends what is already stored through the feeds you choose.
Frequently Asked Questions
Can Gravity Forms Feed Forge process payment feeds?
No. Payment add-ons are excluded. Charging or creating subscriptions from historic entries carries real financial consequences, so the plugin is limited to non-payment feeds. Every other feed-based add-on is a candidate for bulk processing.
Will it keep working if I process thousands of entries at once?
Feed Forge hands the job to the Gravity Forms background processor, which works through the queue in the background. This lets you process feeds for thousands of entries without sitting on a loading screen. You can carry on with other tasks in the WordPress admin while the queue runs.
Is Gravity Forms Feed Forge licensed under the GPL?
Yes. It is distributed under the GPL, so you can use it on your own sites, study the code, and modify it within the terms of that license. It operates as an extension to Gravity Forms and depends on the feed-based add-ons you already use to do the actual delivery of data.

