Migrate your Service Suite FSM data

Service Suite FSM manages work orders as the core job object, but no public schema defines required fields versus optional ones. We require a field-by-field discovery call before mapping to any destination platform's equivalent object.

The platform includes a CRM module, but whether customer records map to Companies, Contacts, or both is undocumented. We typically map these as Contacts with company affiliation preserved as a property.

Technician records include scheduling and dispatch assignments. We map these to the destination's Users or Resources object, preserving skill tags and availability windows where present.

Scheduling data links work orders to technicians with time windows. We extract schedule entries as standalone records and re-link them in the destination system post-migration.

Payment processing is listed as a feature. Invoice records exist but their structure and relationship to work orders must be confirmed during discovery before export.

No documented attachment API or export mechanism was found in the available research. We cannot confirm whether photos, signatures, or documents attached to work orders can be extracted. We flag this explicitly during scoping.

The platform likely supports custom fields given its bundled feature set, but no public data model confirms this. We treat all non-standard fields as requiring manual discovery and value-mapping.

Integration connections exist but configuration data, linked accounts, and sync histories are not independently exportable. We preserve integration references as metadata but do not transfer active sync states.