Migrate your JobTread data

Jobs are the top-level container in JobTread, housing the budget, schedule, tasks, documents, and all financial records. We map Jobs 1:1 and preserve the budget-first hierarchy that ties cost items to the job budget.

Customers are contacts linked to jobs and represent the client side of a project. We import them via CSV template or API and preserve contact details, company associations, and job history.

Leads are captured in the CRM before they become Customers. We migrate Lead records and preserve the lead-to-customer lifecycle stage as a custom property on the destination if the target platform has a separate Lead object.

Both vendor types are distinct objects in JobTread. We map them to the equivalent vendor objects in the destination CRM, preserving contact info, payment details, and any linked Purchase Orders or Bills.

Cost Items are line items tied to budgets; Cost Groups are category headers. These are migrated from the Cost Catalog. Custom cost items created per job require value-level mapping to ensure the destination uses the same naming conventions.

Estimates in JobTread can include selections, formulas, and parameters. We preserve the line item structure and pricing but note that complex formula logic may need manual review post-import in the destination platform.

Selections are the client-facing choice lists tied to budgets and estimates. We migrate selection templates and linked items, but the client portal associations require re-establishment in the destination system.

Purchase Orders link vendors to cost items and budgets. We preserve the vendor association and line items but flag that approval workflows are not transferable and must be rebuilt.

Work Orders are assigned to subcontractors or crews and tie to job budgets. We carry forward the task assignments and cost item links but note that crew scheduling data may need re-entry in the destination.

Bills are vendor invoices tied to Purchase Orders and budgets. We migrate bill records and payment status, but any existing payment records in the destination accounting system require separate reconciliation.

JobTread supports Custom Fields on Jobs, Customers, and likely other objects. We handle field-level mapping but note that custom field creation on the destination must be completed before the data import begins.

Workflows in JobTread generate irreversible actions with stored workflow/run IDs. We do not migrate workflows as objects because their trigger-and-action logic is tightly coupled to JobTread's internal event model. We provide a structured audit log of what workflows ran so the customer can manually rebuild them in the destination.