Migrate from Husky Intelligence to Salesforce Sales Cloud

Husky customers hold both company and primary contact data in one record. We split this into a Salesforce Account (company fields) and a Contact (contact fields), with the AccountId stored on the Contact. Customers without a company name become Salesforce Contacts attached to a placeholder Account.

Husky sites represent physical locations tied to customers. Each site becomes an Account with the ParentId set to the primary customer Account. Address, site type, and site-specific custom properties migrate as custom fields on the Site__c object if multiple locations per customer exist.

Husky jobs are the core work records. We create a custom Job__c object in Salesforce with fields for job_id, status, priority, scheduled_date, job_type, assigned_technician, description, and site reference. Jobs link to the parent Account via AccountId. This is not a native Salesforce object — Service Cloud's Work Order is an alternative if your org has it licensed.

Husky's drag-and-drop scheduling and technician assignments have no direct Salesforce equivalent in Sales Cloud. We create a Technician__c custom object and link it to Job__c records via a lookup field. Technician name and contact details migrate as Salesforce Users when email matches exist.

Husky quotes (estimates) become Salesforce Opportunities with line-item details stored in custom fields or a Quote__c custom object. If your Salesforce org has CPQ licensed, we map to the native Quote object. Otherwise, quote totals, line items, and approval status become custom fields on the Opportunity.

Husky invoices carry financial records that do not map to standard Salesforce objects. We create an Invoice__c custom object with invoice_id, amount, status, issue_date, and linked OpportunityId. Salesforce Order objects can be used if your workflow involves order-to-cash, but invoice data itself is custom.

Husky custom properties are key-value pairs stored per record. We map named properties to Salesforce custom fields using the __c convention (e.g. Warranty_Expiry__c). Properties without a clear Salesforce analogue become JSON-stored fields on the record, with a rebuild reference exported for your admin.

Husky technicians and admins resolve to Salesforce Users by email match. Unmatched owners are flagged before migration — your team either creates Salesforce Users first or assigns records to a fallback OwnerId. No record lands in Salesforce without a resolved owner.

Husky file attachments (photos, signed forms, invoices) re-upload to Salesforce Files attached to the parent record. File size limits apply (Salesforce default 25MB per file). Inline images in notes are downloaded and rehosted in Salesforce's Files. Each file is pulled from the Husky export, validated against Salesforce's 25MB limit, and loaded into Salesforce Files via the ContentVersion API, preserving the original file name and MIME type.

Husky job notes, technician visit logs, and call records migrate as Salesforce Tasks (for notes and calls) or Events (for scheduled site visits). Original timestamps, related Job__c record, and owner preserved. Task WhatId links to the parent Job__c. We also set the WhoId for related contacts and assign TaskSubtype or Event Type to distinguish notes, calls, and visits, enabling accurate activity reporting.