Migrate from Vonigo to Microsoft Dynamics 365 Sales

Vonigo contact records map directly to Dynamics 365 Contact. Phone, email, address, and job title fields transfer as-is. Vonigo contacts linked to a franchise or company map via the companyId lookup to the corresponding Account in Dynamics 365. Owner resolution matches Vonigo user email to a Dynamics 365 system user.

Vonigo company records map to Dynamics 365 Account. Business address, phone, website, and industry fields map directly. Multi-location companies in Vonigo map to a parent Account with child Accounts for each branch location using the Parent Account lookup in Dynamics 365.

Dynamics 365 Sales has no native work order entity. FlitStack creates a vonigo_work_order custom table in Dataverse with fields for work order number, status, scheduled date, technician assignment, service type, and site address. This table is accessible within Dynamics 365 Sales on Enterprise licenses; Professional license migrations must plan around the 15-table cap.

Each Vonigo work order line item becomes a record in a vonigo_work_order_line table with a lookup to the parent vonigo_work_order. Fields include service description, quantity, unit price, tax, and line total. Line items are migrated as separate records rather than a JSON blob to preserve reporting capability in Dynamics 365.

Vonigo invoices have no direct equivalent in Dynamics 365 Sales. If your organization also deploys Business Central, invoices migrate to the Invoice entity there. For CRM-only Dynamics 365 Sales setups, FlitStack creates a vonigo_invoice custom table capturing invoice number, date, customer link, total amount, status, and payment reference.

Vonigo payment records map to a vonigo_payment custom table with a lookup to the related invoice. Fields include payment date, amount, payment method, transaction reference, and status. Payment data is migrated for audit continuity even though Dynamics 365 Sales does not manage payment processing natively.

Vonigo users (dispatchers, technicians, office staff) are resolved by email match to Dynamics 365 system users. Unmatched users are flagged before migration — your team either provisions Dynamics 365 seats first or assigns records to a fallback owner. Role-based access in Vonigo does not map to Dynamics 365 security roles automatically; those must be configured post-migration.

Vonigo file attachments on work orders and invoices are downloaded and re-uploaded to the SharePoint document library associated with the target Dynamics 365 entity. Attachments are linked to the corresponding custom work order or invoice record. File size limits from Vonigo's storage and Dynamics 365's SharePoint constraints both apply.

Vonigo stores unlimited custom properties as key-value pairs on any record. FlitStack audits the full property inventory and creates matching custom fields in Dynamics 365 on the appropriate entity (Contact, Account, or vonigo_work_order). Properties that cannot map cleanly become text fields or notes attachments for admin reference.

Vonigo franchisee locations map to child Accounts under a parent franchise Account. Territory assignments in Vonigo migrate to Dynamics 365 Territory records and are linked to the relevant Accounts. Territory-based reporting in Dynamics 365 then reflects the same geographic breakdowns your Vonigo setup uses.

Vonigo service appointments map to a custom vonigo_service_appointment table linked to the work order and technician. Native Dynamics 365 Calendar Events are contact-centric and not suited for field-service scheduling — the custom table preserves the full scheduling record including time window, technician assignment, and site address.