---
title: "Zendesk Sell to Dynamics 365 Migration | FlitStack AI"
description: "Migrate Zendesk Sell to Dynamics 365 with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/zendesk-sell/to/dynamics-365-sales"
---

# Zendesk Sell to Dynamics 365 migration

We migrate Leads, Contacts, Deals, and activity history from Zendesk Sell into Microsoft Dynamics 365 Sales with the Pipeline-to-Record-Type mapping resolved up front, stage history preserved across the Dataverse API, and every Sell custom field mapped to a typed column before cutover. The August 31, 2027 Sell retirement deadline makes migration timing a first-order constraint for every customer in this pair.

Short answer

FlitStack AI migrates leads, contacts, accounts, opportunities and record types from Zendesk Sell to Dynamics 365, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 3-5 weeks.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See what moves →](https://flitstack.ai/migrations/crm/zendesk-sell/to/dynamics-365-sales#what-moves)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Zendesk Sell ![](https://flitstack.ai/platforms-trim/zendesk-sell.webp)

Destination Dynamics 365 ![](https://flitstack.ai/platforms-trim/dynamics-365-sales.webp)

Lead Contact Account Opportunity Record Type

Mapped field by field · sample run · one-click rollback

## What moves from Zendesk Sell to Dynamics 365?

Moving from Zendesk Sell to Microsoft Dynamics 365 Sales is a structural migration driven by Sell's confirmed retirement on August 31, 2027.

Read the full summary

Zendesk Sell organizes revenue around Pipelines containing Stages with Deals as the revenue record; Microsoft Dynamics 365 Sales uses Opportunities with Record Types and Sales Processes to achieve equivalent segmentation. We resolve the Pipeline-to-Record-Type split during scoping, map Sell Stages to corresponding Dynamics 365 stage values within each Sales Process, and preserve the stage-order ordinality that drives reporting. Activity history (calls, emails, meetings, tasks) migrates to Dynamics 365 Activity records via the Dataverse API with parent-record resolution against the migrated Contact or Opportunity. Sell Sequences, Line Items, and custom Objects require explicit mapping decisions at scoping because Dynamics 365 does not store them identically. We deliver a written automation inventory for the customer's admin to rebuild in Dynamics 365 Sales Insights or Power Automate post-migration; we do not migrate workflows, sequences, or automations as code.

1:1

### Lead → Lead

Zendesk Sell Leads map directly to Microsoft Dynamics 365 Sales Leads.

How it maps

The Lead's source, status, and unqualified-reason fields map to Dynamics 365 Lead Status and Lead Source. Custom Lead fields in Sell migrate to custom columns on the Lead entity in Dataverse. Owner assignment migrates by email match against the Dynamics 365 User table. Lead scores and any custom scoring fields transfer as integer or decimal columns.

1:1

### Contact → Contact

Sell Contacts map to Dynamics 365 Contacts with standard fields (full name, email, phone, address) preserved.

How it maps

Custom Contact fields migrate to Dataverse custom columns on the Contact entity. Parent Company (Sell's company\_id) resolves to Dynamics 365 Account.accountid at migration time. We run dedupe validation on email before insert to catch duplicate Contacts.

1:1

### Company → Account

Sell Companies map to Dynamics 365 Accounts.

How it maps

The Company name becomes Account.name; domain becomes Account.website. Sell's company type or industry field maps to Account.industry. Custom Company fields migrate as Dataverse custom columns on the Account entity. Account must exist before Contact import so that the parentcustomerid lookup is satisfied.

1:1

### Deal → Opportunity

Sell Deals map to Dynamics 365 Opportunities.

How it maps

The dealstage property maps to the stage name in the relevant Dynamics 365 Sales Process; probability migrates to closeprobability. Closed-Lost and Closed-Won reasons map to Dynamics 365's closereason field. Deal value (estimated\_value) maps to Dynamics 365 estimatedvalue. The associated Sell Contact and Company link via Dynamics 365's customerid and parentaccountid lookups.

configuration

### Pipeline → Record Type

Sell Pipelines are custom workflow containers that have no direct Dynamics 365 equivalent.

How it maps

We map each Sell Pipeline to a Dynamics 365 Record Type on Opportunity. The Record Type controls which Page Layout and Sales Process apply, effectively replacing Sell's pipeline-level segmentation. Multi-pipeline Sell accounts (Professional tier) require multiple Record Types in Dynamics 365.

configuration

### Stage → Sales Process Stage

Sell Stages are children of Pipelines with ordinal position and win/loss flags.

How it maps

We map each Stage to a Stage in the corresponding Dynamics 365 Sales Process. Stage order is preserved by matching the ordinal position. Loss flags become Dynamics 365 Stage categories (Lost, In Progress, Won). We configure the Sales Process in the target org before migration begins.

******What moves 10 objects

Zendesk Sell Dynamics 365

- Lead Lead 1:1
- Contact Contact 1:1
- Company Account 1:1
- Deal Opportunity 1:1
- Pipeline Record Type transformed
- Stage Sales Process Stage transformed

\+ 4 more in the mapping below

## How Zendesk Sell and Dynamics 365 differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension            | Zendesk Sell                                                     | Dynamics 365                                                                   |
| -------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| Revenue object model | Deal inside Pipeline with Stage hierarchy                        | Opportunity with Record Type and Sales Process stages                          |
| Company model        | Standalone Company object                                        | Account object (Company concept) with Contact child records                    |
| Lead conversion      | Lead converts to Contact and optionally creates Deal             | Lead converts to Contact attached to Account; Opportunity creation is separate |
| Pipeline count       | Team 1 pipeline, Professional unlimited pipelines                | Unlimited Record Types at all paid tiers                                       |
| Custom objects       | Supported on Professional and above via custom fields            | Custom entities via Dataverse at all tiers with Power Apps licensing           |
| Activity timeline    | Calls, emails, meetings, tasks as first-class engagement records | Activity (PhoneCall, Email, Appointment, Task) via Dataverse                   |
| Native integrations  | Zendesk Support for unified customer view                        | Microsoft 365 (Teams, Outlook, SharePoint, Copilot)                            |
| Pricing structure    | Per-user at $19-$49/month with Zendesk Suite ties                | Per-user at $20-$95/month for Sales; full Microsoft 365 E3/E5 bundle value     |

## What to watch for in a Zendesk Sell to Dynamics 365 migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Sell sunset creates a hard deadline that compresses migration windows

Zendesk retired Sell on August 31, 2027 and deletes all Sell data per its Service Data Deletion Policy upon subscription end or sunset date, whichever comes first.

How we handle it

Organizations that begin migration after Q1 2027 risk rushed timelines, specialist availability constraints, and potential data loss. We schedule discovery calls with a target migration-start at least 9 months before the deadline and push customers toward early-start windows of 12-18 months. The retirement context makes this migration time-bound by default, unlike other pair migrations where timing is discretionary.

high

### Pipeline-to-Record-Type mapping requires pre-migration schema design

Sell Pipelines and Stages are a two-level hierarchy with no direct Dynamics 365 equivalent.

How we handle it

Dynamics 365 uses Record Types (per Pipeline) and Sales Processes (per Record Type with stage steps) to replicate this model, but the mapping must be designed and deployed before any Opportunity records import. Multi-pipeline Sell accounts (Professional tier) create multiple Record Types that must be provisioned with distinct Page Layouts. Skipping this design step results in all Deals importing into the default Opportunity entity with no pipeline segmentation, breaking downstream reporting.

medium

### Sell custom field IDs differ from field keys in API calls

Sell assigns a numeric custom field ID to all custom fields and a separate custom field key for user and organization fields.

How we handle it

When bulk importing via the Sell Core API, the field key (not the numeric ID) is required. Dynamics 365 custom columns use Dataverse column names (logical names). We resolve both Sell identifiers during scoping and maintain a field-key lookup table before writing any record. Migrations that skip this step produce null values for custom field data in Dynamics 365.

medium

### Activity history requires Dataverse API with parent-record resolution

Sell activity records (calls, emails, meetings, tasks) must link to the correct parent Contact or Opportunity in Dynamics 365 using the Dynamics 365 ID, not the Sell record ID.

How we handle it

We resolve the parent ID at migration time by querying Dataverse for the newly created Contact or Opportunity by email match or Sell ID cross-reference before writing the activity record. Dynamics 365 Dataverse API rate limits (6,000 requests/minute per app registration) require batch chunking for large engagement volumes. Call recordings require separate file transfer to SharePoint or blob storage and are not included in standard activity migration scope.

medium

### Sequences, Line Items, and custom Objects require explicit mapping decisions

Sell Sequences store enrollment state and cadence data not exportable as discrete records and with no equivalent in Dynamics 365 Sales.

How we handle it

We export Sequence metadata as a reference document and flag that reps must rebuild active sequences in Dynamics 365 Sales Insights or a third-party sales engagement tool. Line Items attach to Deals and represent products or services with quantity and price; Dynamics 365 Opportunity Products serves this function, but the migration must pre-create Product records and Price Lists before Line Item import. Custom Sell objects map to Dataverse custom entities, requiring Power Apps schema work that extends beyond standard migration scope.

## How the migration runs

1. ### Discovery and migration-start urgency briefing

   We audit the source Sell portal across tier (Team/Professional), pipeline count, custom fields, active sequences, and engagement volume.

   What this step covers

   We pair this with a review of the customer's current Microsoft 365 tenant and Dynamics 365 licensing state. The discovery output is a written migration scope with a migration-start recommendation tied to the August 31, 2027 sunset deadline. We push customers toward starting at least 12 months before sunset to avoid last-quarter crunch.

2. ### Schema design and Record Type/Sales Process mapping

   We design the Dynamics 365 destination schema.

   What this step covers

   This includes provisioning Record Types on Opportunity (one per Sell Pipeline), configuring Sales Processes with stage steps (one per Sell Stage), mapping Sell stage probabilities to Dynamics 365 close probability values, and creating any required custom columns on Lead, Contact, Account, and Opportunity to receive Sell custom field data. Schema deploys into a Dynamics 365 Sandbox first for validation before production migration begins.

3. ### Sandbox migration and reconciliation

   We run a full migration into a Dynamics 365 Sandbox using production-like data volume.

   What this step covers

   The customer's RevOps lead reconciles record counts (Leads in, Contacts in, Accounts in, Opportunities in, Activities in), spot-checks 25-50 random records against the Sell source, and signs off the schema and mapping before production migration. Mapping corrections happen in the Sandbox, not in production.

4. ### Owner reconciliation and User provisioning

   We extract every distinct Sell User referenced on Lead, Contact, Account, Opportunity, and Activity records and match by email against the Dynamics 365 destination User table.

   What this step covers

   Owners without a matching User enter a reconciliation queue. The customer's Dynamics 365 admin provisions any missing Users. This step gates all subsequent record imports because OwnerId references are required on standard entities.

5. ### Production migration in dependency order

   We run production migration in record-dependency order: Accounts (from Sell Companies), Contacts (with Account.accountid resolved), Leads (direct map), Opportunities (with RecordTypeId, Sales Process, OwnerId, and AccountId resolved), Activity history (Tasks, PhoneCalls, Email, Appointments via Dataverse API with parent-record resolution), and custom entity data (if applicable).

   What this step covers

   Each phase emits a row-count reconciliation report before the next phase begins.

6. ### Cutover, validation, and automation rebuild handoff

   We freeze Sell writes during cutover, run a final delta migration of records modified during the migration window, then enable Dynamics 365 as the system of record.

   What this step covers

   We deliver a written Sequence, automation, and workflow inventory document to the customer's admin team for rebuild in Dynamics 365 Sales Insights, Power Automate, or a third-party sales engagement tool. We support a one-week hypercare window for reconciliation issues. We do not rebuild Sell Sequences or automations as Power Automate flows within migration scope.

![](https://flitstack.ai/platforms/zendesk-sell.svg) Zendesk Sell ![](https://flitstack.ai/platforms/microsoft-dynamics-365-sales.svg) Dynamics 365

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Dynamics 365 Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**3-5 weeks** Typical, smaller accounts

**8-12 weeks** Large or heavily customised accounts

A quote scales with record volume, custom object complexity, and pipeline mapping scope. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Zendesk Sell to Dynamics 365 →](https://flitstack.ai/contact)

## Why teams move from Zendesk Sell to Dynamics 365

- Zendesk announced Sell's retirement on August 31, 2027, with data deletion per its Service Data Deletion Policy triggered on sunset date or subscription end, whichever comes first. Reddit discussions in r/CRM and analyst commentary frame this as a hard deadline that forces action regardless of satisfaction level with Sell, making Dynamics 365 a credible destination for Microsoft-stack organizations that want to consolidate vendors.
- Microsoft Dynamics 365 Sales dominates Zendesk on analytics and reporting, scoring 30 out of 30 evaluated criteria versus Zendesk's 24 out of 30 in a head-to-head feature comparison. Organizations running SaaS business models, multi-territory forecasting, or complex attribution models cite Dynamics 365's native Power BI integration and unlimited custom fiscal period configuration as materially stronger than Sell's reporting layer.
- Dynamics 365 Sales integrates natively with Microsoft 365 Copilot, Teams, Outlook, and SharePoint without third-party middleware. Microsoft 365 Copilot connects CRM opportunity details directly into Outlook and Teams workflows, a native integration advantage that Sell cannot match outside the broader Zendesk ecosystem which requires separate licensing. G2 reviewers on Dynamics 365 cite the Outlook and Teams embedding as a primary driver for enterprise adoption.
- Organizations already running Microsoft Dynamics 365 (Finance, Supply Chain Management, Business Central) for ERP or finance operations gain a unified data model when adding Dynamics 365 Sales. Sell has no native ERP integration path and requires manual re-entry or third-party connectors to QuickBooks, Xero, or NetSuite, a friction point explicitly cited by CRM consultants advising SMBs post-Sell retirement.
- Dynamics 365 Sales holds a higher overall rating on Gartner Peer Insights (4.4 stars, 545 reviews) versus Zendesk Sell (4.2 stars, 186 reviews), with 77% of Dynamics 365 reviewers willing to recommend the platform. The larger review corpus and higher recommendation rate reflect sustained enterprise investment and broader use-case coverage that Sell's narrower sales-focused feature set cannot match.

Questions, answered

## Zendesk Sell to Dynamics 365 migration questions

How long does a Zendesk Sell to Microsoft Dynamics 365 Sales migration take?

Most migrations land between three and five weeks for accounts under 15,000 Contacts, 3,000 Deals, and a single Sell pipeline with no custom entities. Migrations with multiple Sell pipelines (Professional tier), large engagement histories (over 200,000 activity records), or custom Sell objects requiring Power Apps schema work move to eight to twelve weeks because of Record Type/Sales Process configuration, Dataverse API batch chunking, and stage-order reconciliation.

Do Zendesk Sell Sequences and automations migrate to Dynamics 365?

No. Sell Sequences store enrollment state, step timing, and reply tracking tied to individual Contacts. This data is not exportable as a discrete record and has no equivalent in Dynamics 365 Sales. We export Sequence metadata (name, step count, cadence) as a reference document and flag that reps must rebuild active sequences in Dynamics 365 Sales Insights or a third-party sales engagement tool (Outreach, Salesloft). Sell Workflows similarly do not migrate; we deliver a written automation inventory with recommended Power Automate equivalents for the customer's admin to rebuild post-migration.

Can we keep Zendesk Support while moving Sell to Dynamics 365 Sales?

Yes. A hybrid stack is a common pattern for organizations that want to retain Zendesk Support for customer service while moving the sales CRM to Dynamics 365. Zendesk Support and Dynamics 365 Sales operate as independent systems with no native bidirectional sync. If the customer needs a unified customer view, we can configure a custom integration via Power Automate or a middleware tool (Zapier, Workato) to link Zendesk Support tickets to Dynamics 365 Account records. Alternatively, some customers migrate both Sell and Support to Dynamics 365 Customer Service for a fully unified Microsoft stack.

Do we lose historical engagement data (calls, emails, meetings, tasks) during migration?

No. We migrate the full engagement history via the Dynamics 365 Dataverse API with parent-record resolution. Calls land as PhoneCall activities; emails land as Email activities; meetings land as Appointment records; tasks land as Task records. Each activity links to the migrated Contact or Opportunity using the resolved Dynamics 365 ID. Activity ordering is preserved by setting ActivityDate to the original Sell timestamp. Call recordings are excluded from standard scope and require a separate file transfer to SharePoint or blob storage.

How do we handle the August 31, 2027 Sell sunset deadline?

The sunset deadline makes migration timing non-negotiable. Zendesk deletes all Sell data on the sunset date or subscription end, whichever comes first. We treat every Sell migration as time-bound and recommend starting discovery at least 12-18 months before August 31, 2027. Organizations starting after Q1 2027 face constrained specialist availability, compressed UAT windows, and the risk of partial data migration if the window closes before completion. We prioritize early-start customers and schedule migration-start targets at least 9 months before the deadline.

Can FlitStack AI also migrate Zendesk Support to Dynamics 365 Customer Service?

Yes. We treat Zendesk Support to Dynamics 365 Customer Service as a parallel or combined scope. Support ticket data (Tickets, Comments, Attachments) maps to Dynamics 365 Cases and Annotations via the Dataverse API. The key architectural difference is that Zendesk uses a Tickets-as-cases model while Dynamics 365 Customer Service uses Cases with separate Email, Phone, Chat channels. We configure the channel routing, SLAs, and case forms in the target org before migration. Workflows and Zendesk AI features do not migrate; we deliver an automation inventory for rebuild in Power Automate or Dynamics 365 Copilot Studio.

## Related migrations

[![](https://flitstack.ai/platforms-trim/dynamics-365-sales.webp) Migrate to **Dynamics 365** Every source we move into Dynamics 365, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/dynamics-365-sales)

### [Dynamics 365 implementation](https://flitstack.ai/services/dynamics-365-implementation)

[Set up Dynamics 365 and migrate into it as one engagement.](https://flitstack.ai/services/dynamics-365-implementation)

[See the service →](https://flitstack.ai/services/dynamics-365-implementation) [**Pipedrive to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/pipedrive/to/dynamics-365-sales) [**Field Services Workflow and Logistics to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/field-services-workflow-and-logistics/to/dynamics-365-sales) [**ActiveCampaign to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/activecampaign/to/dynamics-365-sales) [**Bitrix24 to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/bitrix24/to/dynamics-365-sales) [**HubSpot to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/hubspot/to/dynamics-365-sales) [**Odoo CRM to Dynamics 365** Mapping · history · rollback](https://flitstack.ai/migrations/crm/odoo-crm/to/dynamics-365-sales) [**Zendesk Sell to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/zendesk-sell/to/hubspot) [**Zendesk Sell to Pipedrive** Mapping · history · rollback](https://flitstack.ai/migrations/crm/zendesk-sell/to/pipedrive) [**Zendesk Sell to Odoo CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/zendesk-sell/to/odoo-crm)

## Sources: official documentation

1. [Dynamics 365 environment strategy — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/environment-strategy-guidance-product)
2. [Import accounts, leads, or other data — Microsoft Learn (Dynamics 365)](https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/basics/import-accounts-leads-other-data?view=op-9-1)
3. [Import data (all record types) — Power Platform | Microsoft Learn](https://learn.microsoft.com/en-us/power-platform/admin/import-data-all-record-types)
4. [Execute Batch Operations on Dataverse — Microsoft Learn](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/execute-batch-operations-using-web-api)
5. [Service protection limits (Microsoft Dataverse)](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/api-limits)
6. [Entity relationship behavior — Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/entity-relationship-behavior?view=op-9-1)

Get a quote

## Moving from Zendesk Sell to Dynamics 365?

Tell us roughly how many records and objects you have. We scope the mapping and the Dynamics 365 setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
