What we do
Tools
Industries
Department
How we workLet's talk →
Home/Zendesk/Is Zendesk a CRM? Sell Is Retiring, Then What
Zendesk

Is Zendesk a CRM? Support Isn't, and Zendesk Sell Is Being Retired

Zendesk Support was never a sales CRM: it has tickets, users and organizations, not deals or a pipeline. Zendesk did sell a CRM, Zendesk Sell, but it's being retired. And "Sunshine" now means two different things, one of them already gone. Here's where each piece stands, and what to do if you were counting on one of them.

Where each Zendesk product stands now

Zendesk Support (and Suite): a help desk. It stores who contacted you and their tickets, plus any custom fields and custom objects you add. No pipeline, deal stages or forecasts.

Zendesk Sell: Zendesk's separate sales CRM. Zendesk has announced it retires on August 31, 2027, and data is deleted after that. Check the notice in your own account for the exact terms.

Sunshine Conversations: still active. It's the messaging API underneath Zendesk messaging, for WhatsApp, Messenger, SMS and in-app chat.

The original Sunshine platform (legacy custom objects): removed in July 2026. Custom objects now live in Support itself.

Admin Center Objects and rules Custom objects

What to do, depending on what you have

If this is you What to do now The trap
Your sales team runs on Zendesk Sell Pick a replacement CRM now and move while Sell still works, so you can check records side by side. Leaving it until the last month. Moving deals is quick; rebuilding the Sell-to-Support link and the reports people rely on is the slow part.
Support only, and agents want account context on tickets You may not need a CRM. Custom objects or a sidebar app can put plan, orders or equipment beside each ticket. Typing that data in by hand. It goes stale within weeks unless the system that owns it keeps it updated.
You already run HubSpot or Salesforce Keep it as the CRM. Use its Zendesk app for visibility and sync only the fields support truly needs. Two-way sync on the same field, which lets each system overwrite the other.
Something you built read from legacy Sunshine custom objects Assume it's broken. Those objects and their API were removed, so rebuild on the new custom objects. Silent failures: an integration that used to write to Sunshine may still run and just do nothing.

Leaving Zendesk Sell before it shuts down

Sequence beats speed here. Each step keeps something from getting lost on the way out.

  1. 1

    List what Sell is actually doing for you

    Not just leads and deals. Note the pipelines and stages, custom fields, sequences, the reports someone reads every Monday, and the link that shows Sell data inside Zendesk Support.

  2. 2

    Export everything, then check the export

    Run Sell's export and open the files. Compare record counts with what you see in Sell, and look specifically for notes, emails, calls and documents.

    Watch for: history that isn't in the files. Activity is the part teams most often find missing, and it can't be pulled once the account is deleted.

  3. 3

    Choose the replacement CRM by how support and sales share customers

    If agents need deal or account data on tickets, check that the new CRM has a working Zendesk app, or plan a sync. Options worth comparing are on our CRM for small business page, including Pipedrive, HubSpot and Salesforce.

  4. 4

    Move the data with Sell IDs kept

    Store each Sell record's ID on the new record. It's what lets you re-run the move for anything that changed during the switch, and match old reports to new ones.

  5. 5

    Rebuild the link to Zendesk Support, then switch off Sell

    Point Zendesk at the new CRM, confirm agents see the right account on a few real tickets, and only then stop working in Sell.

Where should account data live: in Zendesk, or beside it?

Most teams asking whether Zendesk is a CRM really want one thing: the customer's plan, orders or equipment on the ticket. There are two ways to get it there.

Inside Zendesk

Custom fields and custom objects

  • Records such as subscriptions, assets or orders, linked to tickets, users and organizations with lookup relationship fields.
  • Triggers, views and routing can use them, so a premium plan can jump the queue.
  • Only as current as whatever keeps them updated from the system that owns the data.
Beside Zendesk

A sidebar that reads the other system live

  • Always current, because nothing is copied.
  • Good for data that changes hourly, like order status or balances.
  • Zendesk's rules can't act on it, since it never becomes Zendesk data.

Copy in what routing and reporting need, such as tier, plan and renewal date. Read live what agents only look at. Most good setups use both.

Account context on tickets, without buying Zendesk Sell

A business on Zendesk Support with order and account data in its ERP

Before

Agents wanted order history and account tier on every ticket. The obvious suggestion was to add Zendesk Sell.

Nobody at the company tracked deals. They needed context, not a sales pipeline.

After

n-frames built a sync from the ERP into Zendesk custom fields, so order history and tier sit on each ticket and stay current.

No second product to license, and nothing to migrate now that Sell is being retired.

Sunshine Conversations, if messaging is what you came for

Sunshine Conversations came to Zendesk with its purchase of Smooch. It puts WhatsApp, Facebook Messenger, SMS, web and in-app chat behind one API, and Zendesk's own messaging runs on it. Most teams use it without ever calling it directly. You reach for the API when you want your own chat inside your app, or a bot that decides what to do with a conversation before an agent sees it.

We've used it to give one business a single thread per customer across WhatsApp and its web widget, so agents stopped piecing together two histories. If you're moving off the old Zendesk Chat at the same time, Zendesk live chat and messaging covers what changes. For syncing other systems into Zendesk generally, start with Zendesk integrations, and developers can go straight to the Zendesk API reference.

Questions people ask

Is Zendesk a CRM?

Zendesk Support isn't. It's a help desk with tickets, users and organizations, and no deals or pipeline. Zendesk's CRM was Zendesk Sell, a separate product that Zendesk is retiring on August 31, 2027.

What is Zendesk Sell?

Zendesk's standalone sales CRM: leads, deals, pipelines and contacts, priced separately from Support and Suite. It integrates with Support so both teams see the same customer. Zendesk has announced its retirement, so existing users need to move to another CRM before the shutdown date.

What happens to our data when Zendesk Sell shuts down?

Zendesk deletes it after the subscription ends or the retirement date passes, whichever comes first. Export it well before then, check the files for notes and activity history, and keep each Sell ID on the records you import elsewhere.

What is Zendesk Sunshine?

Two different things, depending on when it was written. Today it usually means Sunshine Conversations, the messaging API under Zendesk messaging. Older material means the original Sunshine platform, whose custom objects have now been removed and replaced by custom objects inside Support.

What's the difference between Sunshine and Sunshine Conversations?

Sunshine was the open customer-data platform with legacy custom objects, now removed. Sunshine Conversations is the messaging API from the Smooch acquisition, still active, used for WhatsApp, Messenger, SMS and in-app chat.

Is the Sunshine platform still around?

No. Zendesk stopped new legacy custom objects in January 2026 and removed the rest in July 2026. Anything built on that API needs rebuilding on the new custom objects. Sunshine Conversations is unaffected.

Who can build the sync between Zendesk and our real CRM or ERP?

That's work n-frames takes on: moving data off Sell, syncing plan, order or equipment records into Zendesk custom objects, and building sidebars that read the other system live. We start from the field your agents ask about most.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.