Migrate from ServicePower HUB to Microsoft Dynamics 365 Sales

ServicePower HUB customer records map directly to Dynamics 365 Sales Account. The Account record becomes the parent for all related Contacts, Cases, and service history. ServicePower's company name and contact details transfer as Account.Name, Account.Phone, and Account.Website. Parent-child customer hierarchies in ServicePower HUB map to Account.ParentAccountId.

Individual contact points within a ServicePower HUB customer map to Dynamics 365 Sales Contact records linked by AccountId lookup. ServicePower contact names, emails, phone numbers, and roles transfer directly. Multiple contacts per customer collapse into Contact records with the primary contact flagged via Account.PrimaryContactId.

ServicePower HUB work orders map to Dynamics 365 Sales Case (Incident) records. The Case.Title carries the work order number and description. ServicePower's work-order status, priority, and assigned technician map to Case.Status, Case.Priority, and Case.OwnerId respectively. Original work order number is stored in a custom Source_Work_Order_ID__c field for traceability.

ServicePower HUB parts used per work order do not map to any standard Dynamics 365 Sales field. FlitStack creates a custom Dataverse table (e.g., WorkOrderLineItem) linked to Case with fields for PartName, PartNumber, QuantityUsed, and UnitCost. This preserves full parts-usage history for warranty and billing audit trails.

ServicePower HUB technicians and contractors merge into two Dynamics 365 Sales constructs: BookableResource (for capacity and scheduling) and SystemUser (for record ownership). Email-matched SystemUser records get work-order ownership; BookableResource carries skill certifications, capacity bands, and work territories from ServicePower HUB.

ServicePower HUB tracks work order status transitions with timestamps (scheduled, en route, on-site, completed). These are stored as custom datetime fields on a Case audit entity or as a custom WorkOrderStatusHistory Dataverse table linked to Case. Original timestamps and status values are preserved exactly.

ServicePower HUB COD and warranty invoice records map to Dynamics 365 Sales Invoice. Invoice.Amount and Invoice.Tax transfer directly. Invoice status (paid, outstanding) maps to Invoice.StatusCode. Note that Dynamics 365 Sales invoicing is CRM-level; full accounting requires Dynamics 365 Business Central integration.

ServicePower HUB parts catalog items map to Dynamics 365 Sales Product records. Part number, name, description, unit cost, and vendor information transfer to Product.Number, Product.Name, Product.Description, Product.StandardCost, and Product.VendorName. Default stocking locations map to Product.DefaultWarehouse. Additionally, part categories are stored in Product.ProductStructure or a custom category field, and unit‑of‑measure (UOM) data transfers to the Product.Unit of Measure entity to preserve quantity rounding during work‑order processing.

ServicePower HUB schedule and route assignments map to Dynamics 365 Field Service BookableResourceBooking records. Each booking carries the technician BookableResource, the Case (work order), start/end times, and geographic territory. Requires Dynamics 365 Field Service license on the destination — FlitStack surfaces this as a prerequisite before migration.

ServicePower HUB warranty and third-party administrator (TPA) job references have no standard Dynamics 365 Sales equivalent. FlitStack creates a custom text field (Warranty_TPA_Reference__c) on the Case record to preserve the OEM or TPA job number associated with each work order.

ServicePower HUB photo attachments and documents on work orders migrate as Dynamics 365 Sales Annotation records (stored in SharePoint if SharePoint integration is enabled). File size limits per the destination apply; inline images from work order notes are downloaded and rehosted in the Dynamics 365 SharePoint document library.

ServicePower HUB's customer self-service portal activity logs (booking submissions, status checks) have no Dynamics 365 Sales native equivalent. These are preserved as a custom portal activity log entity linked to Case for reference. Rebuilding the self-service experience requires Power Pages or a custom Power App.