Migrate from Field2Base to Freshsales

Each Field2Base form submission containing a person name and at least one contact method (email address or phone number) is mapped to a Freshsales Lead. The submission's region values populate corresponding standard Lead fields or custom fields. The original submission timestamp is recorded as the Freshsales Lead creation date, and duplicate detection uses the submission ID.

Field2Base submissions that contain no person-level data — work orders, inspection reports, maintenance logs — map to Freshsales Tasks or Appointments depending on whether the submission has a scheduled date region. The Task subject carries the form template name for identification.

Field2Base Company records map directly to Freshsales Accounts. Company name maps to Account Name. Address regions map to Freshsales billing address fields. Domain/website maps to the Account Website field. Multiple Field2Base contacts associated with one company link to a single Account via Freshsales Contact-to-Account relationship.

When a Field2Base form captures a financial amount (via a numeric region), that data maps to a Freshsales Deal. The Deal Name is constructed from the form template name and submission ID. Amount maps to the Deal Amount field. Pipeline and stage require a Freshsales admin to pre-create a pipeline and map Field2Base status regions to Freshsales stage values.

Field2Base Users are matched to Freshsales Users by email address. Matching is required before form submissions can be assigned to Freshsales owners. Unmatched users are flagged in the migration plan — either invited to Freshsales or assigned to a default owner before migration runs.

Field2Base form templates with region fields that have no Freshsales standard equivalent require custom field creation in Freshsales Admin Settings. Each region (text, numeric, dropdown, checkbox, camera, signature) becomes either a Freshsales standard field if a match exists, or a custom field created before migration. We deliver a field creation checklist as part of the migration plan.

Many Field2Base forms contain a status region (such as Pending, Approved, Rejected, or Closed). These region values are mapped to Freshsales Deal Stage names or Lead Status pick-list values on a one‑to‑one basis. Because Field2Base status vocabularies are customer‑defined and vary per form template, each form’s status set requires a separate value‑mapping configuration in Freshsales Admin Settings before migration.

Field2Base photo regions, signature captures, and PDF attachments download from Field2Base cloud storage and re-upload to Freshsales Files, linked to the corresponding Lead, Contact, Account, or Deal record. File size limits apply — Freshsales enforces a 25MB per-file cap. Large photo batches are processed in batches to avoid timeout errors.

Field2Base Workflows define routing, approval chains, and downstream actions triggered by form submission. These do not have a Freshsales equivalent and cannot be migrated programmatically. We export the workflow configuration as a structured PDF blueprint showing trigger conditions, routing rules, and assigned reviewers. Your Freshsales admin uses this to rebuild equivalent automation in Freshsales CRM Workflows.

Field2Base GPS capture regions store latitude and longitude. If the submission is linked to a Field2Base Company, these coordinates map to the Account address fields in Freshsales. If the GPS data is not tied to a company, it becomes a pair of custom number fields (Latitude__c, Longitude__c) on the corresponding Freshsales record.