Migrate from TeamWave to Microsoft Dynamics 365 Sales

TeamWave Contact records map directly to Microsoft Dynamics 365 Sales Contact. Standard fields (fullname, emailaddress1, telephone1, address) transfer via CSV-to-Dataverse column mapping. Lifecycle stage from TeamWave maps to a custom field tw_original_lifecycle__c on Contact because Microsoft Dynamics 365 Sales does not have a native lifecycle stage property. The Company-Contact link from TeamWave's company_id foreign key resolves to Account.customerid during staging.

TeamWave Company records map to Dynamics 365 Account. The company domain name becomes the Account.website field and is used as the dedupe key during upsert. Account is created before any Contact import so that the customerid reference is satisfied at Contact insert time. If the customer uses multiple Company-Contact assignments in TeamWave, we split these into primary (Account.primarycontactid) and secondary (Contact.accountid) relationships.

TeamWave Deals map to Dynamics 365 Opportunity. The deal pipeline name in TeamWave maps to an Opportunity salesprocessid we pre-create as a Dynamics 365 Business Process Flow. Stage names map to stageid, and deal value maps to estimatedvalue. Closed-won and closed-lost reasons from TeamWave custom fields become Dynamics 365 resolution fields or custom fields on Opportunity. Owner assignment from TeamWave deal.owner_id resolves to Dynamics 365 SystemUser.userid during staging.

TeamWave pipeline stages map to Microsoft Dynamics 365 Sales Process stages. We pre-create a Business Process Flow in the destination org that mirrors the TeamWave pipeline stage names, probabilities, and order. Stage probability percentages migrate as stagecategorycode values. Each Microsoft Dynamics 365 Sales Process is scoped to a single Business Unit so that stage values stay scoped per team.

TeamWave's single deal pipeline maps to one Microsoft Dynamics 365 Sales Process with a corresponding Business Process Flow. If the customer used TeamWave's multi-pipeline feature, each pipeline becomes a separate Sales Process and Business Process Flow in Dynamics 365, with Record Types assigned per pipeline to scope page layouts and stage values to the relevant line of business.

TeamWave Tasks linked to Projects or Contacts map to Dynamics 365 Task records. Subject, description, scheduledend (due date), prioritycode, and statuscode transfer directly. Assignee resolution uses the same email-to-SystemUser lookup as Deal owner resolution. Task-to-Project links from TeamWave's project_id foreign key cannot be preserved as a native relationship in Microsoft Dynamics 365 Sales ; we store the original project_id as a custom field tw_project_id__c on the Task record for reference.

TeamWave User records map to Dynamics 365 SystemUser by email match. We extract all TeamWave users referenced as owners on Deals, Tasks, and Projects and match by email against the destination org's SystemUser table. Any TeamWave user without a matching SystemUser goes to a reconciliation queue for the customer's admin to provision before production import resumes. The migration user account must have the Security Role needed to assign records.

TeamWave Projects have no native Microsoft Dynamics 365 Sales equivalent. If the customer uses Dynamics 365 Project Operations, we map Projects to msdyn_project records with client linked to Account. If Project Operations is not in scope, we re-create Projects as a custom tw_project__c entity with custom fields for status, start date, end date, and client (lookup to Account). Project assignments migrate as Task records linked to the project entity. We flag this decision during scoping and confirm with the customer before schema deployment.

TeamWave HR module employee records (name, role, department, basic metadata) do not map to any Microsoft Dynamics 365 Sales standard entity. We migrate them as Contact records with a custom field tw_employee_record__c set to true, or as a custom tw_employee__c entity if the customer also licenses Dynamics 365 Human Resources. Employee-to-manager relationships from TeamWave's org structure map to a custom lookup field on the Contact or custom entity.

TeamWave Calendar Events with linked Deal, Project, or Contact associations migrate to Dynamics 365 Appointment records. Subject, scheduledstart, scheduledend, and location map directly. The linked entity reference is resolved by cross-referencing the TeamWave object type and ID against the staged Account, Contact, and Opportunity IDs, then set as the regardingobjectid on the Appointment. Attendee lists from TeamWave events map to Dynamics 365 AttendeeSet records linked to the Appointment.