Migrate from Field2Base to Salesforce Sales Cloud

Each Field2Base submitted form becomes a Salesforce Case. The form template name maps to Case Origin or a custom pick-list field (Form_Template_Name__c). Submitted form timestamp becomes Case CreatedDate via Salesforce's audit field — original submission time is preserved in Original_Submission_Date__c for reporting continuity.

Every Field2Base Region on a form template becomes a Salesforce custom field on the Case object. Region names are converted to valid API field names (spaces removed, underscores added). Field type is mapped: text Regions → Text(255), numeric Regions → Number, date Regions → Date, dropdown Regions → Picklist. Fields must be created in Salesforce before the migration run.

Form templates map to Salesforce Case Origin values (e.g., 'Inspection Form' → Origin = 'Inspection') or to Record Types when different form types require distinct page layouts and pick-list values. One form template can generate one or more Record Types depending on how many unique Case types Field2Base captures.

Field2Base users who submitted forms map to Salesforce Contacts. Resolution happens by email match against existing Salesforce Contacts. Unmatched users are flagged before migration — your team either pre-creates their Contact record or assigns submissions to a fallback Contact flagged with the original Field2Base User ID in Source_System_User_ID__c.

Field2Base users assigned as form reviewers map to Salesforce Contacts separately from submitters. Review action and timestamp are preserved as a custom activity note on the Case record. A custom field Reviewer_Name__c stores the reviewer's name when they are not yet a Salesforce Contact.

Field2Base captures GPS coordinates on form submissions. This migrates to two Salesforce custom Number fields (Submission_Latitude__c and Submission_Longitude__c) on the Case object. Salesforce Maps can visualize these as Case markers on a map view if your org has the Salesforce Maps product enabled.

Photos and file attachments submitted with forms are downloaded from Field2Base storage and re-uploaded to Salesforce as Files attached to the corresponding Case record. File size limits apply — Salesforce Files default to 25MB per file; larger files require Salesforce CRM Content or an external storage integration.

Field2Base form submission status values map to Salesforce Case Status pick-list values. 'Draft' forms in Field2Base can be excluded from migration (they are not finalized) or mapped to a Salesforce Case Status value like 'New / Not Started'. 'Submitted' maps to 'New' or 'Working', 'Approved' maps to 'Resolved' or a custom closed status — value-by-value mapping required.

Field2Base Workflows (review-and-approval steps on form submissions) do not migrate. FlitStack AI exports each workflow definition — step sequence, reviewer assignment rules, and approval conditions — as a JSON reference document your Salesforce admin uses to rebuild equivalent Flow logic. This is a manual rebuild; no automated conversion exists.

Field2Base integrations built via the Data Integration Module connect form data to back-end SQL, ERP, or other SaaS systems. These connections require new Salesforce integrations — typically a Salesforce Connected App for API access or Salesforce External Data Sources for ODBC-style live queries. We document each active DIM/EDM connection for your integration team to rebuild.

Field2Base optionally links form submissions to a Company record (enterprise tier). This maps directly to Salesforce Account. Address, phone, and industry fields migrate to the corresponding Account fields. If no Company is linked in Field2Base, submissions land as Cases on a default 'Field Service' Account your admin specifies.