Migrate from Husky Intelligence to Twenty CRM

Husky Contacts map directly to Twenty People. Every standard field — name, email, phone, job title — translates to the equivalent Twenty People field. Husky contacts without a primary company attach to a default placeholder Company in Twenty or land without a link until you run the company import.

Husky Companies map 1:1 to Twenty Companies. Company name, domain, industry, employee count, revenue, and address fields translate directly. Parent-child hierarchies map to the Twenty Companies relation field where you define the parent record explicitly. The migration tracks each mapped record ID for cross-system reconciliation and validation after load.

Husky Work Orders are the core FSM record and do not have a direct Twenty equivalent. We map Work Orders to Twenty Opportunities — the deal-tracking object — and append Husky-specific FSM fields as custom fields on each Opportunity. The Opportunity Name carries the Work Order reference; Opportunity Amount carries the billed value if applicable.

Husky work_order_status values (e.g. Scheduled, In Progress, On Hold, Completed, Invoiced) have no native equivalent in Twenty's Opportunity object. We create a custom select field Work_Order_Status__c on the Opportunity object and map each status value explicitly. Status-changed timestamps are preserved in a companion datetime custom field.

Husky's priority field on work orders — Low, Medium, High, Urgent — migrates to a custom select field Priority__c on the Opportunity object. The pick-list values are created in Twenty to match your active priority levels exactly. If your team uses custom priority names beyond the standard four tiers, each custom name is added as a pick-list option during the pre-migration schema setup.

Husky scheduling data — technician assigned, scheduled date, start/end time — has no equivalent in Twenty's standard objects. We create a custom TechnicianAssignment object with relation links to the Opportunity (Work Order) and to the WorkspaceMember representing the technician in Twenty.

Husky Sites store service-location data (address, contact person at site, site-specific notes). These map to a custom ServiceSite object in Twenty with a relation back to the Company and a link to the Opportunity representing the work performed at that location.

Husky tracks parts and stock consumed per work order. This maps to a custom PartsUsage object in Twenty with a relation to the Opportunity and fields for part name, quantity used, and unit cost. Parts inventory master data migrates as a separate Companies-adjacent custom object if your team maintains a stock catalogue.

Husky timecard entries per work order — technician ID, hours logged, date, and billable flag — have no native Twenty equivalent. We create a custom WorkTimeEntry object linked to the Opportunity and WorkspaceMember, preserving hours worked, original log date, and billable status as custom fields. The technician is resolved by email match against Twenty WorkspaceMembers.

Husky notes and comments attached to contacts, companies, or work orders migrate to Twenty Notes. Each Note links to the corresponding People, Company, or Opportunity record. Original create timestamps are preserved; note authors are resolved by email match against Twenty WorkspaceMembers.

Tasks and follow-up items in Husky migrate to Twenty Tasks. Due dates, assignees, and completion status carry over verbatim. Open tasks migrate as open; completed tasks migrate with their completion status and completion date so nothing slips through during cutover. Overdue tasks are flagged in the migration report for your team's review.

Husky invoices are billing records tied to work orders. In Twenty, invoice status and amount are stored as custom fields on the Opportunity record (Invoice_Status__c, Invoice_Amount__c). Full invoice PDFs are preserved as file attachments on the Opportunity; invoice line items are stored as a custom OpportunityLineItem custom object if your team needs granular billing detail.

Husky owner and user records are resolved by email match against Twenty WorkspaceMembers. Unmatched owners are flagged before migration — your team either invites them to Twenty first or assigns their records to a designated fallback WorkspaceMember so no migrated record lands without an owner.

Husky Service Agreements (recurring contract terms, SLA periods, covered sites) have no direct Twenty equivalent. We create a custom ServiceAgreement object with a relation to the Company and date fields for start, end, and renewal, preserving the agreement terms as a text field for reference.