Migrate from Urban-Hawks to Microsoft Dynamics 365 Sales

Urban Hawks Account maps directly to Dynamics 365 Account, preserving the primary contact as a PrimaryContactId lookup. All standard address components—street, city, state, postal_code, and country—flatten into Dynamics' composite address field. Parent-account hierarchies translate via Account.ParentAccountId. Custom fields on Account are handled separately as custom columns, and any non-mapped attributes are flagged for review.

Urban Hawks Work Order maps to Dynamics 365 Sales Field Service Work Order — the native entity for field service records. Status values require explicit value-by-value mapping because the pick-list options differ between platforms. Technician assignment resolves by email match to Dynamics SystemUser.

Urban Hawks Asset maps to Dynamics 365 Field Service Customer Asset. Parent-child asset hierarchies are preserved via the CustomerAsset.ParentAssetId relationship — parents must migrate first and FlitStack sequences accordingly. Asset metadata (model, installation date) migrates as standard and custom fields.

Urban Hawks Contact maps to Dynamics 365 Contact. Urban Hawks stores full name as one field; Dynamics uses separate FirstName and LastName — FlitStack splits on the first space separator and stores the remainder in LastName. Account association migrates as Contact.AccountId lookup. Urban Hawks Contact without a company lands on a default account.

Urban Hawks custom fields on Account objects become Dynamics 365 custom columns created via the Power Apps solution explorer. Text fields map to Text, numbers to Number, dates to DateTime, and pick-lists to OptionSet — FlitStack applies type-aware mapping. Non-standard field types are handled with transformations documented in the migration plan.

Urban Hawks custom fields on Work Order migrate as custom columns on the msdyn_workorder entity. Type alignment (text, number, date, pick-list) is preserved. Fields that do not have a Dynamics equivalent are flagged as custom_field_required in the mapping plan so the Dynamics admin can pre-create them before the migration run.

Urban Hawks Technicians are not CRM contacts — they are operational records. FlitStack resolves each Urban Hawks technician by email match to a Dynamics 365 SystemUser. Unmatched technicians are flagged before migration so the admin can either invite them to Dynamics or assign their records to a fallback owner. Technician ID is preserved in a custom field for traceability.

Urban Hawks AR session records (session_id, duration_minutes, device_type, device_metadata) have no native equivalent in Dynamics 365 Sales. FlitStack creates a custom AR_Session table in Dynamics with custom columns for each AR property. The parent Work Order links via a lookup. Your admin configures the form and views post-migration.

Urban Hawks service tickets map differently depending on workflow type. Tickets that follow a customer-service path route to Dynamics 365 Customer Service Incident (Case). Tickets that represent field service dispatches route to msdyn_workorder. Priority and resolution timestamp migrate as custom fields. The split is determined during the mapping plan phase based on your workflow description.

Urban Hawks file attachments on records re-upload to Dynamics 365 SharePoint integration or Note (Annotation) entity. If your Dynamics tenant has SharePoint document management enabled, attachments land in the associated SharePoint library; otherwise they attach as Annotations on the parent record. File size limits per Dynamics apply.