Migrate your Connect Field Service data

Work Orders is the primary job record in FSM systems, containing status, priority, site address, and assigned technician. The schema is well-documented across Salesforce, Dynamics, and Oracle. We migrate Work Orders with all standard fields and custom extensions intact.

Service Appointments represent scheduled time windows for work order execution. They link to Resources and Territories. We map scheduling windows and travel time data to equivalent destination objects.

Service Resources represent field technicians with skills, certifications, and geographic territories. Skills are often stored as multi-select fields or related objects requiring value-level mapping.

Customer accounts store billing and site locations. Multiple service sites per account require address-level splitting during migration to avoid geocoding failures.

Assets represent equipment under service contracts. Custom properties and parent-child hierarchies require recursive traversal to preserve maintenance history.

Territories define geographic zones for dispatch routing. Territory assignment rules differ between platforms and require logic translation.

Skills attached to Resources must be mapped to destination skill taxonomies. Missing skills in the destination require customer decision on whether to create them or skip the association.

Service pricing models vary significantly. Flat-rate, time-and-materials, and contract-based pricing require structural mapping to destination price book objects.

Technician-captured photos and signatures attached to Work Orders are stored as blobs or file references. We extract and re-upload to destination storage with reference links maintained.

Time tracked against Work Orders includes travel, labor, and parts. Aggregated totals vs. line-item records require customer scoping decision before migration.