Migrate from JobTread to Twenty CRM

JobTread Customers (the primary point of communication on jobs) map directly to Twenty People records. Name, email, phone, job title, and address fields carry over as direct one-to-one mappings. The owner's email address on each Customer record resolves to a Twenty workspace member for owner assignment during the import process.

JobTread Companies (client organizations, which may also include vendors stored as companies) map directly to Twenty Companies. Industry, employee count, website, and address fields migrate as direct or value-mapped fields. Portal-access companies from JobTread map as regular Company records in Twenty.

JobTread Jobs are the core revenue record and map to Twenty Opportunities. Job name, stage, amount, expected start date, expected end date, and address fields carry over. Construction-stage values (Estimate Sent, Proposal Signed, Job Started, Completed) require value mapping to Twenty Opportunity stage pick-list values defined in Twenty's workspace settings before import.

JobTread's construction-stage pick-list (e.g., 'Estimate Sent', 'Proposal Signed', 'Job Started', 'Completed') must map to Twenty's Opportunity stage pick-list. FlitStack delivers a stage-mapping plan based on JobTread's actual stage values; Twenty stages must be created in Settings → Data Model before the migration CSV is uploaded.

JobTread Estimates are standalone selling documents that often precede a Job. Each Estimate migrates as a Twenty Opportunity record with the estimate name as Opportunity name and the estimated amount as the Opportunity amount. The original estimate date is preserved as a custom datetime field. Line items from the estimate body are consolidated into a Note attached to the Opportunity.

JobTread Purchase Orders (issued to subcontractors and vendors) have no native equivalent in Twenty. FlitStack creates a Purchase Order custom object in Twenty with fields for PO number, vendor, total amount, status, and linked Job. The PO-to-Job relationship is preserved as a custom relation field pointing back to the Opportunity record.

JobTread Change Orders (approved scope additions or variations on a job) are created as a Change Order custom object in Twenty, linked to the parent Opportunity. Fields include change order number, description, amount, status, and approval date. The full change-order history is preserved on the Opportunity via custom fields and linked records.

JobTread file attachments (drawings, contracts, photos) are re-uploaded to Twenty's file storage and linked to the Opportunity record. The original JobTread file ID and file name are stored as custom text fields on the Opportunity so teams can cross-reference the source file during the transition period.

JobTread custom fields on Jobs (e.g., job costing budget, customer portal access flag, subcontractor portal flag) have no native Twenty equivalent. FlitStack creates matching custom fields in Twenty's Data Model before import. Fields are typed as text, number, select, or date based on JobTread's field definition.

JobTread owner assignment on Jobs, Estimates, and POs is resolved by matching the owner's email address against Twenty workspace members. Unmatched owners are flagged before migration — teams either invite them to Twenty first or assign records to a fallback WorkspaceMember. No record lands without a valid Twenty owner reference.

JobTread tasks and to-dos on jobs map directly to Twenty Tasks. Task title, due date, assignee, and completion status carry over. Tasks without a due date or assignee migrate with those fields blank. Tasks linked to a specific Job carry the associated Opportunity ID in Twenty.

JobTread Notes on Jobs, Estimates, or Customers map directly to Twenty Notes. The note body, author (from owner email), and creation date are preserved. Notes are linked to the appropriate Opportunity or People record based on the source attachment in JobTread.