Migrate your Forms On Fire data
No-code mobile forms and workflow automation platform for field teams, with offline data collection and GPS/signature/barcode capture. Most popular in construction, manufacturing, and field services environments.
In its favor
Why people choose Forms On Fire
The signal that keeps Forms On Fire on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Drag-and-drop form builder requires no coding, letting field supervisors create digital inspection forms and safety checklists without developer involvement.
Offline-first mobile data collection syncs automatically when connectivity returns, keeping field crews productive in remote or underground locations.
Over 3,000 integrations including Zapier, Salesforce, and Microsoft products allow field data to flow directly into existing business systems.
Responsive onboarding and customer support teams help organizations migrate from paper-based processes to digital workflows in days rather than weeks.
AI-assisted form generation from text descriptions, voice input, or uploaded PDFs accelerates initial app creation for new use cases.
Steeper-than-expected learning curve for complex form logic, dynamic filtering, and multi-step workflows requiring conditional field visibility.
Managing connected data between forms and Data Sources is difficult, with limited UI for tracing and debugging data relationships.
Entry volume limits on Standard tier (1,500 per user per month) force organizations to upgrade or delete historical records as they scale.
Complex workflows and advanced features require custom configurations that typically need technical expertise, negating the no-code promise for sophisticated use cases.
Some organizations report the platform becomes difficult to navigate as the number of apps and forms grows across the organization.
Reasons to switch
Why people leave Forms On Fire
The recurring reasons buyers give for replacing Forms On Fire. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Forms On Fire fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Forms On Fire pricing overview
Forms On Fire charges per-seat on a monthly or annual basis with a 20% discount for annual prepayment. Entry volume is gated on Standard (1,500/user/month), removed on Premium, and enterprise features require a minimum of 25 users. Volume discounts begin at 26 seats.
Standard Edition
Tier 1 of 3
$20/user/month (monthly) or $25/user/month billed monthly; $20/user/month billed yearly (20% savings)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Forms On Fire's schedule — see our quote-based pricing →
What gets migrated
Forms On Fire object support
Object-by-object support for Forms On Fire migrations. Per-pair details surface during scoping.
Forms
Fully supportedForms are the primary container in Forms On Fire, containing Pages and Fields. We export form definitions including all field configurations, validation rules, and layout structure as JSON or Excel. Form logic referencing Data Sources is preserved as part of the export.
Form Fields
Fully supportedAll standard field types are exportable: text, number, date, Choices, Data, Location (GPS), Signature, Photo, Barcode, and calculated fields. Data names (case-sensitive, underscore-only) are preserved verbatim in exports. Custom field-level validation rules are included in the migration package.
Data Sources
Fully supportedData Sources are structured datasets used for Choices dropdowns and Data lookups. We export Data Sources as tabular data preserving column headers and row data. First-column uniqueness (row identifier) is maintained to preserve filtering behavior post-migration.
Entries (Submissions)
Mapping requiredEntry records are submitted form responses. We export all Entries with field values, timestamps, user assignments, and GPS coordinates. However, Standard tier limits (1,500 entries/user/month) mean historical Entries may have been deleted — we flag missing records during scoping.
Apps
Mapping requiredApps are containers grouping related Forms for deployment. We preserve app structure and the Form-to-App assignments during migration. Where the destination system uses Projects or Workspaces, we map App groupings accordingly.
Users
Mapping requiredUser records include name, email, and role assignments. We export user lists and their form access permissions. Note that billing is per-user — organizations may have inactive or decommissioned users that inflate seat counts in the source system.
Document Templates (docx/xlsx)
Mapping requiredWord and Excel output templates define how Entry data is rendered into documents. We export template files but flag that dotx template linkage (a known Forms On Fire issue) can cause generation failures if the original template referenced an inaccessible local file.
Integrations / Connectors
Mapping requiredPremium and Enterprise connectors (Salesforce, SAP, Power BI, etc.) are configuration-level settings. We document integration endpoints and auth credentials for re-configuration in the destination system. 3,000+ Zapier-compatible integrations can be rebuilt using the API key and webhook URLs.
Workflows
Mapping requiredWorkflows automate post-submission actions like notifications, doc generation, and external API calls. We export workflow definitions but complex conditional logic and external API call configurations may require manual re-implementation in the destination BPM tool.
Offline Sync Data
Not in this platformOffline submission queues sync automatically when connectivity returns — the submitted data becomes standard Entries and is migrated with Entries. The transient offline queue itself is a runtime artifact and not independently exported.
| Object | Support | Notes |
|---|---|---|
| Forms | Fully supported | Forms are the primary container in Forms On Fire, containing Pages and Fields. We export form definitions including all field configurations, validation rules, and layout structure as JSON or Excel. Form logic referencing Data Sources is preserved as part of the export. |
| Form Fields | Fully supported | All standard field types are exportable: text, number, date, Choices, Data, Location (GPS), Signature, Photo, Barcode, and calculated fields. Data names (case-sensitive, underscore-only) are preserved verbatim in exports. Custom field-level validation rules are included in the migration package. |
| Data Sources | Fully supported | Data Sources are structured datasets used for Choices dropdowns and Data lookups. We export Data Sources as tabular data preserving column headers and row data. First-column uniqueness (row identifier) is maintained to preserve filtering behavior post-migration. |
| Entries (Submissions) | Mapping required | Entry records are submitted form responses. We export all Entries with field values, timestamps, user assignments, and GPS coordinates. However, Standard tier limits (1,500 entries/user/month) mean historical Entries may have been deleted — we flag missing records during scoping. |
| Apps | Mapping required | Apps are containers grouping related Forms for deployment. We preserve app structure and the Form-to-App assignments during migration. Where the destination system uses Projects or Workspaces, we map App groupings accordingly. |
| Users | Mapping required | User records include name, email, and role assignments. We export user lists and their form access permissions. Note that billing is per-user — organizations may have inactive or decommissioned users that inflate seat counts in the source system. |
| Document Templates (docx/xlsx) | Mapping required | Word and Excel output templates define how Entry data is rendered into documents. We export template files but flag that dotx template linkage (a known Forms On Fire issue) can cause generation failures if the original template referenced an inaccessible local file. |
| Integrations / Connectors | Mapping required | Premium and Enterprise connectors (Salesforce, SAP, Power BI, etc.) are configuration-level settings. We document integration endpoints and auth credentials for re-configuration in the destination system. 3,000+ Zapier-compatible integrations can be rebuilt using the API key and webhook URLs. |
| Workflows | Mapping required | Workflows automate post-submission actions like notifications, doc generation, and external API calls. We export workflow definitions but complex conditional logic and external API call configurations may require manual re-implementation in the destination BPM tool. |
| Offline Sync Data | Not in this platform | Offline submission queues sync automatically when connectivity returns — the submitted data becomes standard Entries and is migrated with Entries. The transient offline queue itself is a runtime artifact and not independently exported. |
Gotchas
What to watch for in Forms On Fire migrations
Issues we've hit on past Forms On Fire migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Standard tier entry limits silently gate historical data
dotx template linkage breaks Word document generation
Data Source auto-select behavior can silently alter form state
Enterprise requires 25+ users minimum
Non-Office document generation not supported
| Severity | Issue |
|---|---|
| High | Standard tier entry limits silently gate historical data |
| Medium | dotx template linkage breaks Word document generation |
| Medium | Data Source auto-select behavior can silently alter form state |
| Low | Enterprise requires 25+ users minimum |
| Low | Non-Office document generation not supported |
Leaving Forms On Fire?
Where Forms On Fire customers move next
12 destinations Forms On Fire can migrate to.
How a Forms On Fire migration works
Four steps, Forms On Fire-specific
Connect
API key (Full Open API available on Standard and Premium) into Forms On Fire. Scopes limited to read-only on the data we move.
Map
We translate Forms On Fire-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Forms On Fire quirks before production.
Migrate
Full migration with Forms On Fire rate-limit handling. Rollback available throughout.
FAQ
Forms On Fire migration FAQ
Answers to the questions buyers ask most during Forms On Fire migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Forms On Fire migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Forms On Fire.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Forms On Fire setup and destination — written quote back within a business day.