Zendesk has confirmed that Zendesk Sell and its mobile app will be retired on 31 August 2027. Existing customers can continue using Sell until that date, but organisations should start planning their replacement well before the deadline.
The immediate priorities are to understand which business processes depend on Sell, test what data can be extracted, document integrations and decide what the replacement CRM needs to do. Choosing another platform is only one part of the project. Data quality, workflow design, reporting, integrations and user adoption will determine whether the migration succeeds.
Starting early creates time to compare packaged, semi-bespoke and bespoke CRM options without forcing the business into a rushed like-for-like replacement.
What does the Zendesk Sell retirement mean for customers?
Zendesk Sell will remain accessible until 31 August 2027. Zendesk has partnered with Pipedrive to provide customers with a potential migration route, but Sell users can also evaluate other sales CRM products.
The deadline also has important implications for data. Zendesk states that Sell data will be deleted when the Sell subscription ends or from 31 August 2027, whichever happens first. Once deletion begins, it cannot be reversed.
Organisations should therefore avoid treating the final retirement date as their migration deadline. A replacement CRM should ideally be selected, tested and operating before access to Sell ends.
What can you export from Zendesk Sell?
Zendesk's standard account export can include:
- Leads
- Contacts
- Deals
- Notes
- Tasks
- Smart lists
- Full account data
- The Total Sales report
However, Zendesk says the standard export cannot include activity history, appointments, emails, call logs or documents. Some system fields, including Parent Company and Parent Company ID, may only be available through a smart list export.
This distinction matters. A CSV containing contacts and deals may be enough for a simple sales database, but it may not preserve the complete history or context that sales teams use every day.
The Zendesk Sell Core API documentation lists additional resources including calls, documents, text messages, pipelines, stages, products and line items. A technical assessment can determine whether relevant information can be extracted through the API, obtained from an integrated source system or archived separately. Availability will depend on the data type, account permissions, subscription and the way each integration was configured.
Before committing to a migration plan, create a field-level inventory showing:
- Where each important item of data is stored
- Whether it can be exported through CSV, an API or its original source
- How it relates to contacts, companies, deals and activities
- Whether it must remain searchable in the new CRM
- How long it needs to be retained
- Who is responsible for validating it
Run a test export early. Do not wait until the final weeks of the subscription to discover that important relationships, attachments or historical records require a different extraction method.
Should you move from Zendesk Sell to Pipedrive?
Pipedrive is a credible option to assess, but it is not automatically the right choice for every Zendesk Sell customer.
Zendesk selected Pipedrive as its transition partner and highlights its native Zendesk integration and migration tools. Organisations with relatively standard sales pipelines may find that this offers a straightforward route.
The decision should still be based on your requirements rather than the convenience of the recommended migration path. A technically easy move can become expensive if the new CRM requires users to work around missing processes for several years.
Ask whether the proposed replacement can support:
- Your lead qualification and sales stages
- Multiple pipelines, territories or business units
- Custom fields and relationships
- Approval and handover workflows
- Forecasting and management reporting
- Email, calendar and telephony processes
- Connections with Zendesk Support
- Finance, ERP, quoting and operational systems
- Mobile and remote working
- Access controls, audit requirements and data governance
- Planned growth and future process changes
A short proof of concept using real workflows and representative data is usually more informative than a feature checklist or sales demonstration.
What are the main Zendesk Sell alternatives?
Most Zendesk Sell customers will compare a handful of established sales CRMs with a tailored option. No single product is the best alternative for everyone. The right choice depends on how standard your sales process is, whether you still use Zendesk Support and how much of the wider business relies on CRM data.
| Alternative | Often suits | Check before choosing |
|---|---|---|
| Pipedrive | Teams with a straightforward, pipeline-led sales process who want the officially supported route | How its Zendesk integration and migration tools handle your data, and whether multiple pipelines, approvals and reporting fit without workarounds |
| HubSpot Sales Hub | Organisations that want sales and marketing in one platform | Which features sit in higher tiers, how costs grow with seats, and how Zendesk Support tickets will appear to sales users |
| Salesforce Sales Cloud | Larger or more complex sales teams with administrator capacity | Configuration and licence costs, the internal or partner resource needed to run it, and integration effort |
| Other packaged CRMs (for example Zoho CRM or Freshsales) | Smaller teams looking for a lower-cost, general-purpose CRM | Data import options, integration coverage and long-term fit as processes become more specific |
| Bespoke or semi-bespoke CRM | Businesses whose quoting, approvals, service handovers or account structures don't fit a standard sales CRM | Initial investment, delivery timescale and who will support and develop the system |
Whichever products you shortlist, test them against the same requirements and a sample of real Sell data. The custom CRM vs HubSpot or Salesforce comparison explains when a packaged CRM, a bespoke build or a hybrid of the two makes most sense.
What type of CRM replacement should you choose?
The right replacement depends on how closely your organisation follows a standard sales process and how much of its wider operation depends on CRM data.
| Replacement approach | Likely to suit | Points to examine |
|---|---|---|
| Off-the-shelf CRM | Teams with conventional lead, contact and pipeline management requirements | Subscription costs, available integrations, configuration limits and long-term fit |
| Configured or semi-bespoke CRM | Organisations that can use an established platform but need tailored workflows, integrations or reporting | Which requirements can be configured and which will require custom development |
| Bespoke CRM | Organisations with complex processes, unusual data relationships or a need to connect sales directly with operational systems | Initial investment, delivery timescale, governance, support and ownership responsibilities |
A bespoke system is not always necessary. If a standard CRM meets the important requirements with limited configuration, it may be the quickest and most economical answer.
Conversely, forcing complex quoting, approvals, service handovers or account structures into a conventional sales CRM can recreate the same inefficiencies that prompted the replacement project. In those cases, bespoke software development can provide a CRM designed around the actual business process. Our comparison of custom CRM vs HubSpot or Salesforce sets out when each route makes sense, including the hybrid option of keeping a packaged CRM and building only the part it handles poorly.
How should you plan a Zendesk Sell migration?
A controlled CRM replacement should be treated as a business change programme, not a one-off data import.
1. Discover how Sell is really being used
Document pipelines, custom fields, reports, automations, integrations and manual workarounds. Speak to salespeople, managers, administrators and the teams that receive information from sales.
Vivato's CRM discovery workshops can help map the current system, identify dependencies and define what the replacement must achieve.
This stage often reveals that the documented sales process and the process users actually follow are different.
2. Define the minimum viable replacement
Separate essential launch requirements from improvements that can follow later. The first release must support business continuity, but it does not need to reproduce every historical configuration.
Priorities might include:
- Managing active leads and opportunities
- Preserving essential customer and deal history
- Maintaining sales-to-service handovers
- Recreating critical reports
- Connecting email, finance or operational systems
- Giving users a clear way to complete everyday tasks
A defined project scope keeps the migration focused and provides a basis for realistic budgets, responsibilities and acceptance criteria.
3. Map and clean the data
Create explicit mappings between Zendesk Sell fields and the target CRM. Decide how custom fields, tags, pipelines, stages, owners and historical users will be represented.
This is also an opportunity to resolve:
- Duplicate contacts and companies
- Inconsistent stage names
- Obsolete fields
- Missing ownership
- Invalid email addresses
- Unused tags and smart lists
- Records that should be archived rather than migrated
Cleaning data before migration is usually more effective than moving every problem into the new system.
4. Rebuild integrations deliberately
List every system that reads from or writes to Zendesk Sell. This may include Zendesk Support, email and calendar services, finance software, quoting tools, marketing platforms, telephony, data warehouses and internal applications.
Each connection needs an owner, data-flow definition, error-handling process and test plan. Vivato provides API and third-party integration services for organisations that need their replacement CRM to exchange data reliably with existing systems.
Do not assume that a connector with the same name will reproduce the behaviour of the current integration.
5. Rehearse the migration and cutover
Run at least one trial migration with representative data. Validate record counts, field values, relationships, ownership, permissions and reports.
The cutover plan should specify:
- When changes in Sell will stop
- When the final export will run
- How late changes will be captured
- Who validates the migrated data
- When integrations will switch
- How users will report problems
- Whether Sell will remain available temporarily for reference
Where possible, allow a controlled period in which selected users can verify the new CRM before it becomes the sole working system.
6. Train users around their jobs
CRM training should reflect the tasks users perform, not simply describe every screen. Salespeople need to know how to qualify leads, update opportunities and plan follow-ups. Managers need confidence in forecasts and reports. Administrators need procedures for permissions, configuration and data quality.
Collect feedback after launch and prioritise improvements. A CRM replacement is successful when the new system becomes a dependable part of the sales process, not merely when the data import completes.
How can Vivato help replace Zendesk Sell?
Vivato can support the CRM replacement and migration from initial assessment through to long-term operation.
Our work can include:
- Auditing how Zendesk Sell is used
- Documenting workflows, data and integrations
- Comparing packaged, semi-bespoke and bespoke approaches
- Defining requirements and a phased delivery roadmap
- Designing and building a tailored CRM where appropriate
- Developing data extraction and transformation processes
- Rebuilding integrations with Zendesk Support and other systems
- Testing migration accuracy and supporting cutover
- Providing ongoing software support and hosting
The goal is not to steer every organisation towards a bespoke build. It is to identify the most appropriate replacement, protect important information and ensure the resulting CRM supports the way the business needs to operate.
Frequently asked questions
When is Zendesk Sell being discontinued?
Zendesk Sell and its mobile app will be retired on 31 August 2027. Customers can continue using the product until that date, although data deletion may begin earlier if the Sell subscription ends before then.
Do we have to migrate from Zendesk Sell to Pipedrive?
No. Zendesk has partnered with Pipedrive and presents it as a migration option, but customers can evaluate Pipedrive, other packaged CRMs, semi-bespoke solutions or a bespoke CRM.
What are the best alternatives to Zendesk Sell?
Common shortlists include Pipedrive (Zendesk's migration partner), HubSpot Sales Hub, Salesforce Sales Cloud and lower-cost CRMs such as Zoho CRM or Freshsales. Businesses with specialised workflows may be better served by a semi-bespoke or bespoke CRM. Compare options against your own requirements and a sample of real data rather than a feature list.
Can all Zendesk Sell data be moved through a CSV export?
No. Zendesk states that the standard export does not include activity history, appointments, emails, call logs or documents. Some data may require API extraction, retrieval from an integrated provider or a separate archive. Test the available methods before finalising the migration scope.
Will Zendesk Support also be retired?
The announcement applies to Zendesk Sell and the Sell mobile app. It does not announce the retirement of Zendesk Support. Organisations that continue using Zendesk Support should include the connection between support and their replacement sales CRM in the migration requirements.
When should we start planning the migration?
Start now if Sell supports active sales processes, integrations or a significant volume of historical data. Early discovery and test exports provide time to resolve data gaps, compare replacement options and rehearse the cutover before the retirement deadline.
Plan your Zendesk Sell replacement before the deadline
The retirement of Zendesk Sell creates a fixed deadline, but it can also provide a useful opportunity to improve how sales information supports the wider organisation.
The strongest migration plans begin with business requirements and data, not a preferred product. By understanding what needs to be preserved, what should be improved and how the CRM connects with other systems, you can choose a replacement that works beyond the initial cutover.
Speak to Vivato about assessing your Zendesk Sell setup and creating a practical CRM replacement roadmap. An early conversation can establish the likely migration scope, identify data risks and clarify whether an off-the-shelf, semi-bespoke or bespoke solution is the best fit.
