Migrate from Contractor+ to HighLevel

Contractor+ Clients migrate to HighLevel Contacts. Client name splits into First Name and Last Name fields. Email, phone, address, and custom fields map directly. The Contractor+ Client ID is stored in HighLevel's custom Source_System_ID__c field for traceability and delta-run de-duplication.

Contractor+ does not have a standalone Company object — clients ARE the company-of-record. We extract client records that represent businesses (not individuals) and create both a HighLevel Contact and a corresponding HighLevel Company record, linking them via Contact-Company association. Business type is inferred from the presence of a business name or website field.

Contractor+ leads that are not yet converted to clients migrate as HighLevel Contacts with a custom Source_Type__c field set to 'Lead'. Lead status and source information map to custom fields in HighLevel. Unconverted leads retain their original create date in Original_Create_Date__c.

Contractor+ Jobs map directly to HighLevel Opportunities. Job name becomes Opportunity Name. Job estimated value or quoted amount maps to Opportunity Amount. Job status (New, In Progress, Completed) maps to the HighLevel pipeline stage value. The Contractor+ Job ID is stored for reconciliation.

Contractor+ job status values (New, Scheduled, In Progress, On Hold, Completed, Cancelled) are mapped value-by-value to HighLevel Opportunity pipeline stages. We create a HighLevel pipeline named after the Contractor+ job workflow and apply the same stage sequence. Stage-enter timestamps from Contractor+ are preserved in custom datetime fields in HighLevel.

Contractor+ estimates are line-item documents with quantities, unit prices, and totals. Each estimate line item migrates as a HighLevel Opportunity Product entry linked to the corresponding Opportunity. The estimate document reference (estimate number, date, status) is stored in custom fields on the Opportunity. If estimate totals differ from job amount, both values are preserved.

Contractor+ invoices are standalone financial documents. We create a HighLevel Custom Object named 'Invoice' with fields for invoice number, issue date, due date, total amount, status (Paid/Unpaid/Overdue), and a link to the related Opportunity (the Job). Paid invoices get a custom Paid_Date__c field. Unpaid balances are preserved for accounts-receivable reconciliation.

Contractor+ Work Orders are operational scheduling records. HighLevel does not have a native Work Order object, so we create a Custom Object named 'Work Order' with custom fields for work order number, assigned technician, scheduled date, job type, and status. Work Orders are linked to the parent Opportunity via a lookup relationship field.

Contractor+ team members (dispatchers, technicians, admins) are matched to HighLevel users by email address. Active HighLevel user accounts must exist before migration; we flag any unmatched owners so they can be provisioned before the cutover. Role and permission settings are destination-side configuration.

Contractor+ custom fields (text, number, date, dropdown) on clients, jobs, and estimates are created as matching custom fields in HighLevel on the respective object. Dropdown fields require value-by-value mapping if the pick-list options differ between platforms. All custom field definitions are documented in the migration plan before the migration run.

Contractor+ file attachments on jobs and clients are downloaded and re-uploaded to HighLevel Files associated with the corresponding Contact or Opportunity record. File size limits follow HighLevel's upload constraints. Inline images in notes are extracted and re-hosted as HighLevel file attachments.