Migrate from Husky Intelligence to Microsoft Dynamics 365 Sales

Husky Jobs carry customer details, site location, operative assignment, and schedule time all in one record. We decompose each Job into a Dynamics 365 Account (customer), a Contact (site contact), and a Case (job record) with custom fields capturing operative, duration, and route data. For field-service-heavy setups, a Work Order is used instead of Case.

Husky stores no standalone Account entity — customer names live on Job records. We extract unique customer names across all Jobs, create an Account for each, and link all related Jobs to that Account via the CustomerId lookup. Address data from the Job's site fields populates the Account address.

Site-level contacts from Job records are created as Dynamics 365 Contacts linked to the parent Account. The Contact's email and phone come from the Job's contact fields. If a Job has no named contact, the Account's primary contact is used.

Husky Quotes map 1:1 to Dynamics 365 Quote entities — name, status, expiration date, and total amount transfer directly without transformation. Each Quote Detail (line item) stored as a JSON array on the Husky Quote becomes a Quote Detail child row in Dynamics 365. If the Husky Quote references products by ID, we cross-reference the Dynamics 365 product catalog or create minimal product records to preserve line-item accuracy.

Quote line items transfer as Dynamics 365 Quote Details: product name, quantity, unit price, tax, and discount all map to their corresponding Dataverse columns. If Husky stores a product ID, we look it up in the Dynamics product catalog or create a basic product record.

Husky Invoices transfer as Dynamics 365 Sales Orders. The Invoice status (paid, overdue, voided) maps to the Order status field. Line items transfer as Order Products. Partial payments tracked in Husky are recorded as a note on the Dynamics Order.

Husky operative names resolve to Dynamics 365 Bookable Resources by email match against active Dynamics users. If no match is found, the operative becomes a User record first, then a Bookable Resource, ensuring scheduling continuity. Unmatched operatives are flagged before migration.

Husky schedule time slots transfer as Bookable Resource Booking records in the Dynamics 365 Field Service context. Start time, end time, duration, and the linked Case or Work Order are preserved. If the Field Service app is not provisioned, times are stored as custom datetime fields on the Case.

Husky Sites carry an address, customer name, and site-level notes. We create a child Account record with the Site name for multi-location customers, or attach the address to the primary Account using the Address composite field. Site-specific notes migrate as a custom text field on the related Contact or Case.

Husky Timecards record operative, check-in time, check-out time, and hours worked. Each timecard becomes a Dynamics 365 Task or a custom Time Entry entity capturing the operative (as Owner), start/end timestamps, and hours. The Task is linked to the related Case representing the job performed.

Husky Routes with sequence, vehicle, and distance data have no direct Dynamics 365 equivalent. We create a custom Route_Planning__c table in Dataverse to store route name, sequence order, vehicle ID, and total distance. Route stops are linked to Bookable Resource Bookings via a lookup.

Husky Service Agreements (recurring contracts) transfer as Dynamics 365 Contracts or a custom Agreement__c table if the contract terms include custom pricing rules. Agreement line items map to Contract Lines or Quote Details depending on the agreement type.

Husky custom properties added to Jobs are replicated as custom Dataverse columns on the corresponding Case or Work Order entity in Dynamics 365. We maintain the original data type (text, number, date, picklist), preserve pick-list value sets, and carry forward any validation constraints encoded in the Husky property definition. This ensures custom reporting logic built on these fields remains functional after cutover.

Husky file attachments on Jobs, Quotes, and Invoices are downloaded from the source system and re-uploaded to the corresponding Dynamics 365 record's associated SharePoint document location or as a Dataverse Note attachment. File associations are maintained so the attachment appears in the correct record's timeline. Microsoft SharePoint's 15 GB per document library storage applies, and the standard 32 MB per file limit is enforced for individual uploads.