Migrate from Fieldproxy to HubSpot

Fieldproxy Customer maps directly to HubSpot Contact. The contact's email, phone, and name fields transfer as-is. If the customer has multiple site locations, each site becomes a separate Company record linked via association, and the contact gets assigned to the primary Company.

Fieldproxy's primary site for a customer becomes a HubSpot Company. Company name, address, phone, and domain fields map directly. HubSpot's Company record stores the billing address; site-specific address data migrates as a custom property if multiple sites exist for one customer.

Fieldproxy Sites represent service locations. Each site with a distinct address becomes a separate HubSpot Company record, associated to the primary Company via Parent Account or a custom association property. Sites with no separate address store location metadata as custom properties on the primary Company or Contact.

Fieldproxy Job records are the core migration object. Each Job maps to a HubSpot Deal, with the Fieldproxy job number stored as Source_System_ID__c. Job status (Scheduled, In Progress, Completed, Cancelled) maps to HubSpot dealstage via a value-mapping table — the specific stage names are configurable per pipeline at migration planning time.

Fieldproxy job statuses are mapped one-by-one to HubSpot deal stage values in the target pipeline. 'Completed' jobs map to Closed Won, 'Cancelled' maps to Closed Lost, and in-progress jobs map to the appropriate pipeline stage based on completion percentage. The mapping table is confirmed during the sample migration review before the full run.

Fieldproxy Technicians map to HubSpot User records by email address. The technician's name, email, phone, and skill tags migrate as HubSpot User properties. If a technician email has no corresponding HubSpot user at migration time, the record is assigned to a fallback owner and flagged for admin review.

Fieldproxy Quotes map to HubSpot Quotes linked to the corresponding Deal. Line items in the Fieldproxy quote (parts, labor) become HubSpot Line Items with product name, quantity, and price. If the HubSpot account does not have the Sales Hub Quote feature enabled, quotes are stored as custom properties on the Deal record.

Fieldproxy Invoices do not have a native HubSpot equivalent. Invoice number, amount, status (Paid, Overdue, Draft), and Stripe payment reference migrate as custom properties on the Deal record. Paid invoices retain the original payment date; the financial data is preserved for reporting continuity.

Fieldproxy activity logs (job notes, status changes, technician check-ins) map to HubSpot Engagement timeline entries on the Deal or Contact. Timestamps, owners, and notes body transfer with original values preserved. High-priority log entries are flagged with a custom property on the parent record.

Fieldproxy custom properties on Job records — such as job type, priority level, equipment serial number, or service category — require HubSpot custom deal properties to be created before import. Each custom property is assessed for data type (text, number, picklist, date) and mapped accordingly. Custom property creation is scoped in the pre-migration setup phase.

Fieldproxy Parts used on jobs require a split strategy. Parts with a SKU and pricing become HubSpot Products with the part name, SKU, and unit price. Parts without a SKU are stored as custom fields on the Deal (part_name__c, part_quantity__c). The mapping is determined by the presence of a part SKU in the source data.

Fieldproxy automation rules and workflow triggers do not have a direct HubSpot equivalent because HubSpot's workflow model operates on contacts, deals, and tickets rather than job dispatch logic. We export a structured JSON manifest of every active Fieldproxy workflow (trigger conditions, actions, recipients) as a rebuild reference document for the HubSpot admin or implementation partner.