Migrate from Zendesk Sell to Microsoft Dynamics 365 Sales

Zendesk Sell Leads map directly to Microsoft Dynamics 365 Sales Leads. 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.

Sell Contacts map to Dynamics 365 Contacts with standard fields (full name, email, phone, address) preserved. 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.

Sell Companies map to Dynamics 365 Accounts. 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.

Sell Deals map to Dynamics 365 Opportunities. 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.

Sell Pipelines are custom workflow containers that have no direct Dynamics 365 equivalent. 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.

Sell Stages are children of Pipelines with ordinal position and win/loss flags. 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.

Sell Tasks with due dates, assignees, and completion status map directly to Dynamics 365 Tasks. Subject, description, priority, and ActivityDate transfer. Owner assignment resolves by email match against Dynamics 365 Users. Completed status maps to Dynamics 365 Task.statuscode = Completed.

Sell call logs, outcomes, and duration data map to Dynamics 365 PhoneCall records. Call disposition maps to Dynamics 365 phonecalldirection or a custom field. Call duration migrates to duration field or a custom integer column. Sell call recordings are audio files requiring separate file transfer to Dynamics 365 SharePoint or blob storage; we flag this as a separate file-migration step and do not include audio transfer in standard scope.

Sell Notes attached to Contacts, Deals, Leads, or Companies map to Dynamics 365 Annotations (the Dataverse Note equivalent). Note body migrates as notetext. Parent reference (Sell's parent_type and parent_id) resolves to the Dynamics 365 entity logical name and id for the linked record. Rich-text formatting in Sell Notes is preserved where possible; complex HTML is simplified to plain text.

Sell Users (sales reps, admins) export with email, role, and territory. We match by email against the Dynamics 365 destination User table. Any Sell User without a matching Dynamics 365 User enters a reconciliation queue for the customer's admin to provision before record import resumes. Territory assignments migrate as a reference document for reconfiguration in Dynamics 365.