Migrate from Teamwork CRM to Microsoft Dynamics 365 Sales

Teamwork CRM Companies map to Microsoft Dynamics 365 Sales Accounts. The company name becomes Account Name; address, phone, and website fields map directly. We extract Companies first in every migration run to establish the parent reference before any Contact or Opportunity import. The AccountID on Dynamics Contacts must be resolved before Contact insert, so Company records load as a prerequisite phase with a row-count reconciliation before the Contact phase begins.

Teamwork CRM Contacts map to Microsoft Dynamics 365 Sales Contacts with the parent AccountID resolved from the Company mapping phase. Standard fields (name, email, phone, job title, address) migrate 1:1. Custom Contact fields (short text, integer, dropdown types only, matching Teamwork's supported field types) map to equivalent Dataverse column types. Any Teamwork Contact without a matching Company is attached to a placeholder 'Unassigned' Account for reconciliation.

Teamwork CRM Leads map to Microsoft Dynamics 365 Sales Leads when the customer runs separate Leads and Opportunities pipelines. Lead status, source, and rating transfer to corresponding Dynamics Lead fields. Any lead-stage probability weights in Teamwork migrate as a custom field on Dynamics Lead. If the customer has qualified all leads into opportunities and does not use the Lead object, we skip this mapping and document the decision.

Teamwork CRM Opportunities map to Microsoft Dynamics 365 Sales Opportunities with the parent AccountID resolved from the Company mapping and the OwnerID resolved from the User mapping. Deal value, close date, and stage name transfer directly. The pipeline association in Teamwork maps to a Microsoft Dynamics 365 Sales Record Type and Sales Process that we configure in the destination org before migration. Closed-Won and Closed-Lost reasons from Teamwork migrate to a custom field on Dynamics Opportunity.

Each Teamwork CRM pipeline becomes a Microsoft Dynamics 365 Sales Record Type with a corresponding Sales Process. We pre-create the Record Type and deploy the Sales Process stage definitions to the destination org before any Opportunity records load. If the customer runs both a Leads pipeline and an Opportunities pipeline, we create separate Record Types for each.

Teamwork stage names and probability weights map to Microsoft Dynamics 365 Sales stage names and probability percentages within the target Sales Process. Stage sort order preserves from Teamwork. If Teamwork stages have custom names not present in the default Dynamics stage set, we add them as custom stage values within the Sales Process rather than reusing a default name that does not match the customer's pipeline semantics.

Teamwork call activities map to Microsoft Dynamics 365 Sales Task records with TaskSubtype set to Call. Call duration, disposition, and assignee transfer to custom Task fields. The ActivityDate is set to the original Teamwork timestamp to preserve timeline ordering. The Task's Regarding lookup resolves to the migrated Contact or Opportunity.

Teamwork meeting activities map to Microsoft Dynamics 365 Sales Event records. Start time, end time, location, and description transfer directly. Attendees resolve to Contact or User references in Dynamics. Event is linked to the parent Account or Contact via the Regarding lookup.

Teamwork task activities map to Microsoft Dynamics 365 Sales Task records with status (open, completed), priority, and due date preserved. Task assignment migrates by resolving the Teamwork owner ID to the Dynamics User ID via the email-based user mapping. The Task's Regarding field points to the migrated Contact or Opportunity.

Teamwork CRM Owners map to Microsoft Dynamics 365 Sales User records by email address. We extract all distinct owner IDs referenced on Contact, Company, Opportunity, and Activity records. Owners without a matching Dynamics User go to a reconciliation queue for the customer's admin to provision before record import resumes. This is a prerequisite gate: no Opportunity or Contact import proceeds until owner resolution is complete.

Teamwork CRM custom fields of type short text, integer, and dropdown migrate to Dataverse custom columns on the corresponding entity (Contact, Company, Opportunity, Lead). Multi-select, date, and boolean custom fields are not supported by Teamwork CRM natively, so there are no Teamwork fields of these types to migrate. We pre-create Dataverse columns before migration begins using the Dataverse Web API.

Teamwork CRM tags on Contacts and Opportunities migrate to Microsoft Dynamics 365 Sales multi-select picklist fields on the corresponding record type. We capture the customer's tag strategy during scoping: either tags become a multi-select picklist on the standard form, or tags are mapped to Dynamics Topics with TopicAssignment records for a more flexible segmentation approach.