Migrate from Workiz to HighLevel

Workiz Clients map 1:1 to HighLevel Contacts. Client name maps to Contact full-name (split into first/last if structured in Workiz), email to Contact email, phone to Contact phone, and address fields map to the Contact address compound field. Primary company association uses HighLevel's Company link.

Workiz Clients flagged as commercial entities (those with a business name in the company field) also create a HighLevel Company record. The Company record links back to the Contact via the Account-Contact relationship. Multi-client associations (Workiz allows one client per job) collapse correctly in this 1:1 model.

Workiz Jobs map to HighLevel Opportunities. The Job name becomes the Opportunity name, job amount maps to Opportunity MonetaryValue, and the scheduled date maps to Opportunity CloseDate. Job status (Scheduled, En Route, On Site, Completed, Canceled) maps to a custom pick-list field since HighLevel has no native job-status concept.

Workiz Leads that have not been converted to Jobs map to HighLevel Contacts tagged with 'Lead' source. If the Workiz Lead has an estimated value, it creates both a Contact and a placeholder Opportunity so your HighLevel pipeline reflects in-flight estimates.

Workiz Estimates (proposals attached to jobs) merge into the Opportunity record in HighLevel — the estimate total becomes Opportunity MonetaryValue and the line items go into an Estimate_Items custom object linked to the Opportunity. Estimate status (Draft, Sent, Approved, Declined) is stored as a custom field on the Opportunity.

Workiz Invoices do not have a native HighLevel equivalent. We create an Invoice custom object linked to the Opportunity (job) and populate invoice number, total, balance due, payment status, and payment date. Payment method (card vs. bank transfer via Workiz Pay) is stored as a custom field.

Workiz Items (the line-item catalog used in estimates and invoices) map to a HighLevel Products custom object. Item name, price, unit, and description map to matching custom fields on the Product object. This enables HighLevel's opportunity-product linking if you configure it.

Workiz job types (e.g., Repair, Installation, Maintenance) have no native HighLevel equivalent. We create a Job_Type__c custom pick-list field on the Opportunity object and populate the values from Workiz's active job type list during migration. The pick-list values are created in HighLevel before data lands.

Workiz job statuses (Scheduled, En Route, On Site, Completed, Canceled) do not exist in HighLevel. We create a Job_Status__c custom pick-list on the Opportunity object and populate each job's current status at migration time. Historical status transitions are not available — only the final status at migration is preserved.

Workiz assigns a technician (user) to each job. HighLevel Opportunities do not have a native assigned-technician field. We create a Tech_Assigned__c text field on Opportunity and resolve the Workiz user to a HighLevel user by email match, storing the name in the field. If no match exists, the Workiz user name is stored as a text string.

Workiz captures lat/lng on jobs. HighLevel Opportunities do not have a native geolocation field. We create Latitude__c and Longitude__c custom number fields on Opportunity and populate them from Workiz. HighLevel's map view will not render these coordinates natively — they are stored for reference and third-party integration use.

Workiz call recordings and call logs link to jobs and clients. HighLevel has no native call recording storage. We export the call log metadata (call duration, timestamp, direction, client name) as entries in a Call_Log custom object linked to the Contact. Audio files cannot be transferred — they must be re-downloaded from Workiz before cutover and stored externally.

Workiz tags on clients and jobs map directly to HighLevel Tags. Tags are preserved on both Contact and Opportunity records. If a Workiz tag applies to a job (e.g., 'urgent', 'rework'), the equivalent tag is applied to the corresponding HighLevel Opportunity.

Workiz custom fields on Clients, Jobs, Leads, Estimates, and Invoices each need evaluation. For pick-list custom fields, we create matching pick-lists in HighLevel. For text or number fields, we create the equivalent HighLevel custom fields on the target object. Complex nested Workiz custom fields (e.g., JSON blobs stored in notes) are preserved as-is in a Custom_Data__c text field.

Workiz Automations (trigger-action rules on Jobs and Clients) have no export capability. We document each Workiz automation in a written rebuild guide with screenshots and trigger-action steps, organized by the business outcome (e.g., 'send SMS when job status changes to Completed'). Your HighLevel admin uses this guide to rebuild in the Workflows builder. Automations must be rebuilt — they cannot be migrated.