Migrate from Successware to Microsoft Dynamics 365 Sales

Successware stores client contacts in a flat people file. We split each client into an Account (organization) and a primary Contact, with the Successware contact type preserved as a custom field (Original_Contact_Type__c). For sole-proprietor clients without a named organization, the Account name defaults to the contact's full name.

Successware relation, prospect, and vendor contacts also split into Account–Contact pairs. Vendor contacts are tagged with an Account type of 'Vendor' using a custom pick-list field (Account_Type__c) in Dynamics 365 so reporting can filter vendor accounts separately from customer accounts.

Successware jobs contain service type, technician assignment, job status, and revenue in a single record. We map jobs to Opportunities with Opportunity Type set to 'Field Service' and preserve the original Successware job ID as a custom field (SW_Job_ID__c) on the Opportunity. Job status maps to a custom pick-list (Job_Status__c) with value-by-value mapping from Successware status labels. Technicians become Opportunity Owner references.

Each Successware PriceBook entry maps 1:1 to a Dynamics 365 Product. The PriceBook code becomes the Product number. Pricing tiers from Successware become Price List Items attached to the Product, preserving flat-rate and time-and-materials distinctions as separate price-list lines. Service descriptions transfer as the Product description field.

Successware employees and technicians are not direct CRM users. We match each employee by email address to a Dynamics 365 SystemUser record. Technicians who resolve to a SystemUser become Opportunity OwnerId values. Employees with no email or no matching SystemUser are flagged before migration so your admin can either invite them to Dynamics 365 or assign their records to a fallback owner.

Closed Successware invoices migrate as Dynamics 365 Invoice records linked to the corresponding Account and Opportunity (via SW_Job_ID__c). Line items map to Invoice Details referencing Products. Invoice status (Paid, Outstanding) is preserved using a custom field (Invoice_Status__c) since Dynamics 365 Invoice entity does not have a native paid/unpaid status pick-list.

Successware's A/R Aging Report captures open balances not tied to specific invoice records in a clean export format. We load this as a custom Dataverse table (SW_AR_Aging__c) linked to Account, preserving customer name, outstanding amount, and aging bucket (Current, 30/60/90+ days). For teams requiring full AR functionality, Business Central integration is recommended post-migration.

Successware notes attached to jobs migrate as Dynamics 365 Annotations linked to the corresponding Opportunity via SW_Job_ID__c. Original timestamps and the creating user's name are preserved in the Annotation's notetext and ownid fields. Rich-text formatting in Successware notes is stripped to plain text during load to avoid display issues in the Dynamics 365 rich-text note control.

Successware allows extended properties per record type. Each custom property maps to a new_* custom field on the appropriate Dynamics 365 entity using the most compatible field type (text, number, pick-list, or date). All custom field definitions are documented in the pre-migration schema plan so your Dynamics 365 admin can review and adjust field types before data lands.

Successware automations, scheduling rules, and business-process sequences are application-level logic not stored in the data export. FlitStack exports a structured JSON reference of Successware workflow definitions (trigger conditions, action types, and field dependencies) to serve as a rebuild blueprint for Power Automate or Dynamics 365 classic Workflow/Process Builder.