Migrate from Fieldy to HubSpot

Fieldy contact records — including name, email, phone, and address — map directly to HubSpot contact properties using the same data types. Staff members flagged as customers are also created as HubSpot contacts, preserving their original creation timestamps and last‑modified dates so the full audit trail is available in HubSpot after migration.

Fieldy company entries — containing the company name, domain, address, and industry — map to HubSpot company properties using matching field names. Service‑site companies defined in Fieldy are linked to the primary customer company record in HubSpot, maintaining the hierarchical relationship between sites and the parent organization.

Fieldy's native job object has no direct equivalent in HubSpot, so we create a Jobs__c custom object and define fields that mirror the original schema: job name, status, type, priority, appointment time, technician assignment, and GPS coordinates. The original Fieldy job ID is preserved as a custom field (Source_System_Job_ID__c) to support traceability and to enable delta‑run de‑duplication during subsequent data loads.

Fieldy's status values — scheduled, in_progress, completed, cancelled — are mapped into a custom picklist field (Job_Status__c) on the Jobs__c custom object. Because HubSpot lacks native job‑status automation, each status transition rule must be rebuilt manually in HubSpot Workflows, with triggers defined for time‑based or action‑based changes to reflect the original scheduling logic.

Fieldy quotes represent pre‑service sales opportunities and are mapped to HubSpot deals, preserving the quote amount, status, and discount percentage as deal fields. We store the original quote status in a custom picklist field (Quote_Status__c) and the discount percentage in a custom number field (Discount_Pct__c) to keep all quote metadata intact after migration.

Multiple line items attached to a single Fieldy quote are consolidated into a HubSpot deal by storing a line‑item count in a custom integer field (Line_Item_Count__c). The detailed product names and descriptions for each line item are captured in a custom long‑text field on the deal record, ensuring the full quote context is preserved for reference and reporting.

Fieldy invoices, along with their totals, payment statuses, and amounts, migrate as custom fields on the associated HubSpot deal: Invoice_Total__c, Invoice_Status__c, and Amount_Paid__c. This approach merges separate invoice records from Fieldy into deal‑level billing fields, allowing your team to view payment history directly within the deal record without maintaining a separate invoice object.

Fieldy staff records are converted to HubSpot contacts with the Service_Technician__c checkbox set to true and a custom Role__c field capturing their title. Staff members who do not have a corresponding customer profile are created as contacts only, preserving their name, email, phone, and role information for workforce management within HubSpot.

Fieldy teams — which group technicians for scheduling and dispatch — have no native equivalent in HubSpot, so we either create a Teams__c custom object to store team details and link it to contacts via a junction relationship, or we attach a custom pick‑list field (Team__c) on the staff contact record, depending on the complexity of your team hierarchy.

Fieldy location records — containing the service address, city, state, zip, and country — are attached to the HubSpot company as standard address fields. GPS latitude and longitude captured in Fieldy map to HubSpot's native geo coordinates or are stored as custom number fields on the company record for use in routing and map‑based visualizations.