Migrate from Husky Intelligence to HighLevel

Husky contact records — name, email, phone, address — map directly to HighLevel Contact fields. Original Husky create/update timestamps are preserved as custom datetime fields since HighLevel's CreatedAt is set at migration time. Owner resolution uses email matching against HighLevel user accounts.

Husky company records map to HighLevel Company objects. Company name, domain, industry, employee count, and annual revenue fields map directly where present in Husky. Parent-child company hierarchies in Husky translate to HighLevel Company relationships — circular references are flagged before migration commits.

Husky job records translate to HighLevel Opportunities in a designated pipeline. Job status (Pending, In Progress, Completed) maps to pipeline stage values. Job amount or quoted price maps to Opportunity monetary value. Each Husky job type can be assigned its own HighLevel pipeline for workflow segmentation.

Husky's built-in quote and estimate functionality has no direct HighLevel equivalent. Quotes migrate as a HighLevel Custom Object with line-item custom fields (item description, quantity, unit price, total). For ongoing quote management, a HighLevel Workflow can be configured to replicate quote-to-job logic post-migration.

Husky service agreements — including contract terms, renewal dates, and coverage scope — have no native HighLevel object. We create a Service_Agreement__c custom object in HighLevel with custom fields for contract start/end dates, coverage tier, and linked contact/company. Renewal date triggers can be reconstituted as HighLevel Workflow reminders.

Husky site records representing physical locations associated with jobs become a Location__c custom object in HighLevel with address fields, site name, site-type classification, and access instructions. Jobs and service agreements are linked to Location records via HighLevel custom object relationships. Location records must be migrated before job records to ensure valid foreign-key references; otherwise Opportunity records will reference null lookups, breaking the location audit trail.

Husky timecard data — operative name, job reference, hours worked, date — migrates to a Time_Entry__c custom object. Timesheet reporting can be rebuilt in HighLevel via custom reports against this object. HighLevel's task management (Tasks) can supplement time tracking for service calls if a native timesheet is not required.

Husky leads that have not yet converted to jobs map to HighLevel Contacts tagged with a 'Husky Lead' tag. Lifecycle stage equivalents from Husky (New, Contacted, Qualified) are stored in a custom pick-list field on the Contact record for segmentation and reporting in HighLevel. Unconverted leads are identified by checking for absence of a linked job record, and the tag is applied automatically during migration.

Husky notes attach to the corresponding HighLevel Contact or Company record preserving the original creation timestamp and author. File attachments are downloaded from Husky's storage and re-uploaded to HighLevel's file storage with the same filename. Inline images embedded in notes are extracted and re-hosted within HighLevel's media library, with image references updated in the note body.

Husky tags applied to contacts and companies map 1:1 to HighLevel Tags. Tag-based segmentation used in Husky job categorization is preserved as a tag set in HighLevel, enabling equivalent workflow triggers and contact filtering without structural changes.

Husky contact-level custom properties — beyond standard fields — create corresponding custom fields in HighLevel. Field types are mapped: text to text, number to number, date to date, pick-list to choice field. Custom fields are created in HighLevel before migration so target fields exist at write time.

Husky job-level custom fields (e.g., job type classification, technician assignment rules, site access instructions) become custom fields on the HighLevel Opportunity record. Field naming follows HighLevel's camelCase convention for readability in the UI.

Husky invoicing records have no native HighLevel equivalent since HighLevel lacks a built-in invoicing module. We preserve invoice records as a custom Invoice__c object in HighLevel containing invoice number, amount, status, line items, and linked contact/opportunity reference. This preserves historical billing data for audit purposes, but active billing operations require connecting Stripe, QuickBooks, or another payment integration post-migration.