Migrate from Handyman to HighLevel

Handyman customer profiles map directly to HighLevel Contacts. Every customer record carries name, phone, email, address, and service history. We preserve the original Handyman customer ID in a custom field on the Contact record for traceability during delta-run de-duplication. This ensures accurate reporting across both systems.

When Handyman stores business/corporate customer names alongside individual contacts, we split them: the business name becomes a HighLevel Company record, and the individual contact links to it via the Contact-Company association. Homeowner customers (individuals without a company) land as standalone Contacts with no Company link.

Handyman job records map to HighLevel Opportunities. Job name becomes Opportunity name; job amount or estimate total becomes monetary Amount. Job status (Scheduled, In Progress, Completed) maps to a HighLevel pipeline stage defined by your team before migration. Original job creation date preserved as a custom datetime field.

Handyman job status values are flat labels with no probability weighting. We map each status value to a named pipeline stage in HighLevel's Opportunity pipeline. Stage probability and forecast category are re-applied based on HighLevel's stage configuration. If your Handyman setup uses custom status labels, we map those value-by-value.

Handyman estimates attach to a job as a separate pricing document. We merge estimate data into the corresponding Opportunity: line items become Opportunity Product entries or custom text fields, and the estimate total flows into the Opportunity Amount field. Estimate status (Sent, Accepted, Declined) migrates as a custom pick-list field on the Opportunity.

Handyman job notes, internal comments, and service descriptions migrate as HighLevel Notes attached to the Opportunity. Timestamps and author information preserved. If a Handyman note contains action items flagged by the technician, those migrate as Tasks linked to the Opportunity with the original due date if set.

Photos, signed documents, and attachments on Handyman job records are downloaded and re-uploaded to HighLevel Files attached to the corresponding Opportunity. File size limits per HighLevel's storage configuration apply. Inline images in notes are extracted and re-hosted individually. All files retain their original filenames for straightforward identification.

Handyman technician and admin user accounts map to HighLevel Users by email address. Unmatched Handyman users are flagged before migration — your team either creates the HighLevel account first or assigns their records to a fallback user. Owner fields on Opportunities resolve to the matched HighLevel user.

Handyman service categories and tags (e.g., Plumbing, Electrical, HVAC) migrate as HighLevel Tags on the Contact and Opportunity. Tags preserve segmentation logic for future workflow triggers in HighLevel. Multiple tags per record supported natively. This tagging strategy supports segmentation for targeted marketing and workflow automation in HighLevel.

Handyman custom fields defined on job records require HighLevel custom fields on the Opportunity object. We create a corresponding custom field for each Handyman custom property, matching the data type (text, number, pick-list, date). Custom field labels and pick-list values are preserved exactly as configured in Handyman.

Handyman custom fields on customer profiles migrate as HighLevel custom fields on the Contact object. Phone-format custom fields, custom pick-lists for customer type, and referral source fields all create new custom contact fields in HighLevel. Data type conversion applied where Handyman types differ from HighLevel field types.