Migrate from Forms On Fire to Freshsales

Every Forms On Fire submission is a single record containing person data and field answers. FlitStack splits this into either a Freshsales Lead or Contact. Submissions with a valid email address and first/last name create a Contact. Submissions missing last name or containing a 'Lead Source' field value route to a Lead. Contact vs. Lead routing is configurable per form before migration runs.

Forms On Fire captures company name as a plain text field within a submission. We extract that text and either create a new Freshsales Account record or match against an existing Account by name. The Contact is then linked via AccountId lookup. If no company name is present, the Contact lands without an Account association — a default 'Unassigned Account' is optionally created.

Submissions containing a numeric field labeled deal_value, estimated_value, quote_amount, or similar trigger creation of a Freshsales Opportunity record alongside the Contact. The opportunity name uses the form name and submission ID. Stage defaults to the first pipeline stage. If no deal field exists in the form, no Opportunity is created — the submission is Contact-only.

If a form submission contains a dropdown or text field indicating a sales territory, product line, or pipeline segment, FlitStack maps this to a Freshsales Sales Pipeline. Pipelines must be pre-created in Freshsales before migration — we deliver a pipeline setup plan based on the form field values detected during the discovery phase.

The original Forms On Fire submission timestamp maps to the Freshsales Contact or Lead created_at field. This preserves the actual submission date for reporting continuity. If the submission was edited after initial capture, the last-modified timestamp is optionally stored in a custom datetime field.

The Forms On Fire internal submission ID is stored as a custom text field on the Freshsales Contact record. This enables traceability back to the source system and is used during delta-pickup runs to de-duplicate any submissions that were modified in Forms On Fire after the initial migration pass.

Photos captured via the Forms On Fire mobile app (image field type) are downloaded from Forms On Fire storage and re-uploaded to Freshsales as file attachments linked to the corresponding Contact record. Photos maintain their original file name and upload timestamp. Files exceeding Freshsales size limits are flagged before the full migration runs.

Signature fields in Forms On Fire generate PNG image files. These migrate as Freshsales attachments on the Contact record. The signature image appears in the Contact's timeline view. Signature images from old submissions are preserved but do not link to any Freshsales native e-signature workflow.

Barcode and QR code scan values captured via the Forms On Fire barcode field migrate to a custom text field (Barcode__c) on the Contact. This preserves the scanned identifier for inventory, asset, or asset-tracking workflows you intend to rebuild in Freshsales.

Forms On Fire Location fields store latitude and longitude as separate numeric values. These migrate to two custom number fields on the Contact record. Freshsales has no native map field type — these coordinates are available for reporting, map integrations, or custom app overlays, but no built-in Freshsales map visualization is created.

Forms On Fire Choice fields with static options map directly to Freshsales picklist custom fields. The option labels transfer as picklist values. If a Forms On Fire choice field pulls from a Data Source (dynamic options), we migrate the current snapshot of option values — dynamic lookups must be rebuilt as Freshsales Data Sources or manual picklist updates.

The name of the Forms On Fire form that generated the submission is stored as a custom text field (Source_Form__c) on the Contact or Lead. This is critical for segmentation — it lets you filter Freshsales reports by the originating form without requiring manual tagging post-migration.

Forms On Fire captures device type, OS version, and app version metadata per submission. Freshsales has no standard or custom field that accepts device metadata in this format. This data is not migrated. If device tracking is required post-migration, the Freshsales mobile app provides its own device telemetry.

Forms On Fire field-level conditional logic (show/hide fields, auto-populate values, routing rules) is embedded in the form definition and is not exportable as a standalone configuration. These rules must be documented and rebuilt in Freshsales Workflows. FlitStack offers a workflow audit deliverable to capture your Forms On Fire logic as a rebuild specification.

Forms On Fire Data Sources are lookup datasets that populate Choice and Data fields within forms. These are not linked to submission records — they are design-time references. Freshsales has no equivalent Data Source feature. The lookup datasets must be recreated manually as Freshsales picklist values or imported as CSV-based custom objects if the lookup data needs to persist in Freshsales.