Migrate from Forms On Fire to monday CRM

Each Forms On Fire form maps 1:1 to one Monday CRM board. The form name becomes the board name. All form fields become board columns in the order they appear in the form designer. Multi-page forms are flattened — page breaks do not map to any Monday construct, so field grouping by page is communicated to your admin before migration as a board folder or naming convention.

Forms On Fire field types are translated to the closest Monday column type. Text, Number, Date, Location (GPS), and File fields map directly. Choice and multi-choice fields map to Monday Dropdown or Tags columns with value-by-value mapping. Data Source lookup fields require a pre-existing Monday lookup column or connected board. Signature and Barcode fields are stored as text or file values in Monday's closest equivalent column type.

Each Forms On Fire submission becomes a Monday Item in the target board. The submission's primary field (typically the submission ID, a form-defined name field, or the first text field) maps to the Item's Name column. All other field values map to the corresponding board columns by name. Original submission timestamps map to Monday's Created Date; the submission's last-modified timestamp maps to the Item's Last Updated date.

If a Forms On Fire form has an Assigned User field or captures the submitter's identity, that value maps to a Monday People column. FlitStack resolves the user by email — if the email matches an existing Monday workspace member, the item is assigned automatically. Unmatched users are flagged in the pre-migration audit and can be invited to Monday before the full run.

Forms On Fire Data Sources are reference tables used as choice lists or linked records. Small Data Sources (under 100 rows, static options) are re-created as Monday Dropdown column options directly in the target board. Larger or dynamic Data Sources need a connected Monday board with the same columns; the migration plan flags these and your admin creates the connected board before migration runs. Data Source references in submissions are preserved as the row label value.

Photos attached to a submission are downloaded and re-uploaded to the Monday board's File column on the corresponding item. Monday stores files in its own storage (subject to plan limits — Basic 3GB, Standard 20GB). Large submissions with multiple photos may require storage pre-assessment. Inline images embedded in notes or long-text fields are handled the same way.

Forms On Fire Location fields capture latitude, longitude, and optional address text via device GPS or map pin. These map to Monday's Location column, which stores structured location data including address, lat/long, and map thumbnail. The original GPS accuracy value from Forms On Fire is preserved as a text note in a secondary text column since Monday's Location column does not expose accuracy metadata.

Forms On Fire workflow rules — triggers on submission, field-value changes, or scheduled conditions — do not migrate. They must be rebuilt in Monday's Automation Centre. FlitStack exports your Forms On Fire workflow definitions as a structured document (trigger type, conditions, actions) that your Monday admin can use as a rebuild reference. This is the most significant rebuild effort in any Forms On Fire to Monday migration.

Forms On Fire's Word and Excel template features generate output documents from submission data — these do not exist in Monday CRM. The template logic (field-to-placeholder mappings) is documented in the migration package, but document generation must be rebuilt using Monday Docs, an external integration (Make/Zapier), or a dedicated document automation tool.

If a Forms On Fire form uses Groups or Repeatable Sections to capture multiple records in one submission (e.g., a safety inspection covering multiple areas), these map to Monday Item Groups or Subitems depending on the data structure. Single-level repeatable sections work well as Monday Subitems; deeply nested structures require flattening and your admin chooses the grouping strategy before migration.

Forms On Fire form templates and version history are not migrated as separate objects. The final published version of each form maps to the Monday board. Version history and draft forms are documented in the migration audit report for your admin to review; active forms are prioritized for board creation.

Each Forms On Fire form has an internal API identifier. This is preserved on the Monday board as a custom text column labeled Source_Form_ID__c for traceability. Submissions also carry their Forms On Fire record ID — this is stored as Source_Record_ID__c on each Monday Item so delta-pickup runs can de-duplicate against the source system without creating duplicate items.