Migrate from Field Squared to Salesforce Sales Cloud

Field Squared customer accounts map directly to Salesforce Account records. Multi-location accounts in Field Squared require Salesforce Account hierarchies (ParentId) or a custom Address Junction object — we deliver the mapping plan for your admin to configure before data lands.

Contact records migrate to Salesforce Contact with AccountId linking to the mapped Account. Primary contact email is used for Salesforce User matching. Secondary contacts without a primary account link are attached to a default 'Unassigned Account' or flagged for manual review.

Field Squared Tasks map to a custom WorkOrder__c object (preferred for FSM workloads) or to Case records for service-ticket semantics. We create the custom object with the App Builder field schema replicated as Salesforce __c fields. TaskType, Status, ScheduledStart, and ScheduledEnd are preserved as custom fields with original values.

If Field Squared contains line-item or parts-used records associated with tasks, these migrate to a custom WorkOrderLineItem__c object linked to the parent WorkOrder__c or Case via a lookup relationship. Each line item preserves quantity, unit price, part number, and description fields. Product2 linking is attempted where part SKUs match existing Salesforce products, creating a reference to the standard product catalog for pricing and inventory alignment.

Field Squared locations per account become Salesforce ShippingAddress fields on Account (primary address) plus a custom Location__c junction object for multi-location accounts to capture all secondary addresses. Location records without an address link are stored as custom location detail fields on the junction object. The junction object uses AccountId as the parent lookup and includes custom fields for location name, street address, city, state, postal code, and country to preserve the full hierarchical location structure from Field Squared.

Field Squared asset or equipment records map to Salesforce Asset, linked to the Account and optionally to a Contact for technician association. Serial number, install date, warranty expiration, and status fields are preserved. Asset relationships to locations require the custom Location__c junction object lookup to maintain the multi-location context from Field Squared. Where Field Squared stores maintenance history or service intervals, those values map to custom fields on the Asset record.

Field Squared document URLs are downloaded and re-uploaded as Salesforce Files attached to the parent record (Account, Contact, or WorkOrder__c). File size and type limits per Salesforce's native limits apply. Inline images in document descriptions are downloaded and re-hosted as Salesforce Files.

Field Squared's 30+ App Builder custom field types are mapped to Salesforce data types: Text, Number, Date, DateTime, Picklist, Checkbox, Currency, URL, and others. Each custom field in Field Squared requires a corresponding __c field pre-created in Salesforce before migration. We deliver the schema plan with API names, data types, and pick-list values.

Field Squared users and technicians are resolved to Salesforce Users by email address. Unmatched users are flagged before migration — either invited to Salesforce first or assigned to a fallback user. Their task assignments map to OwnerId on WorkOrder__c or Case records.

Task notes in Field Squared migrate to Salesforce Notes attached to the parent WorkOrder__c or Case record. Original timestamps and technician author are preserved. Rich-text formatting in notes is handled as plain-text to avoid Salesforce rich-text rendering issues on standard Notes.

Task status-change history in Field Squared is preserved as a custom StatusHistory__c child object on WorkOrder__c, with Status value, ChangedDate, and ChangedBy fields to maintain a complete audit trail. Each status transition is recorded with its timestamp and the technician or user who made the change. Salesforce CaseHistory is also leveraged where Case object is used as the destination, preserving the native history tracking for service ticket lifecycle management across the migration.