Migrate from WennSoft to Microsoft Dynamics 365 Sales

WennSoft Customers map 1:1 to Dynamics 365 Sales Accounts. Customer Number from WennSoft becomes an Account Number field for direct record matching. Multiple WennSoft customer sites collapse to Address records on the Account, preserving each site address with its own address type designation. Primary Customer flag determines the primary Address record in Dynamics, ensuring the main billing or headquarters address surfaces first in lookup views.

Each Location on a WennSoft Customer becomes a CustomerAddress record linked to the Account. Address fields (street, city, state, zip) map directly. Location-specific contact persons map to Contacts with the Location as a custom field or the Address link. Site name becomes Address Name in Dynamics.

Work Orders have no native equivalent in D365 Sales without Field Service. We create a custom WorkOrder table on Dataverse with fields for WO Number, Status, Priority, Scheduled Date, Assigned Technician, Service Type, and Problem Type. Work Order Status values map to a custom status-option set that mirrors WennSoft's lifecycle.

Job Cost detail lines (labor, materials, subcontractors) from WennSoft Work Orders become custom detail rows on the Dataverse WorkOrder record. Each line carries cost amount, bill amount, cost code, and line type. Cost-plus margin calculates as the difference. Total Work Order revenue maps to a custom Revenue field on the parent WorkOrder.

Closed Service Calls with completed work become Cases in Dynamics. Open Service Calls in progress become Cases with a custom In-Progress status. Technician notes and resolution summaries map to Case Resolution fields. Service Call type (preventive, corrective) becomes a custom Case Type picklist.

Equipment records contain serial number, model, customer link, location link, and maintenance schedule. Without D365 Field Service, we create a custom Equipment table on Dataverse. With Field Service, Equipment migrates to the native Asset table. Warranty expiration dates become custom fields on either entity.

Service contracts with coverage tiers, response-time SLAs, and included labor hours map to a custom Contract table. Contract line items for different coverage levels become detail rows. Bill-to frequency (monthly, quarterly, annually) maps to a custom billing frequency field. Unused hours balance becomes a custom remaining-credits field.

WennSoft Employees used as technicians map to SystemUser records in Dynamics if they need CRM login access. Field technicians who only use MobileTech map to Contacts with a custom Technician flag. Employee Number becomes User ID or Contact ID for traceability. Email addresses match for user resolution.

WennSoft pricing by call type, problem type, equipment type, and labor level maps to Dynamics Product records with tiered Price List Items. Billing rates become the List Price on Price List Items. Markup percentages from WennSoft's matrix require calculated fields or manual price-list configuration after migration.

TimeTrack data (hours by employee, work order, date) migrates to a custom TimeEntry table linked to the WorkOrder. Expense entries (mileage, materials, per-diem) migrate to a custom ExpenseEntry table. GP payroll export configuration does not migrate — teams must rebuild TimeTrack-to-payroll mapping in their new system.

WennSoft Cloud Document Storage files attach to the relevant Work Order or Equipment record as Notes in Dynamics. WennSoft's document naming conventions map to the Note Title field. Large files exceeding Dynamics attachment limits ( Dynamics default 10MB per file) require SharePoint or Blob Storage integration post-migration.

Posted invoices in WennSoft represent closed billing records. Dynamics 365 Sales Invoice records exist for open invoices connected to Opportunities. Historical posted invoices have no clean migration target — we preserve them as custom InvoiceHistory records on the Account for audit reference, but they do not become active Dynamics invoices.