Migrate from Sales Mantra to Microsoft Dynamics 365 Sales

Sales Mantra Lead records map to Microsoft Microsoft Dynamics 365 Sales Lead. We extract all standard lead fields (name, email, phone, source, status, owner) from the CSV export. The Dynamics Lead Status field is populated from the corresponding Sales Mantra status column. Owner is resolved by matching the Sales Mantra owner name to the email-based User record in Dynamics. If the export includes a lead score or qualification flag, we map it to a custom field lead_score__c in Dynamics.

Sales Mantra Account records map to Microsoft Microsoft Dynamics 365 Sales Account. We preserve Account Name, Address (City, State, Country), Industry, Website, and any custom fields exported. Account is loaded before Contact and Opportunity so that the AccountId lookup relationship is satisfied at the moment of Contact and Opportunity insert. The Account Name serves as the dedupe key to prevent duplicate Account creation during import.

Sales Mantra Deals map to Microsoft Microsoft Dynamics 365 Sales Opportunity. The Deal name becomes the Opportunity Name, Deal value maps to EstimatedRevenue, the Sales Mantra pipeline stage maps to Dynamics StageName, and the expected close date maps to EstimatedCloseDate. We load Opportunities after Accounts so that the AccountId lookup resolves correctly. Pipeline stage values from Sales Mantra are mapped to the corresponding Dynamics Sales Process stage values configured in the destination org.

Sales Mantra Activity records are split by activity type: calls and tasks map to Dynamics Task (with TaskSubtype=Call for call records), and meetings map to Dynamics Event. Email activities map to EmailMessage records linked to Tasks for the activity timeline. Activity timestamps are preserved in ActivityDate (Task) or StartDateTime (Event). We verify during the data audit that the CSV export contains the full activity history for the migration window; if Activities are truncated, we flag this before production migration.

Sales Mantra assigns Deals and Activities to named Owners. We extract the distinct owner list from the CSV exports and match by display name or email to the Dynamics 365 User table. Owner mapping must be validated before record import begins because Dynamics Opportunity, Task, and Event records require a valid OwnerId. If a Sales Mantra owner has no matching Dynamics User, we hold those records in a reconciliation queue and flag the gap for the customer's admin to provision before migration resumes.

Sales Mantra document attachments linked to Accounts or Deals are exported as file references or URLs from the CSV. We map these to SharePoint Document Locations attached to the corresponding Account or Opportunity in Dynamics. If the Sales Mantra export produces download URLs rather than files, we recommend downloading critical documents manually before the migration cutoff. Files that are not reachable via URL require escalation to Sales Mantra for a bulk file export and are handled as a separate managed workflow outside the standard migration scope.

The Sales Mantra contact classification feature may export as delimited multi-value columns (for example, semicolon-separated audience tags) or as named custom properties beyond standard name/email/phone. We audit the export schema during the data audit phase. Delimited columns are split into separate normalized fields mapped to Dynamics custom string fields or multi-select option sets as appropriate. Custom property names are preserved as Dynamics field labels with API names generated from the export column headers. Tier and edition constraints on the destination Dynamics org do not apply to custom fields at the Professional tier.

The Sales Mantra research evidence does not show a separate Products object or line-item catalog within Deals. If the Sales Mantra instance stores a product catalog, it is likely embedded in Deals as text fields rather than structured line items. We verify product catalog presence during the scoping phase. If structured Products exist, we map them to Dynamics Product2 with Standard Price Book entries. If products exist only as free-text Deal descriptions, no Product2 migration applies; the customer recreates the product catalog in Dynamics after migration.