Migrate from Field Pros to HubSpot

Field Pros Contact maps directly to HubSpot Contact. The primary company_id from Field Pros maps to the first HubSpot Company association via the associations API. Secondary company associations migrate as additional HubSpot company associations. Unassigned contacts (no company in Field Pros) land as standalone HubSpot contacts.

Field Pros Company maps 1:1 to HubSpot Company. The parent_company_id field maps to HubSpot's parent company association. Multi-tier company hierarchies in Field Pros are preserved by migrating the top-level company first, then child companies with their parent references updated to match.

Field Pros Deal maps to HubSpot Deal. The deal name, amount, and close date map directly. Deal stage maps as a custom property since HubSpot stores pipeline stages separately from the deal record. Each Field Pros deal links to its primary contact and company via HubSpot associations.

Field Pros pipelines map to HubSpot Pipelines. We create a HubSpot pipeline for each unique pipeline_id in Field Pros, then map the pipeline's stages into the HubSpot pipeline's stage definitions. Stage order and probability values are carried over as stage metadata in HubSpot's pipeline configuration.

Field Pros stage names map to HubSpot stage names per pipeline. Each pipeline stage from Field Pros becomes a named stage in the corresponding HubSpot pipeline. Stage probability and forecast category are applied from HubSpot's stage configuration or carried over as custom properties if Field Pros used non-standard values.

Field Pros owner records resolve to HubSpot Owners. Matching is done by email address — each unique owner email in Field Pros looks up the corresponding HubSpot user by email. Unmatched owners are flagged before migration and assigned to a fallback HubSpot user or created as HubSpot users pending team confirmation.

Field Pros tasks map to HubSpot engagements. The task title becomes the engagement subject, and the task description maps to the engagement body or notes field. Status, priority, and due date from Field Pros are preserved as HubSpot engagement metadata properties. Open and completed tasks retain their original completion status in HubSpot.

Field Pros notes map to HubSpot engagements of type 'note'. The note body text maps to the engagement body content. Original created_by and created_date timestamps are preserved as HubSpot engagement metadata. Notes attached to specific contacts or deals are re-associated via HubSpot's associations API after migration.

Field Pros file attachments are downloaded and re-uploaded to HubSpot Files. Each file's original name, upload date, and associated record are preserved as custom properties on the HubSpot File. Files are re-linked to their parent records (contact, company, or deal) using HubSpot's file associations API after upload.

Field Pros custom fields on the Contact object become HubSpot custom properties. Each custom property is created in HubSpot with the matching field type (text, number, date, picklist, checkbox) before migration. Field options and picklist values map value-by-value. The custom property internal name from Field Pros becomes the HubSpot property name.

Field Pros custom fields on the Company object migrate as HubSpot custom properties on the Company object. Multi-select picklist values in Field Pros map to HubSpot multi-checkbox properties. Number fields with specific decimal precision carry over their precision settings. Date fields use HubSpot's datetime property type with timezone preserved from the source.

Field Pros deal-level custom properties become HubSpot deal custom properties. Each property is created in HubSpot's deal property group with the matching data type before migration. Properties that tracked deal-specific metadata (e.g., renewal type, contract length) are preserved as text or number custom properties. Properties referencing other records (lookups) are flagged for custom mapping or stored as text identifiers.