How to migrate from Salesforce to Dynamics 365 Sales
To migrate a client from Salesforce to Dynamics 365 Sales with superglue's AI agent, connect the client's Salesforce org, and give superglue access to the client's Dynamics 365 Sales account. superglue assesses the data in minutes, plans every phase, recommends an answer to each decision, and runs a trial load that reconciles every record before cutover. You review, decide and sign off with the client.
What are the steps to migrate from Salesforce to Dynamics 365 Sales?
Migrating from Salesforce to Dynamics 365 Sales takes six steps: connect both systems, assess the data, plan every phase, decide the mapping, run a trial load and cut over. Each load repeats exactly what you tested, and every write waits for your approval.
- 01
Connect Salesforce and Dynamics 365 Sales
Connect the client's Salesforce org with one sign-in. superglue reads it through the Salesforce API and writes nothing. The client then gives superglue access to Dynamics 365 Sales.
- 02
Assess the Salesforce data
In minutes, superglue counts every record, finds the open items and lists the data issues with examples. You know the size of the migration before you quote it.
- 03
Plan every phase
superglue drafts the plan from discovery to cutover, with tasks, owners and the Salesforce specifics already in it.
- 04
Decide the mapping
superglue brings each decision below with a recommendation from the client's own data. You confirm or change each answer, and the client signs the mapping.
- 05
Run the trial load
superglue loads a Dynamics 365 Sales sandbox environment and compares it with Salesforce: the record count per object, the open pipeline per stage and owner, and the source ID on every record. superglue explains every difference before cutover.
- 06
Cut over
At cutover, superglue loads the final data with the same steps as the trial load, and you sign the reconciliation with the client.
How do you get the data out of Salesforce?
- Have a Salesforce user who can view all data sign in once. superglue reads the org through the API and writes nothing.
- Every read counts against the org's daily API limit, which the client's other integrations share, so superglue plans the read around them.
- Files and attachments take the longest to move, so superglue counts them in the assessment.
What needs to be configured in Dynamics 365 Sales?
The client signs in to Dynamics 365 Sales with superglue's Microsoft app. superglue configures Dynamics 365 Sales and loads the data through that access, in a Dynamics 365 Sales sandbox environment first, in this order:
- 01
Currencies, business units, teams and security roles.
- 02
Custom tables and columns, option values and business process flows, kept in a solution.
- 03
The product catalog: unit groups, products and price lists.
- 04
Users and owners, then accounts, contacts and leads.
- 05
Opportunities and activities, with opportunities closed last.
What moves from Salesforce to Dynamics 365 Sales?
| In Salesforce | In Dynamics 365 Sales |
|---|---|
| Accounts | Accounts |
| Contacts and person accounts | Contacts |
| Leads | Leads |
| Opportunities and contact roles | Opportunities |
| Products and price books | Products, price lists and unit groups |
| Users, roles and queues | Users, teams and business units |
Open records
Open opportunities with their products and contact roles, open leads, and open tasks and events.
Open opportunities load with their stage, estimated revenue and close date, and every open activity keeps its owner and due date.
History
Closed opportunities, completed tasks and events, emails, notes and files.
History loads with its original created dates, and each record keeps its source ID.
Which decisions do you make when you migrate from Salesforce to Dynamics 365 Sales?
- 01
Where do Salesforce record types go?
Dynamics 365 Sales uses forms, business process flows and option values where Salesforce uses record types.
superglue proposes a business process flow for each sales process, and keeps the record type as an option value for reporting.
- 02
What happens to opportunity contact roles?
Dynamics 365 Sales lists the buying group on the opportunity as stakeholders, through connection roles.
superglue moves each contact role as a stakeholder with the same role name.
- 03
Which leads move?
By default, qualifying a lead in Dynamics 365 Sales creates an account, a contact and an opportunity, and the client can change which records it creates.
superglue moves open leads as leads, and keeps converted leads only as history on their contact.
- 04
Which business units and security roles does the client need?
Business units, teams and security roles decide who sees which records in Dynamics 365 Sales. Every owner must map to a user or team that fits that model.
superglue proposes business units and teams from how records are owned in Salesforce today.
- 05
How much activity history moves?
Activities and emails are often the largest part of the data, and old ones are rarely opened in Dynamics 365 Sales.
superglue recommends every account, contact and open opportunity, closed opportunities from the last three years, and the activities of active records.
What are the common challenges when you migrate from Salesforce to Dynamics 365 Sales?
Person accounts are an account and a contact at once
Orgs that sell to individuals use person accounts. superglue moves each person account as a contact, with its activities and opportunities.
Converted leads are history
Salesforce keeps converted leads as hidden, read-only records that link to the account, contact and opportunity the conversion created or matched. superglue counts them apart from open leads, so they do not come back as new leads.
Agree who takes over the records of people who left
A migration surfaces every account and opportunity owned by someone who left. Agree the new owners with sales leadership before the load, or those records sit unworked. superglue lists them per owner.
Keep the original created dates
Without extra work, every migrated record shows the load date as its created date, and reports on pipeline age and lead response break. superglue keeps the original dates.
Sign off the unit groups before products load
The unit group of a product cannot change once the product exists, so a wrong unit group means deleting and recreating the product. Get the unit groups signed before any product loads.
superglue also runs the rest of the Dynamics 365 Sales project. See the Dynamics 365 Sales implementation
Frequently asked questions
Which data moves from Salesforce to Dynamics 365 Sales?
Accounts, contacts, leads, opportunities and products, the open items, and as much history as the client needs. The mapping table on this page shows where each record lands in Dynamics 365 Sales.
Does superglue write to Dynamics 365 Sales without my approval?
No. superglue only reads Salesforce. Before any write to Dynamics 365 Sales, it shows the target, the connection and a transformed sample, and waits for your approval.
How do I know the migration is complete?
superglue reconciles the trial load and the final load against Salesforce: the record count per object, the open pipeline per stage and owner, and the source ID on every record. You get a reconciliation report to sign with the client.
What happens when I start this migration?
You sign up and connect the client's systems. If you want to see a full migration run first, superglue can set up Pinecrest Supply, a sample client.
Start your Salesforce to Dynamics 365 Sales migration
Sign up and connect the client's systems, or let superglue set up Pinecrest Supply, a sample client, to see a full migration run first.