CRM migration
Field-level mapping, validation, and rollback between Smarketing Cloud and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
Smarketing Cloud
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
7 of 9
objects map 1:1 between Smarketing Cloud and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Smarketing Cloud to Microsoft Microsoft Dynamics 365 Sales addresses two structural problems: Smarketing Cloud's performance degrades under heavy campaign send volumes and offers no published API for programmatic data access, while Dynamics 365 provides a predictable per-user pricing model and deep Microsoft 365 ecosystem integration. Smarketing Cloud has no public bulk export format documented, so we build custom ETL pipelines that parse the platform's export output and remap every field to the equivalent Dynamics 365 entity before import. We do not migrate Smarketing Cloud Workflows, Sequences, or Automation as code; we deliver a written inventory of every active workflow for the customer's admin to rebuild in Microsoft Dynamics 365 Sales , which uses a fundamentally different automation model. Microsoft Copilot for Sales is included with Sales Enterprise and Premium tiers, providing AI-assisted relationship intelligence that Smarketing Cloud bundles across all tiers.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Smarketing Cloud platform overview
Scorecard, SWOT, gotchas, and pricing for Smarketing Cloud.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Smarketing Cloud object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Smarketing Cloud
Contact
Microsoft Dynamics 365 Sales
Contact
1:1Smarketing Cloud Contact records map to Dynamics 365 Contact. Standard fields (firstname, lastname, email, phone) migrate directly. Lifecycle stage from Smarketing Cloud maps to a custom Contact field lifecycle_stage__c since Dynamics 365 does not have an equivalent native property. Smart Data Sync external source links export as custom text fields and are preserved as notes for manual reconnection post-migration.
Smarketing Cloud
Company
Microsoft Dynamics 365 Sales
Account
1:1Smarketing Cloud Company records map to Dynamics 365 Account. The Company-Contact linkage is preserved via the accountid lookup on Contact during migration. Hub ID or internal company identifier from Smarketing Cloud is stored in a custom account field for reference. We create the Account before Contact import so the lookup relationship is satisfied at insert time.
Smarketing Cloud
Pipeline
Microsoft Dynamics 365 Sales
Opportunity + Record Type + Sales Process
lossySmarketing Cloud pipelines and their custom-named stages map to Dynamics 365 Opportunity Record Types with corresponding Sales Processes. Each pipeline in Smarketing Cloud becomes a separate Record Type, and the stage sequence is recreated as a Sales Process with stage values matching the source naming. Stage probability percentages are mapped to the corresponding Sales Process stage definitions.
Smarketing Cloud
Deal
Microsoft Dynamics 365 Sales
Opportunity
1:1Smarketing Cloud Deals map to Dynamics 365 Opportunity. Deal properties (amount, closedate, dealname) map to Opportunity amount, estimatedclosedate, and name. Pipeline assignment determines the Opportunity's Record Type and Sales Process at migration time. Closed-won and closed-lost reasons from Smarketing Cloud custom fields become custom Opportunity fields.
Smarketing Cloud
Campaign
Microsoft Dynamics 365 Sales
Campaign
1:1Smarketing Cloud Campaigns migrate to Dynamics 365 Campaign, preserving campaign member lists and send history. Campaign membership records (which Contacts were enrolled in which Campaigns and when) migrate as CampaignMember records with the appropriate status values remapped to Dynamics 365 CampaignMember status options (Responded, Sent, Opted Out).
Smarketing Cloud
Activity
Microsoft Dynamics 365 Sales
Activity (Task, Email, Appointment)
1:1Smarketing Cloud Activity logs (calls, emails, meetings, notes) linked to Contacts and Companies export with activity type, timestamp, owner, and description text. We map call activities to Task with TaskSubtype=Call, email activities to Email, and meetings to Appointment (Event). Owner assignment is preserved via user email mapping to Dynamics 365 User. Historical timestamps are preserved on ActivityDate.
Smarketing Cloud
User
Microsoft Dynamics 365 Sales
User
1:1Smarketing Cloud User records export with name, email, role, and team assignment. We map Smarketing Cloud roles to equivalent Dynamics 365 security roles (e.g., Salesperson, Sales Manager, Marketing User) during migration scoping. Inactive users can be exported but scope is agreed per migration plan. Users without a matching Dynamics 365 tenant account are held for admin provisioning.
Smarketing Cloud
Custom Object
Microsoft Dynamics 365 Sales
Custom Entity
1:1Smarketing Cloud custom objects migrate to Dynamics 365 custom entities created in Dataverse before migration. We pre-create the destination schema including all custom fields, lookup relationships to Contact, Account, and Opportunity, and any required options sets. Data export is sequenced after schema deployment so all lookup references are valid at insert time.
Smarketing Cloud
Tag
Microsoft Dynamics 365 Sales
Multi-Select Picklist or Topic
lossySmarketing Cloud tags on Contacts and Companies export as string values per record. We apply them in bulk as Dynamics 365 multi-select picklist values on the respective entity, or as Topics with TopicAssignment records if the customer prefers a taxonomy-based classification model. Tag strategy is confirmed during scoping.
| Smarketing Cloud | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Pipeline | Opportunity + Record Type + Sales Processlossy | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Campaign | Campaign1:1 | Fully supported | |
| Activity | Activity (Task, Email, Appointment)1:1 | Fully supported | |
| User | User1:1 | Fully supported | |
| Custom Object | Custom Entity1:1 | Fully supported | |
| Tag | Multi-Select Picklist or Topiclossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Smarketing Cloud gotchas
No public API documentation or developer portal
Proprietary data format with no bulk export format documented
Performance bottlenecks during high-volume campaign sends
Limited historical data export for record history
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
Discovery and export format audit
We audit the Smarketing Cloud account across object types (Contacts, Companies, Deals, Campaigns, Activities, Custom Objects), custom property count, active workflows, campaign send volumes, and user list. We extract a sample export to characterize the undocumented output format. We pair this with a Dynamics 365 edition assessment: Sales Professional ($65/user) covers most migrations; Sales Enterprise ($105/user) is required if the customer needs Copilot, advanced sales intelligence, or multi-territory forecasting. The discovery output is a written migration scope, ETL build estimate, and Dynamics edition recommendation.
Custom ETL pipeline build
We build a custom ETL pipeline that parses the specific export format produced by the customer's Smarketing Cloud instance. The pipeline handles field-to-column mapping, data type normalization, Smarketing Cloud property names remapped to Dynamics 365 field names, and date/time format standardization to UTC. We run a test parse against the sample export and present mapping discrepancies to the customer for resolution before proceeding.
Dynamics 365 schema design and Dataverse configuration
We design the destination schema in Dynamics 365, including custom entities for Smarketing Cloud custom objects, custom fields on Contact and Account for Smarketing Cloud properties, Record Types and Sales Processes for pipeline mapping, and security roles mapped from Smarketing Cloud roles. Schema is deployed into a Dynamics 365 Sandbox environment for validation before production migration begins.
Sandbox migration and reconciliation
We run a full migration into the Dynamics 365 Sandbox using production-like data volume. The customer's RevOps or IT lead reconciles record counts (Contacts in, Accounts in, Opportunities in, Activities in), spot-checks 20-40 records against the Smarketing Cloud source, and signs off the ETL output and mapping before production migration is scheduled. Any corrections to the ETL pipeline or field mapping happen at this stage.
Owner and User reconciliation
We extract every distinct Smarketing Cloud User and Owner referenced on Contacts, Companies, Deals, and Activities and match by email against the destination Dynamics 365 tenant. Users without a matching account go to a reconciliation queue for the customer's tenant admin to provision before production migration. Migration cannot proceed past record loading until all OwnerId references have a valid destination lookup.
Production migration in dependency order
We run production migration in dependency order: Accounts (from Smarketing Cloud Companies), Contacts (with accountid resolved), Opportunities (with RecordTypeId, SalesProcessId, and OwnerId resolved), Campaign and CampaignMember records, Activities via Dataverse API with parent-record resolution (WhoId, WhatId), Custom Objects (last, because they often have lookups to standard entities). Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation rebuild handoff
We freeze Smarketing Cloud writes during cutover, run a final delta migration of any records modified during the migration window, then enable Dynamics 365 as the system of record. We deliver the Workflow and Sequence inventory document to the customer's admin team with recommended Dynamics 365 equivalents. We support a five-business-day hypercare window where we resolve reconciliation issues raised by the sales team. We do not rebuild Smarketing Cloud workflows as Dynamics 365 Power Automate flows inside the migration scope.
Platform deep dives
Smarketing Cloud
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Smarketing Cloud and Microsoft Dynamics 365 Sales .
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Smarketing Cloud: Rate limit documentation not published.
Data volume sensitivity
Smarketing Cloud doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Smarketing Cloud to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your Smarketing Cloud to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Smarketing Cloud
Other ways to arrive at Microsoft Dynamics 365 Sales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
