Migrate from Husky Intelligence to HubSpot

Husky leads map directly to HubSpot contacts. If the Husky lead has an associated company or site, a HubSpot company is created first and the contact is linked via the company_id association. Owner is resolved by email match to a HubSpot user.

Husky jobs with a commercial amount become HubSpot deals. Jobs tracking service calls or maintenance without a dollar value become HubSpot tickets. Job status (e.g., Pending, In Progress, Completed, Cancelled) maps to a custom Job_Status__c property on the target record; stage-level reporting is rebuilt in HubSpot deal pipelines.

Husky quotes with line items map to HubSpot deal products. Quote status (Draft, Sent, Accepted, Declined) is stored as a custom Quote_Status__c property on the deal. Note that HubSpot native quotes require Sales Hub Professional or Enterprise; if your HubSpot tier is Starter, quote data is preserved as deal-line-note text.

Husky invoices with payment status, amounts, and dates have no native HubSpot equivalent. We migrate invoice records as a custom Invoice object in HubSpot (Sales Hub Enterprise) or as a structured set of custom properties on the associated deal. Payment status is preserved as Invoice_Paid__c (boolean) and Last_Payment_Date__c.

Husky sites store customer locations with address, site contact name, and notes. Each site becomes a HubSpot company record with the address in the Address_* properties and the site contact as the primary contact on the company. If one customer has multiple sites, each site maps to a separate HubSpot company.

Husky service agreements (recurring contract terms) map to HubSpot deals with custom properties for Contract_Start__c, Contract_End__c, and Recurring_Amount__c. These custom properties are created in HubSpot before migration, and the deal's associated company links the agreement to the customer record, preserving the relationship.

Husky users and field operatives are matched to HubSpot users by email. Unmatched users are flagged before migration — your team either creates the HubSpot user first or assigns records to a fallback HubSpot owner. Active/inactive status is preserved as a HubSpot User active flag.

Husky stock items map to HubSpot products with name, SKU, and price. Inventory quantities are stored as custom properties (Qty_on_Hand__c) because HubSpot products do not track inventory levels natively. If Husky tracks lot numbers or serialised items, that data is stored as a custom property.

Husky timecard entries (hours worked per operative per job) have no native HubSpot equivalent. We migrate timecard data as a custom Timecard_Entry__c object with date, hours, operative (User lookup), and job (Deal lookup) — available on HubSpot Sales Hub Enterprise. On lower tiers, hours are stored as a custom number property on the deal.

Every Husky custom field maps to a HubSpot custom property on the equivalent object. We preserve the original field label and data type, applying HubSpot's type constraints (e.g., single-line text → single-line text; date → date; numeric → number). Pick-list values in Husky map to HubSpot option sets value-by-value.

Husky files attached to jobs, quotes, or invoices are downloaded and re-uploaded to HubSpot Files. They are then associated to the corresponding contact, deal, or ticket record via the HubSpot file association API. File size limits of 25MB per file in HubSpot apply.