Migrate from Field Nexus to Microsoft Dynamics 365 Sales

Field Nexus Customers map to Dynamics 365 Accounts. Each customer record (name, address, billing details) becomes an Account with primary address fields populated from the source. Customers with multiple service locations generate multiple Account records, with the primary service address marked as the main Account and subsidiary locations linked via Parent Account.

Field Nexus stores contacts at the customer level and at individual service-location nodes. All contact records (name, email, phone, job role) migrate to Dynamics 365 Contacts. If a single person appears at multiple service locations, the contact lands once in Dynamics 365 with the most recently used email and role — secondary location associations are preserved as Account Contact Relationships.

Field Nexus Work Orders do not map to a native Dynamics 365 entity. We create a custom WorkOrder Dataverse table to hold job-level data: description, job type, scheduled date, assigned employee, status, and sign-off timestamp. Active or recently closed work orders also generate a linked Opportunity record so the sales pipeline reflects ongoing service commitments — the Opportunity Name references the WorkOrder ID and account.

Each line item on a Field Nexus Work Order (labor line, parts line, flat-fee service) migrates as an OpportunityProduct record attached to the Opportunity linked to the parent WorkOrder. Unit price and quantity map directly. Discount fields are preserved if populated in Field Nexus.

Field Nexus scheduling assignments (employee, time window, dispatch status) have no Dynamics 365 equivalent at the CRM level. We migrate scheduling metadata as custom fields on the custom WorkOrder table (AssignedEmployee, ScheduledStart, ScheduledEnd, DispatchStatus). If your team uses Dynamics 365 Field Service, these map to Bookable Resource bookings instead.

Field Nexus sign-off records (customer approval, timestamp, sign-off method) are preserved as a custom field (SignoffTimestamp, SignoffMethod) on the WorkOrder custom table. If the sign-off includes a document or image attachment, that file migrates as a Dataverse Note attached to the WorkOrder record.

Field Nexus invoices map to a custom FieldNexusInvoice Dataverse table unless your Dynamics 365 environment includes Business Central, in which case we generate a corresponding Order or Invoice record in Business Central. Invoice status (paid, overdue, voided) migrates as a custom choice field on the destination record.

Field Nexus timesheet data (hours logged per job, employee, date) has no Dynamics 365 Sales native equivalent. We create a custom TechnicianTimesheet table with lookup to WorkOrder and to the user/employee. If your organization uses Dynamics 365 Project Operations, these timesheet entries can route there instead.

Field Nexus custom objects defined via the Infor Nexus-style custom object API (with designs and relationship scripts) map 1:1 to custom Dataverse tables. Each custom object requires a custom table created in your Dynamics 365 environment before migration — we deliver the schema plan upfront so your admin pre-creates the tables with correct relationship cardinalities.

Field Nexus employees and technicians resolve to Dynamics 365 users by email address match. Unmatched employees are flagged before migration; your team either invites them to Dynamics 365 first or assigns records to a fallback owner. If you run Dynamics 365 Field Service, technicians become Bookable Resources with skill and territory attributes.

Field Nexus files attached to work orders, invoices, or customer records migrate as Dataverse Note records with the file attachment re-uploaded to the destination. File size limits of the destination environment apply (Dataverse default 128MB per file). Inline images in Field Nexus notes are downloaded and re-hosted as Note attachments.

Field Nexus dispatch rules, sign-off triggers, and scheduling automations are workflow constructs that do not exist in Dynamics 365 Sales. They cannot migrate. We export the Field Nexus workflow definitions as a JSON reference document your admin can use to rebuild equivalent flows in Power Automate or Dynamics 365's classic workflow engine.