Migrate from Husky Intelligence to Freshsales

Direct map. Husky leads carry first name, last name, email, phone, and source information — these move into Freshsales Leads with all standard fields preserved. Owner assignment is resolved by email match to a Freshsales user. Any custom fields on the Husky Lead object are audited and created as matching custom fields in Freshsales before migration runs, ensuring data continuity for any extended lead properties your team has configured.

Direct map. Husky customers (person-level records tied to sites and jobs) map to Freshsales Contacts. The primary site association is preserved as a custom field in Freshsales. Multi-site customers get their primary site recorded; secondary sites surface as custom note records or a custom module on the Contact.

Direct map. Husky companies map to Freshsales Accounts — company name, address, industry, employee count, and annual revenue all carry over. Parent-company relationships in Husky translate to Parent Account in Freshsales. Where a parent-company has not yet been migrated, the link is flagged for manual resolution or scripted auto-matching by company name after the parent record lands in Freshsales.

Husky quotes (line items with pricing, quantity, and product names) become Freshsales Deals with Products attached. The quote header fields — quote number, validity date, discount — migrate as custom fields on the Deal. Quote status (Draft, Sent, Accepted, Lost) maps to the corresponding Freshsales deal stage by value mapping.

Husky Jobs map to Freshsales Deals, but the mapping depends on job status. Completed jobs that represent revenue events become Deals with a Won stage and the actual amount. Open jobs map to an appropriate pipeline stage based on the job status pick-list. Job-specific fields (site, operative assigned, work type) are preserved as custom fields on the Deal.

Husky sites represent physical locations tied to customers. For single-location customers, the site address becomes the Account billing/shipping address in Freshsales. For multi-site accounts, sites beyond the primary require a Freshsales Custom Module (Enterprise plan) or are stored as custom fields with site name and address for reference.

Recurring service agreements in Husky map to Freshsales Deals with a custom recurring-flag field, billing frequency stored as a custom pick-list, and contract start/end dates as custom date fields. The associated customer and site link to the relevant Freshsales Contact and Account.

Freshsales has no native invoicing object. Husky invoices are preserved as Note records with invoice number, date, total amount, and line-item summary stored as custom fields. Accounting integration (QuickBooks or Xero) should be set up post-migration for ongoing invoice generation.

Husky's scheduling and operative dispatch data does not have a Freshsales equivalent. We export the schedule as a JSON reference file and map operative assignments to Freshsales Tasks with custom date/time fields and the operative name stored for rebuild guidance. Scheduling automation must be rebuilt using Freshsales Workflows or a dedicated field-service tool.

Timecard records (hours logged per operative per job) do not map to any standard Freshsales object. We preserve them as custom fields on the linked Deal or as entries in a Freshsales Custom Module (Enterprise) for reporting continuity. Post-migration, consider a dedicated time-tracking integration.

Husky stock items with part numbers, descriptions, and unit costs migrate to Freshsales Products. Inventory quantities and reorder thresholds are not transferable (Freshsales does not track inventory) — we preserve them as custom fields on the Product record for reference and suggest a separate inventory management integration post-migration.

Husky's fully customisable forms produce property sets that have no fixed schema. We audit every custom form in the source account, create matching custom fields in Freshsales on the appropriate object (Contact, Account, or Deal), and carry the values over. Forms that represent business-process records beyond simple properties are exported as JSON and surfaced in a migration report for manual recreation.