Migrate from Salesmate to Microsoft Dynamics 365 Sales

Salesmate Contacts with a lifecycle stage of subscriber, lead, or marketing qualified lead map to Microsoft Dynamics 365 Lead. Contacts with stage of customer or evangelist map to Dynamics 365 Contact attached to an Account. We compute the split using Salesmate's lifecycle_stage property and preserve the original stage value in a custom field sm_original_lifecycle__c on both Lead and Contact for audit trail and reporting continuity.

Salesmate Company records map to Microsoft Dynamics 365 Account. Company domain stored in the website field becomes the Account's Website. Account is created before any Contact import so the Contact-to-Account lookup relationship is satisfied at insert time. Custom Company fields map to equivalent Account custom fields or to a related custom entity if no native field exists.

Salesmate Deals map to Dynamics 365 Opportunity. The deal stage property maps to a Microsoft Dynamics 365 Sales Process configured as part of migration scope, and pipeline assignment maps to a Record Type. Closed-Won and Closed-Lost reason fields from Salesmate custom properties become Opportunity custom fields for win/loss analysis. Owner assignment migrates by resolving Salesmate owner email to Dynamics 365 User.

Each Salesmate pipeline becomes a Dynamics 365 Record Type with a corresponding Sales Process that whitelists the stage values. We configure stage probability percentages using Salesmate's stage probabilities as the source of truth. The Sales Process is deployed to the destination environment before Opportunity migration begins.

Salesmate Tasks map to Dynamics 365 Task records with Status, Priority, ActivityDate, and OwnerId preserved. Task associations to Contact or Deal resolve to the migrated Lead, Contact, or Opportunity record by cross-referencing the pre-built ID mapping table generated during the scoping phase.

Salesmate email engagements migrate to Dynamics 365 EmailMessage records linked to an ActivityPointer (Task) entry in the timeline. The email body and subject transfer; thread metadata is preserved in a custom field for reconstruction if the customer's admin needs conversation threading. WhoId links to the migrated Lead or Contact; WhatId links to the related Opportunity or Account.

Salesmate call log engagements map to Dynamics 365 Task with TaskSubtype set to Call. Call duration, disposition, and recording URL (if stored in Salesmate) migrate to custom Task fields. Activity timestamp is preserved as ActivityDate to maintain timeline ordering.

Salesmate meeting engagements map to Dynamics 365 Appointment records. StartTime, EndTime, Location, and subject transfer directly. Attendee information maps to ActivityParty records linked to the Appointment. Meeting body and notes migrate as custom fields if the customer's admin requires the full content.

Salesmate notes migrate to Dynamics 365 Annotation records linked via the ObjectId field to the parent record (Contact, Account, or Opportunity). Note creation timestamp is preserved. If Salesmate notes contain embedded images, these migrate as file attachments on the related record.

Salesmate custom fields across Contacts, Companies, Deals, and Tasks map to equivalent custom fields in Dynamics 365. Field types are evaluated during scoping: text maps to Text, date maps to DateTime, number maps to Integer or Decimal, and multi-select properties map to Option Set. We pre-create all custom fields in Dynamics 365 before any record import to avoid field-missing errors during data load.

Salesmate Owners map to Dynamics 365 User records by email match. Owners without a matching Dynamics 365 User go to a reconciliation queue for the customer's admin to provision. Migration cannot proceed past Opportunity import because OwnerId references are required on most standard objects.

Salesmate tags stored as string arrays on Contact and Company export as multi-value metadata. We map them to a Dynamics 365 multi-select Option Set field if tag cardinality is under 300 distinct values; otherwise we use a Text field. The customer chooses the strategy during scoping.

Salesmate Team Inbox shared conversations use a threading model with per-reply attribution that has no direct Dynamics 365 equivalent. We export thread metadata (thread ID, message order, responder user, timestamp) as custom fields on a dedicated sm_team_inbox thread entity, and we attach individual messages as EmailMessage records linked to that thread entity. Full conversation reconstruction requires manual assembly by the customer's admin using the custom fields as a guide.

Smart Flow automation definitions are not fully accessible via the Salesmate API, so the automation logic cannot migrate as code. We export Smart Flow membership data (which contact was enrolled in which flow, enrollment date, step reached, and completion status) as a CSV delivered alongside migration. Your admin uses this membership log to configure equivalent Power Automate flows or Microsoft Dynamics 365 Sales automated flows post-migration. We do not rebuild Smart Flow logic as part of the migration scope.