Migrate from Field Nexus to HubSpot

Field Nexus client records map directly to HubSpot Contacts. Client name splits into HubSpot firstname and lastname where available; otherwise the full name populates FirstName and LastName remains blank. Client email, phone, and address fields map to HubSpot's corresponding standard properties. Primary company association migrates as a Contact-Company association.

If Field Nexus stores client business names separately from individual contacts, those map to HubSpot Companies. Company name, domain/website, industry, and employee-count fields map to their HubSpot equivalents. HubSpot Companies can have multiple associated contacts — we preserve the N:1 or 1:1 relationship from Field Nexus.

Field Nexus work orders decompose into HubSpot Deals. The work order title becomes Deal name; estimated or final job amount becomes Deal amount; work-order status (Scheduled, In Progress, Completed, Cancelled) maps to a HubSpot Deal pipeline stage via value mapping. The client contact becomes the primary Deal contact via Opportunity Contact Role.

Each Field Nexus status value maps to a corresponding HubSpot pipeline stage. Scheduled → Appointment Scheduled; In Progress → Working; Completed → Closed Won; Cancelled → Closed Lost. Custom status values require HubSpot admin to pre-create pipeline stages before migration runs. Stage-entered timestamps are preserved as custom datetime fields.

Field Nexus estimates map to HubSpot Deals with a pre-populated Deal name and amount. If the estimate has been sent to the client, we flag it as 'Proposal Sent' in a custom field and set HubSpot Deal stage accordingly. Estimate line items become a custom field or are stored as a multi-line text property for reference.

HubSpot has no native invoice object in Sales Hub. Field Nexus invoices migrate as a custom object (Invoice__c) with fields for invoice number, amount, status, and associated Deal. For simpler setups, invoice reference data stores as properties on the parent Deal. Payment status is preserved; actual payment recording requires HubSpot Payments or a connected accounting tool.

Field Nexus technician and staff records map to HubSpot Owners. Resolution is by email — each Field Nexus user email matches against HubSpot user email. Unmatched users are flagged before migration; the team either creates HubSpot users first or assigns records to a fallback owner. Active/inactive status on the technician maps to HubSpot user active flag.

Field Nexus equipment records do not have a HubSpot native equivalent. We create a custom object (Equipment__c) with fields for asset name, serial number, location, and service-history notes. Equipment is associated to the relevant Contact or Company via a custom lookup relationship field.

Field Nexus work-order activity history (status changes, technician notes, customer sign-offs) migrates as HubSpot Engagements. Timestamps, technician owner, and the activity description are preserved. These surface in HubSpot's contact and deal timelines. Rich-text formatting in notes migrates as plain text to avoid rendering issues.

Field Nexus custom fields on work orders (e.g., service type, priority level, dispatch zone) map to HubSpot custom properties on the Deal object. We create these as HubSpot custom properties during migration setup. Field type parity is maintained where possible — pick-lists become HubSpot option sets, number fields become number properties.

Field Nexus custom fields on client records (e.g., customer tier, preferred contact method, referral source) map to HubSpot Contact custom properties. Same field-type translation rules apply as with work orders. If the custom field is a reference to another object (e.g., linked equipment), we create a corresponding custom object in HubSpot with a lookup relationship.