Migrate your Field Squared data

Work Orders are the primary job container in Field Squared. The REST API exposes create, update, and list operations for Work Orders including status, assigned technician, location, and scheduling dates. We migrate Work Orders with full field fidelity using ExternalId for reconciliation.

Tasks are nested within Work Orders and represent individual job steps. The Tasks API supports custom fields (30+ types), scheduling windows, status transitions, and unscheduling by clearing ScheduledStart/ScheduledEnd. We preserve task order, custom field values, and task-type classifications during migration.

Documents are uploaded files associated with Work Orders, Tasks, or Customers. The Documents API handles both single and batch array operations. We migrate document metadata, associations, and file content, mapping them to the destination's attachment model.

Custom Fields are defined in the App Builder and support 30+ data types. The API requires knowing the internal field identifier to write values. We discover all custom field definitions via the API before migration, then map values by type to the destination field model, handling type conversions where the destination uses a different field type.

Field Squared's CRM module stores customer records. The platform does not expose a dedicated Customers API in its public documentation, so customer data is typically read from Work Order associations. We extract customer records from Work Orders, de-duplicate by name/email, and map to the destination CRM's contact or account object.

Technician records are tied to user accounts in Field Squared. The user licensing model ($70–$125/user/month) means technician records have associated cost implications in the destination. We map technician assignments to Work Orders and preserve schedule/availability windows, noting any inactive users that should not be migrated.

The Asset Management module ($125/user tier) tracks equipment, locations, and service history. Assets have hierarchies, maintenance schedules, and GPS coordinates. We migrate asset records, parent-child relationships, and linked service history, respecting the tier-gating of this module.

Service Contract Management is listed as a core feature but does not have a dedicated API endpoint in public documentation. Contract records are often stored as custom objects or linked to Work Orders. We extract contract data from related Work Order and custom field records and reconstruct the contract entity in the destination.

Inventory management tracks parts and materials used on Work Orders. Field Squared exposes inventory data through its API, but quantity-on-hand and warehouse location details require careful mapping to the destination's inventory schema, which may use different units of measure or location naming conventions.

Invoicing and billing records are generated from closed Work Orders. The platform integrates with QuickBooks for accounting, meaning some invoice data may live in QuickBooks rather than Field Squared directly. We export invoice records from Field Squared and coordinate with QuickBooks data if present to avoid duplication in the destination.

Work Orders and Assets carry GPS coordinates and location addresses. We extract structured location data including latitude, longitude, address components, and any geofence definitions, mapping them to the destination's address or location object.

Field Squared's Automation features (5 documentation articles) define workflow triggers and actions within the platform. These are configuration records that do not have a documented public API export. Migration of automation rules requires manual reconfiguration in the destination system. We document all discovered automation rules in a human-readable inventory for the customer to re-implement.

The Dashboard module allows users to create custom widget-based reports. Dashboard configurations and saved report definitions are not exposed via a documented API. We migrate the underlying data (Work Orders, Tasks, metrics) that feeds these reports and flag dashboard re-creation as a manual step.