Migrate from Field Harmony to HighLevel

Field Harmony jobs map to HighLevel Opportunities. The job name becomes the Opportunity name, total job value becomes the Amount, and job status (scheduled, in-progress, completed, cancelled) maps to a HighLevel custom status pick-list or pipeline stage. Job-created and job-updated timestamps are preserved as custom datetime fields on the Opportunity so service history is visible in HighLevel reports.

Field Harmony's customer record is a combined entity — it contains billing name, company name, phone, email, and address. We split this into a HighLevel Contact (person fields: name, email, phone) and a HighLevel Company (business fields: company name, website, industry, address). If the customer is a sole proprietor with no separate company, we create a Company record with the customer's name to maintain HighLevel's Contact-Company relationship model.

Field Harmony technicians map directly to HighLevel Users. We resolve each technician by email — if a HighLevel User account exists with a matching email, we assign the Opportunity owner to that User. If no match exists, we flag the technician for team assignment before migration and leave the Opportunity owner blank with a note field identifying the original technician.

Field Harmony job line items (service type, labor hours, parts used) have no direct HighLevel equivalent. We create a JobLineItem Custom Object with fields for job reference, service type, quantity, unit price, and part number. Each line item is linked to its parent Opportunity via a custom relationship field. This preserves parts-usage reporting and service-type breakdown that Field Harmony tracked natively.

Field Harmony stores service-site addresses separate from customer records. In HighLevel, the primary address lives on the Contact record. Service-site addresses that differ from billing addresses are migrated to a ServiceLocation Custom Object linked to the Contact, preserving site-level context for multi-location customers without cluttering the Contact's default address fields.

Field Harmony parts inventory — part number, name, description, quantity on hand, cost price — has no HighLevel standard equivalent. We create a Part Custom Object with these fields and link parts to JobLineItem records. Parts-consumed reporting is then achievable via JobLineItem-to-Part relationship queries in HighLevel. HighLevel does not have inventory management natively, so ongoing parts tracking requires a separate inventory tool or a custom HighLevel integration.

Field Harmony scheduled visits map to HighLevel Appointments — the appointment is linked to the Contact and the Opportunity. Technician dispatch notes (e.g., 'first visit — diagnostic') become a Task with a description and due date. Original scheduled start and end times are preserved as appointment datetime fields. If Field Harmony stores recurring schedules, each occurrence becomes a separate Appointment linked to the same Opportunity.

Field Harmony custom job-type pick-list values (e.g., 'Installation', 'Repair', 'Preventive Maintenance', 'Emergency') require value-by-value mapping to a HighLevel custom pick-list field (JobType__c). We generate the complete value map during the pre-migration audit and apply it during the Opportunity import so stage-reason reporting remains consistent.

Field Harmony urgency or priority flags (e.g., 1–3 scale or 'Low/Medium/High/Critical') migrate as a custom pick-list field Priority__c on the Opportunity. This is a direct field-to-field map with no transformation — we preserve the original label values verbatim and create matching pick-list options in HighLevel before import.

Field Harmony attachments and technician photos on jobs have no native HighLevel file attachment on Opportunities by default. We create a JobAttachment Custom Object that stores the file URL (hosted in HighLevel's file storage or as a reference link), a description, and a link to the parent Opportunity. Your team uploads files to HighLevel's file storage before migration or we re-upload them during the migration run.

Field Harmony tags applied to jobs or customers migrate as HighLevel Tags. Tags are a native HighLevel feature and map directly — no transformation required. We preserve tag names exactly and import them alongside Contact and Opportunity records so segmentation and workflow triggers based on tags remain functional from day one.

Field Harmony workflows, if any exist, do not migrate. HighLevel's Workflows engine uses its own trigger-action model (e.g., contact enters a pipeline → send email → wait 2 days → assign task) that is architecturally incompatible with Field Harmony's automation logic. We export your workflow definitions as a text reference document so your HighLevel admin can rebuild each workflow in the Workflow Builder. Automations are the most common reason teams underestimate migration scope — we flag this upfront.