Migrate from Teamgate to Microsoft Dynamics 365 Sales

Teamgate People records map to either Salesforce-style Lead or Contact in Dynamics 365 depending on qualification status. Prospects and unqualified contacts map to Lead; sales-qualified contacts attached to an Account map to Contact. We define the split rule during scoping using Teamgate's custom lifecycle or status fields if present, and preserve the original People status in a custom field tg_original_status__c on both Lead and Contact for audit trail integrity.

Teamgate Company records map directly to Dynamics 365 Account. The Company domain or website field becomes Account Website, used as a dedupe key during import. Account is created before any Contact or Lead import so that the CustomerID or AccountId lookup is satisfied at insert time.

Teamgate Deals map to Dynamics 365 Opportunity. The deal value, expected close date, loss reason, and owner assignment transfer directly. We resolve the owner by email cross-reference against the destination User table and set the Opportunity's OwningUser and OwningTeam at migration time.

Each Teamgate named Pipeline becomes a Dynamics 365 Record Type on Opportunity with a corresponding Sales Process that scopes the Stage picklist. Multi-pipeline teams (Teamgate Professional and Enterprise) map to multiple Record Types, each with its own Page Layout assignment. We configure Record Types and Sales Processes in the target Dynamics 365 environment before any Opportunity data moves.

Teamgate Pipeline Stages with their sequence order and probability percentages migrate to Dynamics 365 Opportunity Stage values with StageProbability populated per stage. Closed-Won and Closed-Lost stage probabilities are fixed at 100% and 0% per Dataverse rules. Loss reasons from Teamgate Deals map to a custom Opportunity field tg_loss_reason__c.

Teamgate custom fields on People (text, number, date, dropdown, checkbox types) map to Dataverse custom fields on the Lead or Contact entity as determined by the split rule. We pre-create the custom field schema in the Dynamics 365 environment before migration, using field type equivalence (Teamgate date maps to Dataverse datetime, Teamgate dropdown maps to Dataverse choice or picklist).

Teamgate custom fields on Deals migrate to custom fields on the Opportunity entity in Dataverse. Field type mapping follows the same equivalence rules as People custom fields. If a Teamgate custom field references a related Company (via a lookup field), we resolve the target Account GUID before inserting the Opportunity record.

Teamgate tags are flat string labels on People, Companies, and Deals. We export tags as a normalized comma-separated list per record. Tags on migrated records map to either a Dataverse multi-select choice field or to Topics with TopicAssignment records depending on whether the customer uses them for content classification or sales segmentation.

Teamgate activity logs tied to People or Deals migrate to Dataverse Task and EmailMessage records with the Regarding (object) reference pointing to the resolved Lead, Contact, or Opportunity. Call dispositions, durations, and meeting attendee lists migrate to custom fields on the Task record. We batch activity inserts using Dataverse Web API pagination with retry logic on HTTP 429 responses.

Teamgate User records map to Dynamics 365 User by email match. Owner assignments on Deals and Companies are resolved by cross-referencing the Teamgate owner_id to the destination User's Azure Active Directory object ID or email. Any Teamgate Owner without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import proceeds.

Teamgate loss reason dropdown values are a Deal-level custom field. We export all active values and create a Dataverse choice field tg_loss_reason__c on the Opportunity entity, populating the choice values during schema provisioning. Values without a match in Dynamics 365 are created as new choice options before the migration batch runs.