Migrate from Forms On Fire to Nutshell

Forms On Fire stores form-field definitions as metadata. Each field (text, pick-list, GPS, photo) is read and translated into a corresponding Nutshell custom field on the appropriate object (Person, Lead, or Company). Field type mapping follows data-type equivalence: text to Text, numeric answers to Number, GPS to Text (lat/long), photo to a reference field.

A single Form Entry becomes one Nutshell Person record (if the form collects contact info) or one Lead record (if mapping strategy routes anonymous entries to Lead). The entry's submitted field values populate the matching Nutshell standard and custom fields. Multiple entries from the same email can be configured to update one Person or create separate Leads per entry.

Standard contact fields in a Form Entry (first name, last name, email, phone, address) map directly to the equivalent Nutshell Person field: first_name to First Name, email to Email, phone to Phone. These are direct 1:1 field-level mappings with no transformation.

Non-standard field values from a Form Entry (inspections results, order numbers, equipment IDs, custom data types) create Nutshell custom fields. Each custom field is created in Nutshell under the appropriate object before migration, with field type matched to the source data type (text, number, date, pick-list).

Forms On Fire captures metadata per entry: submission timestamp, device identifier, GPS latitude and longitude, and step completion status. These map to Nutshell custom fields: Submitted_At__c (datetime), Source_Device__c (text), GPS_Latitude__c and GPS_Longitude__c (number), and Step_Completed__c (text or pick-list). Original metadata preserved for reporting continuity.

Photo fields in Forms On Fire store binary images. Nutshell's Attachment object accepts one file per write operation with a 25MB limit. Photos exceeding this limit, or multiple photos per entry, require an external storage reference (URL stored in a custom text field) pointing to a hosted copy. Photos below the limit are migrated as Nutshell Attachments linked to the Person record.

Signature field outputs are binary image data. Similar to Photo fields, these migrate as Nutshell Attachments where size permits, or as a custom text field storing a reference URL to the hosted signature image if the binary exceeds Nutshell's file size limit.

Forms On Fire Data Sources provide dynamic pick-list options (e.g., a product catalog or contact list). The data source rows are read, and the active options at migration time are written as pick-list values on the corresponding Nutshell custom field. Dynamic updates to the Data Source after migration require manual pick-list updates in Nutshell.

Forms On Fire Process Steps gate form completion. Each completed step creates a custom field on the Person/Lead (Step_1_Completed__c = true, Step_2_Completed__c = Approved/Rejected) plus a Nutshell Activity record noting the step name, result, and timestamp. Step-email routing and conditional branching are not migratable and must be rebuilt in Nutshell Automation.

Forms On Fire user accounts are matched to Nutshell users by email address. Entry ownership is resolved by this email match — entries submitted by known Forms On Fire users land on the matching Nutshell user's records. Unmatched users are flagged before migration; their entries are assigned to a fallback owner or routed to an unassigned queue.

When a Form Entry contains B2B fields (company name, domain, industry), FlitStack creates a Nutshell Company record and links the Person to it via the Company lookup. Company data (name, domain, industry, employee count) maps to the equivalent Nutshell Company fields. Multiple entries from contacts at the same company are linked to the same Company record.

Each Form Entry submission is written as a Nutshell Activity (type = Form Submission) on the corresponding Person or Lead record, capturing the form name, submission timestamp, and entry ID. This preserves the submission history on the CRM contact timeline for audit and follow-up purposes.