Migrate from Fieldy to HighLevel

Fieldy customer contacts map directly to HighLevel contacts. Fieldy stores name, phone, email, and address on contacts. HighLevel requires contacts to be associated with a company (company_id field) — contacts without a company in Fieldy attach to a default placeholder company in HighLevel during migration.

Fieldy company records (client businesses) map to HighLevel companies. Fieldy stores company name, domain, address, and custom properties. HighLevel companies have a Name, Website, and custom fields — address data migrates to the contact-level address associated with the primary contact or as a custom field on the company record.

Fieldy jobs are the core work-order record and map to HighLevel opportunities. The job name becomes the opportunity name, job amount maps to opportunity Amount, job status maps to a pipeline stage, and the close date maps to CloseDate. Job custom properties migrate as opportunity-level custom fields in HighLevel.

Fieldy's job-status workflow (e.g., New → Scheduled → In Progress → Completed → Invoiced) maps to a HighLevel pipeline with matching stage names. Each Fieldy status value becomes a HighLevel stage within the pipeline. Stage probability values are applied per stage during migration configuration.

Fieldy estimates have line items, totals, and approval status with no direct HighLevel equivalent. FlitStack migrates estimates as Opportunities with custom fields capturing estimate total (Estimate_Total__c), status (Estimate_Status__c), and line items serialized as a JSON custom field (Line_Items__c) for reference. Rebuilding formal estimates in HighLevel requires a third-party quoting tool or custom development.

Fieldy invoices carry line items, tax, total, and payment status. No native invoice object exists in HighLevel. FlitStack migrates invoices as Opportunities with custom fields for Invoice_Number__c, Invoice_Total__c, Amount_Paid__c, and Balance_Due__c. Actual invoice recreation requires connecting a HighLevel-supported payment provider (Stripe, Square) or rebuilding invoices manually.

Fieldy staff records include name, phone, email, certifications, and availability. HighLevel has no staff object — staff migrate as Contacts with a custom Role__c pick-list field set to 'Technician' or 'Field Staff'. HighLevel user accounts are separate and map by email match. Permissions are set via HighLevel user roles and profile assignments post-migration.

Fieldy stores service location addresses on jobs and contacts. HighLevel contacts have a native address block (street, city, state, zip, country). Fieldy location coordinates (lat/long) migrate as custom fields (Service_Lat__c, Service_Lng__c) since HighLevel does not store geocoordinates natively on contact records.

Fieldy tags on contacts, companies, and jobs map directly to HighLevel tags. Tags are a native HighLevel construct applicable to contacts and opportunities. Multi-value tags on a single Fieldy record preserve all values in HighLevel's tag array. Additionally, tags can be used for segmentation and automation triggers in HighLevel workflows.

Fieldy notes on jobs and contacts migrate to HighLevel notes attached to the corresponding opportunity or contact. File attachments are downloaded and re-uploaded to HighLevel's file storage. Note timestamps and author information are preserved in the HighLevel note record where supported.

Fieldy custom properties on contacts, companies, and jobs require corresponding custom fields in HighLevel. FlitStack creates contact-level and opportunity-level custom fields in HighLevel before migration. Field data types are preserved: text, number, pick-list, date, and checkbox map to HighLevel's custom field types respectively.

Fieldy workflow rules (e.g., auto-assign job to technician based on zip code, send SMS on job completion) have no direct equivalent in HighLevel. FlitStack exports Fieldy workflow definitions as a JSON reference document for manual rebuild in HighLevel's Workflows engine. The migration does not move automation logic automatically.