Migrate from Novo Work Order to Microsoft Dynamics 365 Sales

Novo contact records migrate directly to Dynamics 365 Contact entities on a one-to-one basis. Full name, email address, phone number, physical address, and any custom contact properties map directly to their corresponding Dataverse columns. Contacts in Novo that do not have an associated company link will be created as standalone Contact records in Dynamics 365 without a ParentCustomerId reference.

Novo company records map directly to Dynamics 365 Account entities. Address information, industry classification, and employee-count fields have direct counterparts in Dataverse. Parent-child company hierarchies in Novo are translated to Account.ParentId lookups in Dataverse — any circular references are flagged during validation and resolved before the migration batch commits.

Novo Work Order translates to Dynamics 365 Case (Incident). Work order number becomes TicketNumber; title becomes Title; description becomes Description; status and priority map via value-mapping to StatusCode and PriorityCode. The original created-on timestamp is preserved as a custom field since Dynamics 365 sets CreatedOn at insert time.

Dynamics 365 Sales Professional has no native asset entity. We create a custom Asset table (msdyn_asset or named Asset__c) in Dataverse with fields for asset name, location, condition code, and linked work-order history. Enterprise and Premium tiers support more complex asset schemas via the Field Service attachment.

Novo PM schedules (frequency, interval, technician assignment) have no native Dynamics 365 equivalent. We migrate the schedule definition as a custom Entitlement record or as fields on the custom Asset table, leaving the recurring-trigger logic to be rebuilt in Power Automate or Dynamics 365 Field Service.

Work order notes, comments, and communication logs in Novo map directly to Dynamics 365 Activities such as Task or Email records. Each activity is linked to the corresponding Case record via the regarding_objectid lookup field. Original timestamps from Novo and the assigned technician name are preserved on the migrated activity record for full audit continuity.

Labor hours and parts cost tracked on Novo work orders migrate as custom decimal and currency fields on the Case record. Line-item parts detail is stored as an Annotation attachment or as custom sub-grid rows if your Dynamics schema supports product-line linking on Cases.

Novo technicians and staff members map to Dynamics 365 SystemUser records. Owner resolution occurs via email matching: each Novo owner or technician email is matched against existing Dynamics 365 users. Any technicians that remain unmatched after the email lookup are flagged and held for admin review before the full migration batch commits to the destination system.

Any custom fields created in the Novo platform migrate as custom columns in Dataverse. The original field data type is preserved during migration including text strings, numeric values, date fields, and pick-list enumerations. Dynamics 365 Professional tier enforces a strict 15-custom-table limit that may require schema optimization — Enterprise and Premium tiers remove this ceiling entirely.

Files attached to work orders in Novo are downloaded and re-attached to the corresponding Case record as Annotation records. If your Dynamics tenant has SharePoint integration enabled, files are migrated to SharePoint Document Libraries with the case record as the folder parent.

Novo workflow rules, email templates, and notification triggers do not have a migration path to Dynamics 365. We export a JSON/YAML representation of every Novo workflow definition as a reference document for your Dynamics admin to rebuild in Power Automate.