Migrate your Field Services Workflow and Logistics data

Work Orders are the primary job container in FSM systems. Most platforms use a consistent schema with status, priority, scheduled date, assigned technician, and customer reference. We map Work Orders 1:1 and preserve custom status values as destination custom fields.

Service Appointments (Salesforce FSM) or equivalent scheduling blocks represent booked time windows. We export the full appointment record including time, duration, travel time, and linked Work Order reference. Scheduling windows map to destination calendar or booking objects.

Technicians are mapped to destination Users or Contact records with a technician role flag. We preserve certifications, service territories, and availability schedules. Where the destination lacks a technician object, we create a Contact with custom properties for skill and territory assignment.

Customer accounts and contact records are standard CRM objects. We map them directly and link existing relationships to Work Orders and Service Appointments. Billing contact and service address distinctions are preserved as separate fields.

Equipment and Asset records track serial numbers, model numbers, installation dates, and service histories. Asset-to-customer linking is preserved. Custom asset fields and manufacturer data require field-level mapping to destination schema.

Service contracts define SLA terms, coverage periods, and included service types. We export contract records and link them to the customer account. Billing frequency and tiered coverage levels map to destination contract or agreement objects.

Invoices are generated from closed Work Orders or time entries. We export invoice records including line items, tax, and payment status. Open invoices are flagged for cutover sequencing to avoid duplicate billing. Historical invoice PDFs are exported as attachments.

Technician time entries track labor hours, travel time, and billable versus non-billable classifications. We export time entries linked to Work Orders and map billable hours to destination billing objects. Rounding rules and overtime flags require value-level mapping.

Custom workflow forms store pre-job inspection data, parts replaced, and customer sign-off records. These are typically stored as custom objects or JSON fields. We extract form data and map it to destination custom fields or notes, preserving timestamps and technician attribution.

Photo attachments, before-and-after documentation, and signed forms are exported and re-linked to their parent Work Order or Asset records. File naming conventions are normalized to preserve job context. Large attachment volumes may require chunked transfer and storage planning.

Custom fields on Work Orders, Assets, and Technicians vary significantly between FSM platforms. We enumerate all custom properties during discovery, map them to destination equivalents, and flag any unsupported field types that require workaround handling.

Territory assignment rules and dispatch group membership control job routing. We export territory definitions and link technicians and service areas. Where the destination uses a different territory model, we translate grouping logic into the nearest equivalent.