Migrate from Field Nexus to HighLevel

Field Nexus contacts map directly to HighLevel contacts. Email, phone, name, and address fields transfer 1:1. HighLevel's Contact object requires a CompanyId lookup — contacts without a primary company in Field Nexus are attached to a default placeholder company or flagged for manual assignment.

Field Nexus company records map to HighLevel companies through a direct field-to-field transfer. Company name, website, phone number, industry classification, and physical address fields migrate to their corresponding HighLevel company fields. Any Field Nexus company properties that lack a direct HighLevel standard field equivalent are identified during the pre-migration audit and created as custom fields on the Company object before the migration run begins.

Field Nexus work orders have no native HighLevel equivalent — they are migrated as a HighLevel Custom Object. We create a Work_Order__c custom object with custom fields for job status, scheduled date, assigned team member, job description, and source system ID. The custom object is linked to the migrated Contact and Company records via relationship fields.

Field Nexus invoices migrate as a HighLevel Custom Object (Invoice__c). Invoice line items are serialized into a JSON custom field or stored as a text blob since HighLevel has no native billing object. We preserve invoice number, status, issue date, due date, total amount, and the Contact/Company link.

Field Nexus estimates (quotes) migrate as a Custom Object (Estimate__c). Estimate status (draft, sent, accepted, rejected) maps to a custom pick-list field. Line items are serialized as with invoices. The Estimate__c custom object is linked to the Contact and Company custom objects for relationship continuity.

Field Nexus team members are resolved by email against HighLevel users. Matched users are assigned as owners on migrated records (Contacts, Companies, Work_Order__c, Invoice__c). Unmatched team members are flagged before migration — your team either creates HighLevel user accounts first or assigns their records to a fallback owner.

Any Field Nexus contact property that does not map to a standard HighLevel contact field is migrated as a custom field on the Contact object. Custom field type is inferred from the source data type (text, number, date, pick-list). Custom field names in HighLevel use the source property name with underscores replacing spaces.

Field Nexus company properties that lack a HighLevel standard field equivalent are systematically migrated as custom fields on the Company object. Numeric properties such as years in business, number of technicians on staff, annual service call volume, and similar quantitative metrics are created as number fields. Free-text properties including internal account notes, billing terms, and custom classification tags are migrated as text fields. The custom field creation checklist identifies each source property, its data type, and the corresponding HighLevel field type before migration.

Field Nexus call logs and notes map to HighLevel Tasks with Type set to 'Call' or 'Note'. Original timestamps and assigned team members are preserved. Emails logged in Field Nexus map to Tasks with Type='Email'. All activity tasks are linked to the parent Contact record in HighLevel.

Field Nexus scheduling data (job start/end times, dispatch status, assigned technician) migrates into the Work_Order__c custom object's custom fields. HighLevel's calendar and appointment features are separate — the scheduling data is preserved for reference but the dispatch workflow must be rebuilt using HighLevel's Workflows feature.

Field Nexus payment records update the status field on the migrated Invoice__c custom object (from 'unpaid' to 'paid') rather than creating separate payment transaction objects. The original payment date and amount are stored in custom fields on the Invoice__c record.

Field Nexus file attachments and job photos are downloaded from the source platform and re-uploaded to HighLevel's file storage, linked to the relevant Contact, Company, or Work_Order__c record using the Source_System_ID__c reference. File size limits per HighLevel's storage configuration apply and are checked before re-upload. Inline images embedded within notes are extracted, downloaded separately, and rehosted within HighLevel's file storage to maintain visual context in the migrated record history.