Migrate from TeamSystem CRM to Microsoft Dynamics 365 Sales

TeamSystem Contact records map to Microsoft Dynamics 365 Sales Contact. We extract name, email, phone, address, ownership assignment, and any custom fields on the contact record. The email address serves as the primary dedupe key during import. Owner resolution maps TeamSystem owner IDs to Dynamics 365 User records by email match; any unresolved owner goes to a reconciliation queue for the customer's admin to provision before Contact insert proceeds.

TeamSystem Company records map to Microsoft Dynamics 365 Sales Account. The company name becomes Account Name; address fields map to the standard Address compound field in Dataverse. Where TeamSystem stores a domain or website on the Company record, we map that to the Account Website field. Account is created before Contact import so the parent AccountId lookup is satisfied at the moment of Contact insert.

TeamSystem Lead records with status, source, and scoring fields map to Dynamics 365 Lead. Lead status values from TeamSystem require explicit mapping to Dynamics 365 Lead Status picklist values since the stage taxonomy differs per organization. Any scoring field in TeamSystem migrates as a custom integer field on the Dynamics Lead for post-migration segmentation use.

TeamSystem Opportunity records (deals with value, stage, expected close date, and pipeline association) map to Microsoft Dynamics 365 Sales Opportunity. The pipeline stage name in TeamSystem maps to a Microsoft Dynamics 365 Sales Process stage value; we create the Sales Process and whitelisted stages during configuration before migration begins so the stage reference is valid at insert time. Deal amount maps to EstimatedRevenue.

TeamSystem pipeline definitions (stage names, probabilities, and sequence) map to Dynamics 365 Record Types and Sales Processes. Each TeamSystem pipeline becomes a Record Type on Opportunity with a corresponding Sales Process that controls the stage dropdown values and their probabilities. We configure these in the destination Dynamics 365 org during the schema design phase before record migration.

TeamSystem Activity logs (calls, emails, meetings, tasks) require value mapping since the activity type taxonomy differs between platforms. We classify each TeamSystem activity by its type attribute, then map to the corresponding Dynamics 365 entity: calls to Task with TaskSubtype=Call, emails to EmailMessage linked to a Task, meetings to Event, and standalone tasks to Task. The original TeamSystem timestamp maps to ActivityDate to preserve the timeline ordering.

Organization-specific fields on any standard object in TeamSystem require pre-discovery to identify the full field registry. We query the field schema during scoping to ensure all non-standard columns are included in the export package. Each custom field maps to a Dataverse custom column of equivalent type (text, integer, decimal, date, picklist) on the target entity, created during the schema design phase before record migration.

TeamSystem User accounts with role assignments and record ownership do not map directly by ID to Dynamics 365 User records. We build a user mapping table during scoping that matches TeamSystem user email to the corresponding Dynamics 365 User. The customer's admin provisions any missing Dynamics 365 Users before migration. Owner resolution fails cleanly with a reconciliation report for any TeamSystem owner without a destination User match.

Email tracking and inbox association data from TeamSystem migrates as EmailMessage records linked to Tasks on the Contact or Opportunity timeline. We extract email content, timestamps, and sender-recipient relationships. Full email body migration is subject to the TeamSystem integration configuration; we flag any emails that cannot be extracted due to attachment expiry or storage limits during scoping.

Files linked to deals, contacts, or activities export by reference URL or download where accessible. Attachment migration is conditional on TeamSystem storage availability and any expiry rules set on the account. We flag any attachments that exceed storage limits or are inaccessible due to the customer's TeamSystem configuration during the discovery phase.