Migrate from Vortex Field Software to Microsoft Dynamics 365 Sales

Vortex customer records typically contain both company information and a primary contact name. FlitStack splits these into a Dynamics 365 Account (for company name, address, industry) and a Contact (for the primary technician or service manager). Additional contacts from Vortex are created as related Contact records under the same Account.

Vortex work orders carry job description, site address, labor hours, parts consumed, and service status. Revenue-generating work orders map to Opportunity with custom fields for job type, work order number, and service-line details. Non-revenue service calls map to msdyn_workorder if the Dynamics 365 Field Service license is active.

Vortex asset records (serial number, model, installation date, maintenance schedule) map to the Dynamics 365 Field Service msdyn_asset entity. For assets that represent billable products or equipment under service contracts, FlitStack also creates corresponding Product records in Dynamics 365 to enable quote generation against the asset.

Vortex service history entries including maintenance notes, parts replaced, technician comments, and resolution details migrate as Dynamics 365 Annotations (notes) attached to the parent Account or Asset record. Each annotation preserves the original timestamp, technician name, work order reference, and any linked asset serial number. This maintains the complete service audit trail within the customer or asset context for future reference and compliance documentation.

Vortex site records storing service location address and contact details map to the Account's address fields in Dynamics 365. Multiple Vortex sites under one customer become multiple Address records on the single Account using the out-of-box address1 / address2 pattern.

Vortex technician records including name, email, phone, certifications, and skill sets map to Dynamics 365 SystemUser entities for CRM access and security role assignment. If the Dynamics 365 Field Service module is in scope, each technician also becomes a BookableResource record to enable scheduling board visibility and dispatch board assignment. This dual mapping ensures technicians can log into Dynamics 365 while maintaining their field service scheduling functionality.

Vortex parts catalog entries map to Dynamics 365 Product records with unit price, product type (inventory vs. non-inventory vs. service), and default unit of measure. When a work order maps to an Opportunity, parts used are added as Opportunity Product lines.

Vortex dispatch board entries (technician, time slot, work order, route) have no direct equivalent in base Dynamics 365 Sales. FlitStack preserves the mapping as a custom BookableResourceBooking record structure if Field Service is licensed, but the native scheduling UI requires manual rebuild by the Dynamics admin.

Any Vortex custom fields defined on the work_order object are recreated as Dataverse custom columns using the new_fieldname prefix on the target entity before migration. FlitStack validates data type parity between Vortex and Dynamics 365 (text, number, date, pick-list) and applies value-mapping for custom pick-list fields where option sets differ. This prevents data truncation or type conversion errors during the migration load.

Vortex service contracts and recurring maintenance agreements are mapped to a combination of Opportunity (for the contract's total value and stage) and a Quote record (for line-item detail). Contract expiry dates migrate as custom fields since Dynamics 365 does not have a native contract expiration tracker.

Vortex invoice records map to Dynamics 365 Invoice entities linked to the corresponding Opportunity and Account. Invoice status, invoice number, date, line item details, and total amount are preserved during migration. Historical paid invoices migrate as closed Invoice records, while outstanding invoices retain their current status for accounts receivable follow-up, ensuring complete billing history is available for financial reporting.

Vortex file attachments and photos associated with work orders or assets are downloaded and re-uploaded to the Dynamics 365 connected SharePoint document library under the parent Account or Asset folder structure. Original filenames and upload dates are preserved in SharePoint metadata.