Migrate from JobTread to HighLevel

JobTread contacts migrate to HighLevel Contacts. All standard fields (name, email, phone, address) map directly. JobTread contact types (Customer, Lead) become HighLevel Contact tags or custom fields for segmentation since HighLevel has no native contact type field.

JobTread company records migrate to HighLevel Companies. Company name, website, address, and industry map directly. If a JobTread contact has no associated company, HighLevel creates an unlinked contact record — no default account assignment is needed.

JobTread jobs are the core migration object. Each job becomes a HighLevel Opportunity with the job name as Opportunity name, job status (Active, Completed, On Hold) mapped to HighLevel pipeline stages, and original job create date preserved in a custom date field. Job-specific fields (phase, address, start date, projected end date) migrate as Opportunity custom fields.

JobTread estimates (with line items, totals, and proposal status) map to Opportunities with custom fields for estimate total, accepted date, and version number. If the estimate has a detailed line-item breakdown, those items migrate to a custom Estimate_Line_Item__c object linked to the Opportunity — this preserves the full bid structure for reference.

JobTread's reusable Cost Catalog items (cost groups, unit prices, markup rates) become a HighLevel custom object so your team can reference standard costs when building new Opportunities. Alternatively, cost items migrate as Opportunity Product rows for job-specific pricing. Your admin chooses the structure before migration.

JobTread budgets (estimated cost vs. actual cost by line item) split into two HighLevel structures: summary totals (estimated total, committed cost, actual cost, variance) migrate as Opportunity custom fields for pipeline reporting; detailed line-item budget comparisons migrate as Budget_Line__c custom object rows linked to the Opportunity.

JobTread purchase orders (vendor, line items, status, total) migrate as a custom Purchase_Order__c object linked to the parent Opportunity (job). PO status (Draft, Sent, Received, Invoiced) maps to a pick-list on the custom object.

JobTread work orders (subcontractor assignments, scope, status) migrate as a custom Work_Order__c object linked to the parent Opportunity. Status values map to a custom pick-list matching JobTread's status flow.

JobTread tasks and reminders attached to jobs or contacts migrate to HighLevel Tasks. Task due dates, assigned users (resolved by email match), and completion status transfer directly. Open tasks migrate as pending; completed tasks preserve their completion timestamp.

JobTread documents (proposals, contracts, photos) attached to jobs or contacts re-upload to HighLevel Files and attach to the corresponding Contact or Opportunity record. File size limits apply per HighLevel's storage policy.

JobTread internal users resolve to HighLevel users by email match. Unmatched users are flagged before migration — your team either creates the HighLevel user account first or assigns their records to an existing fallback user. External portal-only JobTread users (clients, subcontractors) do not become HighLevel users.

JobTread vendors migrate as HighLevel Companies with a Vendor__c tag so workflows can distinguish them from customer companies. Vendor-specific fields (trade, W-9 status, insurance expiry) map to custom fields on the Company record.

JobTread Workflows (trigger-action automations on job creation, field updates, or date reminders) do not migrate. HighLevel's Workflow Builder uses a different trigger-action model. We export JobTread workflow definitions as a reference JSON so your HighLevel admin can rebuild equivalent automations using triggers like Opportunity Stage Changed, Custom Field Updated, or Task Completed.