Migrate from Contractor+ to Twenty CRM

Contractor+ clients (contacts, leads, subcontractors) map directly to Twenty's People object. The People record holds name, email, phone, job title, and a companyId link. Contractor+ contacts without a primary company get assigned to a default placeholder company record in Twenty or a 'Unassigned' company to satisfy the foreign-key constraint. Original create timestamps from Contractor+ are preserved as a custom datetime field since Twenty's CreatedAt is set at import time.

Contractor+ companies (business accounts associated with clients) map to Twenty's Companies object. The companyId in Contractor+ serves as the unique identifier. Twenty's Companies object holds name, domain/website, industry, employee count, and location fields. Parent-company hierarchies in Contractor+ map to Twenty's ParentCompanyId field if present. Multi-contact companies collapse to one Company record with multiple linked People records via the companyId foreign key.

Contractor+ Jobs (the core project/deal record) map to Twenty Opportunities. The job name becomes the Opportunity name, job amount maps to Opportunity amount, and the job stage (Lead, Bidding, Awarded, In Progress, Completed) maps to Opportunity stage values. FlitStack creates a stage-mapping table between Contractor+ job statuses and Twenty's Opportunity stage pick-list. Job close date maps to the expectedCloseDate field. Contractor+ job type or trade category is preserved as a custom field or tag on the Opportunity.

Contractor+ estimates and quotes attach to Jobs as line-item data. Since Twenty has no native estimate object, FlitStack merges estimate data into the Opportunity record: total estimate amount maps to a custom Estimate_Amount__c field, and line items are preserved as a JSON-encoded custom text field or as a linked custom object (Estimate_Item__c) with quantity, unit price, and description. The original estimate date is preserved as Estimate_Date__c on the Opportunity.

Contractor+ invoices have no direct equivalent in Twenty CRM's standard object model. FlitStack creates a custom Invoice__c object in Twenty with fields for invoice number, amount, status (Draft, Sent, Paid, Overdue), issue date, due date, and linked OpportunityId. Invoice line items are stored as a related custom object (Invoice_Line__c) with product description, quantity, rate, and total. Invoice PDF attachments are re-uploaded to Twenty's file storage and linked to the Invoice__c record.

Contractor+ tasks and work orders map directly to Twenty's Task object. The task title, due date, assignee (via email match to Twenty workspace members), and status (Open, Completed) are mapped field-by-field. Task completion timestamps from Contractor+ are preserved in Twenty's completedAt field. Tasks linked to specific jobs in Contractor+ are linked to the corresponding Opportunity record in Twenty via the task's linkedId and linkedRecordId fields.

Contractor+ notes and client messages map to Twenty's Note object. Notes are linked to the relevant People, Company, or Opportunity record via the Note's linkedId and linkedRecordId fields. Original note timestamps are preserved in Twenty's createdAt. Rich-text formatting from Contractor+ notes is converted to plain text or preserved where the Note object's Body field supports it. Note authors are resolved by email match against Twenty workspace members.

Contractor+ file attachments (photos, contracts, PDF invoices) linked to jobs or clients are downloaded and re-uploaded to Twenty's file storage. Each file is linked to its parent record (Person, Company, or Opportunity) in Twenty. File names and original upload dates are preserved as metadata. Large files exceeding Twenty's storage configuration are flagged for review before migration commits.

Contractor+ custom properties on clients (trade licenses, insurance expiry, referral source) that have no direct Twenty equivalent are created as custom fields on the People object. FlitStack generates a custom field creation plan before migration: field type is inferred from Contractor+ data (text, number, date, or select), and the field is created in Twenty before data is loaded. Custom property values are mapped directly to the new custom field on each People record.

Contractor+ custom fields on Jobs (trade type, project address, PO number, work-site coordinates) migrate to custom fields on Twenty's Opportunity object. Like contact custom properties, FlitStack creates these fields in Twenty before the migration run. Contractor+ pick-list values on job fields are mapped to Twenty select options so that filtering and reporting in Twenty's kanban and list views remain consistent.

Contractor+ owner assignments (sales rep, project manager) are resolved by email match against Twenty workspace members. FlitStack builds an owner-resolution table: each unique owner email in Contractor+ is matched to a Twenty WorkspaceMember record by email. Unmatched owners are flagged before migration and assigned to a fallback Twenty user or marked as 'Unassigned' on the relevant record. The original owner name is preserved in a custom Owner_Source__c field for audit purposes.

Contractor+ workflows (job scheduling rules, Estimatic AI triggers, automated follow-up sequences) do not have an equivalent in Twenty CRM's automation model and cannot be migrated. FlitStack exports the workflow definitions as a structured JSON document that documents trigger conditions, actions, and field dependencies. This export serves as a rebuild reference for the Twenty admin or a FlitStack consultant to reconstruct equivalent automations in Twenty's workflow builder.