Migrate from Field2Base to Zoho CRM

Field2Base users (field workers, admins, reviewers) map directly to Zoho CRM Users by email address match. Active Field2Base users become active Zoho users; the Owner field on migrated records references the matched Zoho User. Field2Base role assignments do not migrate — Zoho profile and permission sets must be configured separately.

If Field2Base submissions include a company or client name field, FlitStack extracts that value and creates a Zoho CRM Account record. Submissions that reference the same company name are deduplicated so one Account accumulates all related submission history. Submissions without a company name are routed to Contacts without an Account link.

Field2Base submissions that include named customer fields (name, email, phone) create Zoho CRM Contact records linked to the resolved Account. Email is the primary deduplication key. Contacts without an email are created as partial records with First Name and Last Name populated; the submission reference is stored for later enrichment.

Field2Base work order numbers and submission IDs map to Zoho CRM Deals if the submission represents a billable service event or a tracked job. The Deal Name defaults to the work order number; amount is derived from pricing fields if present in the form. Stage defaults to a configurable Zoho stage (e.g., 'Closed Won' or a custom 'Field Work Complete' stage).

Each Field2Base submission becomes a Zoho CRM record — either a Task (for simple form submissions) or a custom-module record in a 'Field Submissions' module. The mapping uses the form template name as the custom module or subform reference. Original submission timestamp becomes the Zoho activity datetime; submitters become the Task owner or custom-module record creator.

Field2Base stores photos, signatures, and scanned documents as submission attachments. FlitStack downloads each attachment and re-uploads it to the corresponding Zoho CRM record as an Attachment, linked to the Contact, Account, Deal, or custom module record. Zoho's 25 MB per-file limit is enforced; files exceeding this are uploaded to Zoho Drive and linked via URL.

Field2Base captures GPS latitude and longitude on each submission. Zoho CRM has no native geolocation field, so FlitStack creates two custom number fields — Submission_Latitude__c and Submission_Longitude__c — on the relevant Account or custom module. For high-volume GPS data, a Zoho Creator subform or Zoho Maps integration is recommended post-migration.

Each Field2Base form template (e.g., 'HVAC Inspection', 'Construction Safety Checklist') is mapped to a Zoho CRM Custom Module named after the template. Form regions become custom fields in the module. Submissions are records within that module, linked to the related Account and Contact. This preserves the full structure of the source form in Zoho.

Field2Base workflow status (Pending Review, Approved, Rejected) does not map to a Zoho native field. It migrates as a custom pick-list field (Submission_Status__c) on the custom module record. Zoho Blueprints must be created separately to replicate the approval routing logic.

Field2Base submission timestamps map to Zoho CRM Activity Date (for Tasks/Events) or to a custom datetime field (Submission_Date__c) on custom module records. Zoho's native Created Date reflects the migration timestamp, not the original submission date — the original timestamp is preserved as a custom field for reporting continuity.

Field2Base Basic Workflow enables one-step review-and-approve after form submission. Zoho CRM has no equivalent auto-migration path for this logic. FlitStack exports the Field2Base workflow definitions as a written specification document for your Zoho admin, who then builds the equivalent Blueprint in Zoho.

Field2Base's Data Integration Module (DIM) and Enterprise Dispatch Module (EDM) connect to back-end ERP, accounting, or scheduling systems via CSV, ODBC, API, or Web Services plug-ins. These configurations are proprietary and do not transfer. Zoho CRM integrations must be rebuilt using Zoho Flow, Deluge scripts, or Zoho's native connectors.