Migrate from Field Squared to HubSpot

Field Squared customer records map directly to HubSpot contacts via email matching. We preserve original create dates as custom datetime fields (original_createdate_fs__c) since HubSpot's Createdate is set at import time. Email, phone, address, and job title transfer as direct property maps. Any custom fields on the customer record also migrate using field-type-aware mapping to equivalent HubSpot properties.

Field Squared company records migrate to HubSpot companies with direct field mapping for name, domain/website, industry, employee count, and revenue. Parent-child company hierarchies in Field Squared map to HubSpot's parent company field. Industry pick-list values require per-value mapping where option labels differ between the two platforms.

Field Squared work orders are the core migration object — they map to HubSpot tickets for service-related records. We preserve work order status, priority, scheduled start/end times, and the associated customer contact. Revenue-bearing work orders can alternatively map to Deals.

Work orders carrying pricing, billing amounts, or contract values route to HubSpot Deals instead of tickets. The work order amount maps to deal amount, and the work order completion date maps to the deal close date. Deal stage defaults to a configured pipeline stage unless your team specifies a mapping from Field Squared status values.

Field Squared tasks migrate to HubSpot tasks with original status (Not Started, In Progress, Completed), scheduled times, task type, and description all preserved. Task assignments resolve by email match to HubSpot owners. Completed task history populates the activity timeline on the associated contact or company record in HubSpot.

Field Squared documents attached to work orders, tasks, or customers re-upload to HubSpot as files associated with the matching contact, company, ticket, or deal record. We download originals from Field Squared's document store via API, preserve original file names and timestamps, and re-upload to HubSpot Files with associations restored.

HubSpot has no native asset management object, so we create a custom object named Asset with properties for serial number (serial_number__c), equipment type (asset_type__c), location (location__c), and operational status (status__c). Asset-to-customer associations are preserved via custom relationship properties linking each asset to the appropriate HubSpot contact or company.

Field Squared's 30+ custom field types (text, number, date, datetime, pick-list, multi-select, checkbox, file) each map to the closest HubSpot property type. Pick-list and multi-select fields require value-by-value mapping where option labels differ. Complex types like formula fields or geolocation are approximated to the nearest HubSpot type and documented in the field-level diff.

Field Squared user and technician records that don't have a corresponding customer contact record are created as HubSpot contacts with a 'FS_Technician__c' flag set to true. Active user email addresses are matched 1:1 to HubSpot user accounts for owner resolution on migrated records.

Field Squared workflow configurations (customizable business-process automation tied to work order state changes and task completions) do not migrate directly. We export all workflow definitions as a JSON reference document for your team to rebuild manually in HubSpot's workflow engine post-migration. Workflow rebuild is scoped separately and not included in standard data migration pricing.