Dynamics 365 Sales· Data mapping
OverviewMCP server
Pre-implementation
  1. Implementation plan
  2. Discovery
  3. Data assessment
  4. Solution design
Implementation
  1. Configuration
  2. Data mapping
  3. Data migration
  4. Testing and UAT
  5. Cutover
Post go-live
  1. Hypercare
  2. Handover
Step 6 of 11 · Implementation · Updated October 26, 2026

Dynamics 365 Sales data mapping

Data mapping is where the business decisions of a Dynamics 365 Sales migration are made. A mapping that copies the legacy structure one to one usually carries the legacy problems into Dynamics 365 Sales. superglue's agent proposes field mappings and transformations, you decide the ambiguous cases, and the client signs transformed files before anything loads.

Start a Dynamics 365 Sales projectTalk to us

How this step works

What the agent does

  • Proposes field mappings and value translations from the source structure to Dynamics 365 Sales.
  • Lists the ambiguous cases and the records that cannot map, with counts.
  • Builds a client questionnaire for questions only the client can answer.
  • Produces transformed files for review.

What you decide and approve

  • The business meaning of ambiguous fields and codes.
  • What happens to records that cannot map.
  • When the mapping is ready for the client's signature.

What the client gets

  • A mapping report to sign.
  • Transformed files to review before the load.

Key Dynamics 365 Sales mapping decisions

  1. 01

    Map the security model first

    Business units, teams and security roles decide who sees what. Owners must map to users or teams that fit that model.

  2. 02

    Lead qualification works differently

    Qualifying a lead in Dynamics 365 Sales creates the account, contact and opportunity. Decide which source leads arrive as leads and which as converted records.

  3. 03

    Stages and option values

    Map pipeline stages to the sales process stages, and picklist values to option values, with the business owner.

  4. 04

    Keep the source ID

    Store the source record ID on each record. It makes reconciliation and re-runs safe.

Frequently asked questions

What are the key Dynamics 365 Sales mapping decisions?

Map the security model first; Lead qualification works differently; Stages and option values; Keep the source ID. The agent proposes an answer from the source data, and you confirm or change it.

Can the client review the mapping before anything loads?

Yes. The agent produces transformed files and a mapping report. The client signs the mapping, and the load uses exactly the signed mapping.

How does superglue work with our consultants?

superglue works alongside your team. The agent takes on the repetitive work, such as reading documents, drafting, mapping, loading and reconciling. Your consultants keep the client relationship and the decisions, and they approve every change to a client system.

Can we use our own implementation method?

Yes. Write your firm's method as a playbook, and every consultant and every session follows it. The documents the agent produces carry your firm's branding.

Which systems can we migrate from into Dynamics 365 Sales?

Common sources are Salesforce, HubSpot, Dynamics CRM on-premise, Pipedrive and spreadsheets. The agent also reads Excel, CSV and XML exports and most systems with an API or a database.

Is client data safe?

superglue holds a SOC 2 Type 2 report and works under GDPR. Credentials are encrypted with AES-256. On the Enterprise plan, superglue can run on your own infrastructure.

How do we start?

Start with one live Dynamics 365 Sales project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.