Migrate your Salesforce Field Service data

Work Orders are the primary service record in Field Service. We migrate Work Order headers, status, priority, and custom fields. Line items and entitlement associations are preserved via lookup relationship fields. Scheduling is driven by related Service Appointments, not the Work Order itself.

Service Appointments are the scheduling and dispatch unit in FSL. We migrate scheduled date/time, assigned technician, geographic location, status, and duration. Gantt view data and capacity view assignments are included. This object has a 250-record batch limit for Enhanced Scheduling optimization.

Technicians are standard Salesforce Users with a Field Service resource role. We migrate user profiles, skill certifications, service territory assignments, and operating hours links. Skills are a separate object with many-to-many junction relationships that require explicit mapping.

Accounts map directly as standard Salesforce objects. Location accounts (customer sites) carry additional address fields relevant to dispatch routing. We preserve account-to-asset relationships and service entitlement links during migration.

Contacts map as standard Salesforce objects. For Field Service, the primary contact on a Service Appointment receives automated appointment notifications. We migrate contact roles and maintain the contact-to-account hierarchy.

Assets represent installed equipment at customer locations and link to Accounts. We migrate asset hierarchy, product associations, install dates, and lifecycle status. Asset-to-Work Order lookups are preserved as relationship fields.

Line items are standard Salesforce objects with a lookup to Work Orders. Custom pricing fields and product option configurations require field-level mapping because implementations vary widely in how pricing is handled across FSL and standard Salesforce.

Entitlements define service level agreements and link customers to Work Orders via entitlement processes. We migrate entitlement names, milestones, and business hours. Custom entitlement types and milestone configurations require value mapping against the destination org.

Service Territories define geographic dispatch zones and assign technician membership. We migrate territory shapes, associated operating hours, and member resources. Multi-territory hierarchies and nested territory structures require careful mapping to the destination's territory model.

Operating Hours define work windows for Service Territories and Technicians. We migrate time slots and link them to territory or user records. Time zone handling and holiday schedule associations must be explicitly mapped when crossing regions.

Skills and Certifications are custom objects with junction relationships to Technicians. We migrate skill names, certification dates, and expiry data. Skill-to-Work Order requirements require mapping both sides of the many-to-many relationship.