Migrate from Fieldproxy to HighLevel

Fieldproxy jobs map to HighLevel Opportunities with a custom pipeline representing job stages. Original job create dates and close dates transfer as custom datetime fields since HighLevel's CreatedDate is set at migration time. Job status values require a value-mapping table to HighLevel's pipeline stage pick-list.

Fieldproxy customers map directly to HighLevel Companies. The primary address, industry, and billing information transfer to their corresponding HighLevel Company fields. Customer-level custom properties migrate as custom fields on the Company object. We preserve all customer metadata including tax IDs, payment terms, and service tier classifications through custom field creation. Related contacts automatically link to the parent Company via lookup relationships.

Fieldproxy contacts map to HighLevel Contacts. We link each contact to its primary Company via the CompanyId lookup. Contacts without a parent company receive a placeholder company record in HighLevel before migration — your admin can reassign later. During migration, we match contacts by email address to existing HighLevel users for owner assignment, and we transfer phone numbers, mailing addresses, and custom contact fields to preserve complete communication histories.

Fieldproxy technicians have no direct HighLevel equivalent. We map them to HighLevel Contacts with a Role field set to 'Technician', or optionally create a technician custom object for high-volume operations. Skill certifications and availability windows migrate as custom fields on the contact record.

Each Fieldproxy job-technician assignment becomes a HighLevel Opportunity Contact Role with the technician role. This preserves the link between the opportunity (job) and the assigned technician contact, enabling reporting on technician performance from HighLevel's opportunity view. Multiple technicians per job create multiple Contact Role entries. We include the job start time and skill match as custom fields on the Contact Role for scheduling and routing reference within HighLevel workflows.

Fieldproxy job line items (parts, labor, services) map to HighLevel Opportunity Line Items. Product name, quantity, unit price, and tax amounts transfer directly. HighLevel's line-item model supports description and quantity fields natively — no custom fields required. Discount codes and notes attached to line items in Fieldproxy map to the description field on each Opportunity Line Item, preserving billing context for your finance team.

Fieldproxy assets (equipment, vehicles, inventory) require a custom object in HighLevel since no native asset management exists. We create an Asset custom object with fields for name, type, serial number, status, and a lookup to the related Customer Company. The migration plan includes the schema definition for your admin to pre-create.

HighLevel has no native invoice object. Fieldproxy invoices migrate as a custom Invoice object built via the HighLevel custom_object API. Fields include invoice number, date, amount, status, and a lookup to the related Company and Opportunity (job). Your admin sets up the schema before migration runs.

All Fieldproxy custom fields migrate as HighLevel custom fields on the corresponding object, or as fields on a custom object when no standard object matches. HighLevel enforces that a field is created as either Contact or Opportunity type and cannot be switched — we plan the schema before migration to avoid re-work.

Fieldproxy notes and file attachments transfer to HighLevel Notes and Files respectively. File size limits (HighLevel default 25MB per file) apply — larger files are flagged for manual download links stored as URL custom fields. We maintain attachment associations by linking files to the parent record (Job, Customer, or Contact). Timestamps on notes preserve the original creation date for audit continuity, and attachments over 25MB are uploaded to your cloud storage with URL references migrated to HighLevel.

Fieldproxy tags on jobs, customers, and contacts map directly to HighLevel tags. Tags serve as the primary segmentation mechanism in HighLevel for workflows, smart lists, and campaign targeting. All tag names and associations transfer exactly, preserving your existing categorization structure. HighLevel tags are case-sensitive, so we maintain the original casing from Fieldproxy. Tags enable automated workflow triggers and audience filtering in HighLevel's marketing automation features.