Migrate from Fieldmagic to HighLevel

Fieldmagic customers map directly to HighLevel Contacts. Customer name becomes Contact name, email becomes Contact email, and phone becomes phone fields. The customer address maps to the Contact address fields. Customer IDs are stored as a custom field (FM_Customer_ID__c) on the Contact for traceability and delta-run deduplication.

Fieldmagic contact individuals (site managers, billing contacts) map to HighLevel Contacts with the same field names. Job title becomes HighLevel contact job title. If a contact has no associated customer in Fieldmagic, it lands as a standalone HighLevel Contact and can be linked to a Company record manually post-migration.

Fieldmagic company records map to HighLevel Companies. Company name, domain/website, industry, employee count, and annual revenue transfer as direct field mappings. HighLevel Company records serve as the parent record for associated Contact records and can hold custom fields for CRM-level reporting.

Fieldmagic sites — physical service locations with address, site manager, and site-type information — have no native HighLevel equivalent. We create a Site custom object in HighLevel with fields for site name, full address, site type, site manager contact, and the linked FM_Customer_ID__c. Each Site is then linked to the primary Contact or Company that manages it via a custom object relationship.

Fieldmagic asset types (categories of equipment: HVAC, electrical, plumbing) are mapped to a custom object called Asset Type in HighLevel. This preserves the classification hierarchy separately from individual asset records. The asset type name, description, and category fields transfer as direct text fields on the custom object.

Fieldmagic assets — individual equipment items with serial numbers, status, manufacturer, location, and warranty info — migrate as a custom object called Asset in HighLevel. The asset is linked to its parent Asset Type via a relationship field, to its Site via a site lookup, and to the Customer or Contact that owns it. Asset status (operational, under repair, retired) transfers as a pick-list custom field.

Fieldmagic jobs map to HighLevel Opportunities using a transformation layer. Job number becomes a custom field on the Opportunity (FM_Job_Number__c). Job type, status, priority, and description transfer as Opportunity custom fields. Job schedule date maps to a custom datetime field (FM_Scheduled_Date__c). Job total amount maps to the native Opportunity Amount field. The Opportunity is linked to the Contact or Company that is the job's primary customer.

Fieldmagic quotes (line-item pricing documents attached to jobs) have no native HighLevel equivalent. Quote PDFs are re-uploaded to HighLevel and attached to the corresponding Opportunity or Contact record. Quote status (draft, sent, accepted, rejected) is preserved as a custom pick-list field on the Opportunity if it exists in Fieldmagic. Quote templates and formatting must be rebuilt in HighLevel's template builder post-migration.

Fieldmagic tasks (internal work items linked to jobs or contacts) map to HighLevel Tasks. Task subject, description, due date, and completion status transfer as direct field mappings. Task owner is resolved by email match against HighLevel users. Tasks without a HighLevel user match are assigned to a fallback owner and flagged for admin review.

Fieldmagic scheduling records (technician assignments, time blocks, resource allocations on a drag-and-drop calendar) have no native HighLevel equivalent. The scheduling data — technician name, scheduled date/time, job number reference, and resource type — is preserved as a custom text field on the Opportunity (FM_Schedule_Reference__c) and as a linked Task. HighLevel's calendar is appointment-based (booking tool), not dispatch-based; teams needing real-time scheduling rebuild this capability separately.

Fieldmagic users (office users and mobile technicians) are resolved by email match against HighLevel users. Matched users are assigned ownership of their respective records (jobs, tasks, assets). Unmatched users are flagged before migration so your team can invite them to HighLevel or assign their records to a fallback owner. Fieldmagic's Office User vs. Mobile User distinction does not map to a HighLevel concept.

Any custom properties defined on Fieldmagic jobs are created as custom fields on the HighLevel Opportunity object. Custom pick-list values are rebuilt as pick-list options in HighLevel. Boolean and numeric custom fields map by type. All custom field definitions are exported from Fieldmagic during the discovery audit and delivered as a setup reference for your HighLevel admin before the migration runs.

Files attached to Fieldmagic jobs, quotes, or assets are downloaded and re-uploaded to HighLevel's file management system. Each file is attached to the corresponding Opportunity (for job files) or Contact (for document files). HighLevel's file storage limits per sub-account apply; large attachments are flagged before migration if they exceed plan limits.

Fieldmagic integrations with Xero and QuickBooks (accounting sync, invoice push) have no HighLevel equivalent and cannot be migrated. HighLevel has its own payment and invoicing capabilities but does not natively sync with Xero or QuickBooks. Third-party integrations must be re-established post-migration via Zapier, Make, or HighLevel's API if supported by the accounting platform.