Migrate from Comarch Field Service Management to Salesforce Sales Cloud

Comarch work orders map 1:1 to Salesforce WorkOrder. The WorkOrderNumber in Salesforce auto-generates unless the source system's work order ID is preserved as a custom field (Original_Work_Order_ID__c). Scheduled date maps to Salesforce's ServiceDate field. Dispatch status maps to Salesforce's Status field using value mapping (Comarch status codes → Salesforce picklist values).

Comarch task-level line items within a work order map to Salesforce WorkOrderLineItem records linked by WorkOrderId. Each line item inherits the parent work order's AccountId and AssetId. Line item status, duration, and description map to WorkOrderLineItem's Status, Duration, and Description fields respectively. Unit price maps to UnitCost if parts billing is tracked.

Comarch customer records map to Salesforce Account. The Account object is created before WorkOrder records because WorkOrder requires an AccountId foreign key. Comarch's customer billing address maps to Account.BillingAddress; service site address maps to Account.ShippingAddress or to a separate Location record if geo-coordinates are required for Salesforce's Service Territory model.

Comarch equipment records linked to customers map to Salesforce Asset. The Asset's AccountId links it to the customer Account, and the InstallDate, Status, SerialNumber, and Product2Id fields map directly. Comarch maintenance history maps to a custom field (Last_Maintenance_Date__c) or to the Asset's related Entitlement records if SLA terms are preserved.

Comarch technicians cannot map directly to Salesforce User — they first need to exist as Salesforce Users (or be created as such) before a ServiceResource record can link to them via the RelatedRecordId field. We match Comarch technician email addresses to existing Salesforce Users. Unmatched technicians are flagged for admin decision: invite them to Salesforce first or assign to a fallback ServiceResource.

Comarch skill certifications attached to technicians map to Salesforce SkillRequirement junction records on ServiceResource. The SkillId field references a Salesforce Skill object that must be pre-created (e.g., 'HVAC-Certified', 'Electrical-Licensed'). Each skill assignment from Comarch creates a SkillRequirement record linked to the migrated ServiceResource.

Comarch dispatch records (technician assignments with time windows) map to Salesforce ServiceAppointment linked to the WorkOrder. The scheduled start/end times from Comarch map to ServiceAppointment's SchedStartTime and SchedEndTime. The assigned technician maps via ServiceResourceId. ServiceAppointment status maps from Comarch dispatch status using value mapping.

Comarch parts catalog items map to Salesforce Product2 records with IsActive=true and a PricebookEntry linked to the org's standard pricebook. Parts consumed on a work order line item map to WorkOrderLineItem with QuantityUsed and UnitCost. Bin location and warehouse ID from Comarch map to custom fields on Product2 (Bin_Location__c, Warehouse__c) since Salesforce's Location object is optional and requires additional setup.

Comarch service contracts with SLA terms map to Salesforce Entitlement and Contract objects. The Contract object holds the commercial terms (start/end dates, contract type), while the Entitlement object defines SLA rules (response time, resolution time) that can be linked to the Asset or Account. Comarch SLA priority levels map to Entitlement.Priority using value mapping.

Comarch regions or zones map to Salesforce ServiceTerritory records. Each ServiceTerritory has an OperatingHoursId reference and optionally a ParentTerritoryId for nested hierarchies. If Comarch stores geofence polygon data (lat/long bounds), that data can be stored as custom geometry fields on ServiceTerritory or as a custom Location-based object for use with Salesforce FSL's routing engine.

Comarch service checklist templates attached to work orders need reconstruction in Salesforce. The checklist structure (ordered steps with pass/fail or value-capture fields) can be modeled as a custom Checklist_Response__c object linked to WorkOrderLineItem, or stored as JSON in a custom Long Text Area field. We preserve the template name and the completed responses as structured field-value pairs.

Comarch e-signature captures from field technicians map to Salesforce Files (ContentVersion/ContentDocumentLink). The signature image is uploaded as a file linked to the WorkOrder. We also create a custom boolean field Signed_in_Field__c on WorkOrder to flag records where a signature was collected, and a custom date field Signature_Captured_Date__c for timestamp preservation.