Migrate from Husky Intelligence to Nutshell

Husky leads map directly to Nutshell's Lead object. Lead status, source information, and rating fields carry over. Custom form fields attached to Husky leads migrate to Nutshell custom fields on the Lead object. Owner assignment resolves via email match against Nutshell users.

Husky customers map to Nutshell People. Names, phone numbers, email addresses, and job titles transfer directly. Each customer's associated company record in Husky links to a corresponding Nutshell Company record via the Person-Company relationship. Original create dates and modification timestamps are preserved as custom datetime fields.

Husky company records map to Nutshell Company objects. Company name, domain, address, industry, and employee count fields transfer directly. Parent-child company hierarchies in Husky map to Nutshell's parent-company relationship field. Multi-location companies split into individual Nutshell Company records if they are tracked as separate entities in Husky.

Husky jobs are the primary non-equivalent object. Each job migrates as a Nutshell Deal with the job name as the Deal name, estimated value mapped to Deal amount, and job status mapped to Nutshell's pipeline stage pick-list. Scheduling dates and assigned technician data migrate as custom fields on the Deal since Nutshell Deals lack native scheduling fields.

Husky schedule records — which link a job to a technician and a time slot — translate to Nutshell Tasks or Activities attached to the corresponding Deal. Start time, end time, and assigned resource map to Task fields. Multiple schedule entries for a single job produce multiple Nutshell Tasks so the full dispatch history is preserved.

Husky timecard entries recording hours worked by field staff attach to the corresponding Job-Deal record in Nutshell. Billable hours, start/end timestamps, and technician identifier map to custom fields on the Task. Non-billable time entries are stored as separate Tasks with a timecard type flag for reporting separation.

Husky service agreements contain contract terms, renewal dates, and coverage scope. These fields migrate as custom fields on the associated Deal or Company in Nutshell. Recurring contract value maps to a custom currency field. Renewal date is preserved as a custom date field to trigger Nutshell workflow rebuilds post-migration.

Husky invoices are preserved as read-only reference data in Nutshell. Invoice ID, total amount, status, and issue date migrate as custom fields on the associated Deal. Line-item invoice details are stored as a JSON-formatted custom long-text field on the Deal for reference. Nutshell's built-in billing is not automatically linked — QB Online integration is configured separately.

Husky custom forms attached to customers or leads create destination custom fields in Nutshell. Field types (text, number, date, pick-list, checkbox) are mapped to the nearest Nutshell custom field type. Multi-step form data is flattened into individual custom fields on the target object. Form definitions are exported as a reference document for Nutshell admin rebuild if needed.

Notes attached to any Husky record (customer, company, job) migrate to Nutshell Notes attached to the corresponding destination record. Original author, timestamp, and note body are preserved. Rich-text formatting in Husky notes is converted to plain text or preserved where Nutshell's note format allows.

Files attached to jobs, customers, or companies in Husky are re-uploaded to Nutshell and attached to the corresponding record. File name, size, and MIME type are preserved. Attachments exceeding Nutshell's size limits are flagged before migration so the team can decide whether to exclude or compress.

Husky owner and technician user records resolve against Nutshell users by email address match. Unmatched users are flagged before migration so the team either invites them to Nutshell or reassigns their records to a designated fallback owner. No record lands in Nutshell without a valid owner assignment.