Migrating From Zendesk to Dynamics 365 Customer Service: Plan, Pitfalls, Benefits & Costs

Microsoft Dynamics 365

26 October, 2026

Rosalinda Valenzuela

Introduction

Migrating from Zendesk to Microsoft Dynamics 365 Customer Service involves more than transferring tickets. Organizations must decide which records to preserve, how to redesign workflows, and how to maintain uninterrupted support during the transition.

For businesses already using Microsoft technologies, Dynamics 365 offers opportunities to connect customer service with sales, operations, automation, and AI. However, poor data mapping, incomplete ticket histories, and overlooked integrations can undermine these benefits.

Quick Summary

Migration scope: Tickets, customer records, conversation histories, custom fields, workflows, SLAs, and integrations require separate migration decisions.
Implementation approach: Assess the existing environment, design service processes, migrate and validate data, train representatives, and execute a controlled cutover.
Cost considerations: Licensing, historical data, integrations, communication channels, and ongoing administration affect total costs.
Biggest risk: Importing records without preserving the information, permissions, and workflows representatives need to resolve customer issues.

When Does Migrating From Zendesk to Dynamics 365 Make Sense?

Zendesk supports established ticketing, automation, and customer service operations. However, organizations using multiple Microsoft business applications may reach a point where maintaining separate service processes adds unnecessary complexity.

The decision to migrate should depend on whether Dynamics 365 addresses these challenges more effectively than improving or integrating the existing Zendesk environment.

Unified Customer Data and Service Operations:

Consider a customer contacting support about an incorrect invoice. The representative may need the original service request, account history, sales agreement, and billing information before resolving the issue. When this information lives across disconnected applications, representatives must manually assemble the customer context. Dynamics 365 Customer Service uses Microsoft Dataverse and can integrate with other Dynamics 365 applications and business systems. With appropriate configuration, representatives can access relevant customer and case information through a more connected service environment.

However, if Zendesk’s existing workflows are effective and the main issue is limited data visibility, integrating Zendesk with Microsoft systems may be preferable to replacing it. A migration becomes more compelling when the organization also needs to redesign its service processes, unify case management with existing Microsoft applications, or reduce dependence on separate operational systems.

For a broader evaluation, see how Dynamics 365 Customer Service compares with competing platforms.

AI and Automation Readiness:

AI is another consideration, particularly for organizations looking to reduce repetitive service tasks. Depending on licensing, configuration, and feature availability, Dynamics 365 Customer Service supports capabilities such as case summaries, knowledge assistance, response drafting, and AI-assisted workflows.

Power Automate and related Microsoft services can extend automation across applications. The business case should focus on measurable improvements rather than the availability of AI features alone.

According to an August 2026 Gartner survey of 199 customer service and support leaders, AI spending increased by 38%, while overall service and support budgets grew by only 2%. This spending pressure makes it important to establish whether AI tools actually reduce manual work, improve resolution quality, or help representatives respond more effectively. Zendesk also provides AI capabilities. Organizations should compare how each platform supports their specific requirements rather than assuming that adopting Dynamics 365 automatically delivers better AI outcomes.

Platform Consolidation:

Dynamics 365 can support connections with Microsoft Teams, Power BI, Power Automate, SharePoint, and other business applications. For organizations already invested in these technologies, platform alignment can simplify certain integrations, improve reporting consistency, and support shared governance practices.

Nevertheless, consolidation should not be treated as a guaranteed source of cost savings. Licensing, configuration, additional services, and ongoing administration must all be considered.

How to Assess Your Zendesk Instance Before Migrating

A migration assessment should identify what exists in Zendesk, how its components interact, and which capabilities the business still requires. Without this assessment, teams may discover too late that a ticket field controls an important escalation, an integration depends on a particular status, or an automation supports a process that was never documented.

What Should You Inventory?

Zendesk component	What to assess
Tickets	Volume, status, age, priority, ownership, and retention requirements
Users and organizations	Customer relationships, duplicate records, and account hierarchies
Custom fields	Data types, identifiers, allowed values, and dependencies
Triggers and automations	Conditions, actions, execution order, and business purpose
Macros	Frequently used responses and repetitive representative actions
SLA policies	Targets, business hours, escalation rules, and exceptions
Help Center	Articles, categories, attachments, and access permissions
Integrations	ERP, CRM, billing, telephony, portals, and external applications
Service channels	Email, chat, messaging, voice, and web forms
Reports and views	Operational metrics, queue visibility, and reporting requirements

Custom fields deserve particular attention. A field that appears straightforward in the Zendesk interface may be referenced by several triggers, reports, and integrations. Changing its values or mapping it incorrectly can affect processes beyond the ticket record.

A reliable field-mapping dictionary should document the original field identifier, business meaning, data type, accepted values, transformation rules, and intended Dataverse column.

The important distinction is between migrating data and preserving how that data is used. A technically successful import does not necessarily mean that the service process will continue working.

What Should You Retire Instead of Migrating?

Not every existing configuration needs to survive the transition.

Organizations should classify Zendesk components into four categories:

Retain: Required information and processes that remain valuable.
Redesign: Processes that serve a valid purpose but would work better through Dynamics 365 capabilities.
Replace: Functionality that can be handled through a different native feature or integration.
Retire: Unused fields, outdated macros, duplicate configurations, and obsolete workflows.

This assessment reduces unnecessary customization and prevents teams from reproducing years of accumulated complexity in the new system.

How Zendesk Data Maps to Dynamics 365 Customer Service

Zendesk and Dynamics 365 have different data structures. While many records have functional equivalents, migration requires more than matching field names. The following table provides a practical starting point.

Zendesk component	Potential Dynamics 365 equivalent	What requires attention
Tickets	Cases	Status, priority, ownership, and customer relationships
Ticket comments	Dataverse notes, activities, or appropriately designed custom records	Conversation order, authorship, and public/private visibility
End users	Contacts	Customer identity and account relationships
Organizations	Accounts	Duplicate records and organizational structure
Agents and groups	Users, teams, and queues	Security roles, assignment, and routing
Custom fields	Dataverse columns	Data types, option values, and dependencies
Triggers and automations	Business rules, Power Automate, routing, or other platform capabilities	Workflow logic and execution behavior
Macros	Email templates, quick replies, or configured actions	Representative workflow and available functionality
SLA policies	SLAs and SLA KPIs	Service targets, working hours, and pause conditions
Help Center articles	Knowledge articles	Formatting, categorization, and permissions
Views	Views, dashboards, and queues	Filtering, access, and representative responsibilities
Attachments	Dataverse file storage, notes, or integrated document storage	File relationships, availability, and security

These mappings are not direct one-to-one conversions. The appropriate target depends on the business process and the Dynamics 365 environment.

Core Records: Tickets, Users, and Organizations

Moving a Zendesk ticket into a Dynamics 365 case should preserve the information necessary to understand and manage the customer issue. Consider an illustrative Zendesk ticket containing eight customer replies, three internal notes, two attachments, and an escalation to a specialist group.

Creating a Dynamics 365 case with the correct customer name and ticket description would not be enough.

The target environment must account for the conversation chronology, attachment relationships, internal note visibility, original ownership, and escalation requirements. For historical records, preserving the original Zendesk ticket ID is particularly useful. It provides traceability during reconciliation, troubleshooting, and archive retrieval.

Workflows: Triggers, Automations, Macros, and SLAs

A frequent implementation mistake is treating every Zendesk trigger as a Power Automate flow. Dynamics 365 offers several ways to implement business logic. Case assignment may be handled through routing, while record validation could be addressed through business rules or other configuration. Cross-application activities may require Power Automate.

The correct approach is to document what each Zendesk workflow accomplishes and select the most appropriate Dynamics 365 mechanism. SLA policies also require careful consideration. Response and resolution targets must be tested against the target environment’s calendars, applicable conditions, and pause behavior.

Microsoft entitlements can support service eligibility and allowances, but they should not be treated as direct replacements for Zendesk SLA policies.

Knowledge Articles and Communication Channels:

Zendesk Help Center articles may need to be restructured before becoming Dynamics 365 knowledge articles. Categories, formatting, attachments, embedded links, and permissions should all be reviewed. Communication channels require separate planning.

Migrating tickets does not automatically reproduce Zendesk Talk, chat, or messaging configurations. Voice numbers, routing behavior, messaging providers, and other channel dependencies may require separate implementation work.

Organizations should review chat capabilities in Dynamics 365 Customer Service while determining whether their requirements call for Customer Service, Contact Center, or a combination of capabilities.

How Much Historical Data Should You Migrate?

One of the most consequential migration decisions concerns historical tickets. Moving every record into Dynamics 365 may provide convenient access, but it can increase migration effort, validation requirements, and storage consumption.

The alternative is not necessarily deleting historical information. Organizations can preserve records in an accessible archive while migrating only the information required for active service operations.

Full History, Recent Window, or Open Tickets Only?

Strategy	Best suited for	Main consideration
Full historical migration	Teams that regularly reference older cases within active workflows	Higher data volume, storage, and validation requirements
Recent history plus archive	Teams that need recent cases but must retain older records	Requires reliable archival access and search
Open tickets only	Teams that rarely need closed cases in the new environment	Requires an accessible historical reference system

For example, a company with ten years of support records may choose to transfer open tickets and the most recent 24 months of resolved cases while retaining older conversations in a searchable archive.

Attachments and Dataverse Storage

Attachments are often more complicated than ticket metadata because Zendesk associates them with individual ticket comments.

A ticket export does not automatically establish that every attachment has been retrieved, transferred, and linked correctly.

A practical reconciliation process should classify attachments as follows:

Status	Meaning	Required action
Successfully migrated	File is accessible and linked to the intended case or activity	Accept
Approved exclusion	File was intentionally excluded under an agreed policy	Record the exception
Unexpectedly missing	File should exist but cannot be retrieved	Investigate before sign-off

Migration teams should also consider file sizes, access permissions, storage locations, and long-term retrieval requirements. Dataverse capacity is divided into database, file, and log storage, and different retention choices can affect consumption.

AlphaBOLD’s guide to Dynamics 365 storage capacity planning explains the storage considerations organizations should evaluate before importing large volumes of historical information.

The Zendesk to Dynamics 365 Migration Plan, Step by Step

A successful migration needs a defined sequence of activities, operational ownership, and measurable acceptance criteria.

Step 1: Design the Target Service Process

Define how cases will be created, prioritized, assigned, escalated, and resolved. Rather than recreating every Zendesk workflow, identify opportunities to simplify processes and use native Dynamics 365 capabilities.

Step 2: Configure Dynamics 365 Customer Service

Set up case management, customer records, security roles, queues, SLAs, knowledge management, and required integrations. Voice and digital channels may require separate configuration, licensing, and testing.

Step 3: Migrate and Validate the Data

Test the migration using representative tickets, including conversations, attachments, internal notes, and custom fields. Validate record relationships, permissions, ownership, and historical accuracy.

Incremental migrations also require careful synchronization to prevent duplicate or missing records. Zendesk export limitations, data transformations, and attachment handling should be addressed before the final transfer.

Step 4: Train Agents and Run a Pilot

Test everyday service activities with a selected group of agents before go-live. Confirm they can retrieve customer histories, manage cases, use knowledge articles, and complete escalations. Use their feedback to refine workflows and training.

Step 5: Cut Over and Retire Zendesk

Choose between a big-bang or phased transition based on operational complexity. Plan final data synchronization, channel routing, and recovery procedures before switching systems.

Planning Your Zendesk to Dynamics 365 Migration?

AlphaBOLD's Dynamics 365 consultants help assess your Zendesk environment, identify migration risks, redesign workflows, and develop a tailored roadmap for a successful transition.

Request a Consultation

Common Zendesk Migration Mistakes to Avoid

The following mistakes can affect operational performance even when data migration tools report successful imports.

Recreating Every Zendesk Process: Replicating existing workflows without questioning their purpose can introduce unnecessary customization.
What to do instead: Document the intended business outcome of each process and determine how Dynamics 365 should support it.
Migrating Inconsistent or Duplicate Data: Duplicate customer records, outdated contact information, and incompatible field values can create problems with case ownership, routing, and reporting.
What to do instead: Establish data-cleansing rules and validate mappings against the actual production configuration.
Turning Every Trigger Into a Flow: Creating separate Power Automate flows for processes already supported by native Dynamics 365 features can add administration and maintenance requirements.
What to do instead: Evaluate business rules, routing, SLAs, and platform capabilities before selecting a workflow mechanism.
Assuming Every Attachment Was Migrated: Ticket counts alone cannot establish whether historical records are complete.
What to do instead: Reconcile attachment inventories and document exclusions, missing files, and successful transfers.
Overlooking Communication Channels: Migrating cases without configuring email, voice, chat, or messaging can leave the organization unable to handle customer requests as expected.
What to do instead: Treat channel configuration and end-to-end communication testing as essential migration activities.
Skipping Operational Testing and Training: A technically successful migration can still create longer handling times if representatives cannot locate information or complete familiar tasks.
What to do instead: Use realistic service scenarios, involve operational users, and establish go-live acceptance criteria.

What Does a Zendesk to Dynamics 365 Migration Cost?

Migration costs depend on the capabilities being implemented, the condition of the source environment, and the level of change required. Licensing is only one part of the total cost.

Dynamics 365 Customer Service Licensing Costs:

Edition	Published price	General positioning
Customer Service Professional	$50 per user/month	Core case management and service functionality
Customer Service Enterprise	$105 per user/month	Advanced customer service and AI-enabled capabilities
Customer Service Premium	$195 per user/month	Integrated customer service and contact center capabilities

Prices are in USD, billed annually, and exclude taxes. Additional costs may apply for AI capabilities, contact center services, integrations, and storage, depending on licensing and configuration.

Organizations should evaluate each user’s activities rather than selecting a license solely by comparing product names.

Implementation and Migration Cost Drivers:

Cost driver	What increases complexity
Data migration	High ticket volumes, extensive history, inconsistent fields, and attachment handling
Workflow configuration	Complex routing, custom escalation rules, and automated processes
Integrations	ERP, billing, CRM, identity, and external application dependencies
Service channels	Voice, messaging, chat, and contact center requirements
Reporting	Custom dashboards, historical metrics, and cross-system analytics
Change management	User training, adoption, process documentation, and support
Ongoing administration	Storage, monitoring, governance, maintenance, and enhancements

Historical data is an important consideration. A company that chooses to archive older tickets may reduce the volume imported into Dynamics 365, but it must still account for archive storage, search functionality, access controls, and retention requirements.

Conversely, migrating the complete history may reduce the need to consult separate systems while increasing migration and validation effort.

For a wider budgeting framework, see AlphaBOLD's guide to Dynamics 365 implementation costs.

What Should You Measure After Go-Live?

A migration should be evaluated against operational outcomes, not simply whether Dynamics 365 is live.

Establish a baseline before migration and compare performance after the environment has stabilized.

KPI	What it demonstrates
First response time	How quickly customers receive an initial qualifying response
Average resolution time	How efficiently comparable customer issues are resolved
Average handle time	How much representative time is required per interaction
SLA compliance	How consistently service commitments are met
Case deflection	How effectively self-service resolves requests without representative intervention
Copilot adoption and effectiveness	Whether AI assistance is used and contributes to useful outcomes

For example, reduced handling time is not automatically evidence of better service. It should be evaluated alongside resolution quality, repeat contacts, and customer satisfaction.

Likewise, Copilot usage statistics alone do not establish ROI. Teams should assess whether summaries are accurate, suggested responses are useful, and knowledge retrieval reduces manual research.

AlphaBOLD’s article on Copilot in Dynamics 365 Customer Service explains how these capabilities can support customer service workflows.

What Can Connected Service Data Enable?

In a separate Customer Service implementation, AlphaBOLD helped a semiconductor and electronic hardware company embed a Copilot agent into its Dynamics 365 environment. The solution was designed to help support users retrieve relevant historical case context and reduce manual research across systems.

Although this was not a Zendesk migration, it illustrates the value of making reliable historical service information accessible within representative workflows.

It also reinforces an important migration principle: AI-assisted service depends on the quality, accessibility, and structure of the information available to the system.

Make Your Move to Dynamics 365 Count

Migrating from Zendesk creates an opportunity to improve more than ticket management. AlphaBOLD helps organizations configure Dynamics 365 Customer Service, connect business applications, modernize service workflows, and establish a foundation for measurable operational improvements.

Request a Consultation

Conclusion

Migrating from Zendesk to Dynamics 365 Customer Service requires three important decisions: what data to preserve, which processes to redesign, and how to transition without disrupting customer support. For organizations already using Microsoft technologies, Dynamics 365 can provide a more connected foundation for service operations, automation, analytics, and AI. Achieving those benefits, however, depends on careful planning, accurate data migration, and workflows designed around business needs.

FAQs

Can You Migrate Zendesk Tickets and Attachments to Dynamics 365?

Yes. Zendesk tickets, conversation histories, attachments, and customer records can be migrated to Dynamics 365. However, data mapping, permissions, and record relationships must be validated to ensure information remains accessible and accurate.

Can You Migrate From Zendesk to Dynamics 365 Without Downtime?

A phased migration can minimize service disruption, but zero downtime cannot be guaranteed. Proper planning, incremental data synchronization, testing, and a controlled cutover help maintain service continuity.

How Long Does a Zendesk to Dynamics 365 Migration Take?

Migration timelines depend on data volume, integrations, workflow complexity, and service channels. Organizations should account for system configuration, data validation, user testing, and cutover rather than relying on generic estimates.

Explore Recent Blog Posts

Microsoft Dynamics 365