Switching From Zendesk: What to Export, What Breaks, and How Long It Takes

Step 1: work out what you are actually replacing

Zendesk is a bundle: ticketing, a help centre, chat, reporting, sometimes a phone system. Most small teams use a quarter of it and pay for all of it.

So list what you actually touched in the last thirty days. If the honest answer is "the chat widget, the shared inbox and the help centre", this migration is easy. You can also keep Zendesk so chat and AI sit in front of the ticketing you already trust.

Step 2: export everything while you are still paying

Once a subscription lapses the admin area closes, and rules you never wrote down are gone for good. Do this on a paid account, in one sitting, and put the files somewhere the whole team can find them.

Triggers and automations are the sneaky one: they are configuration, not data, so there is rarely a tidy file to download. Screenshot every rule. And do not plan to reimport years of tickets. Keep them as a searchable archive, and import only the contacts and the answers.

Step 3: write down your current numbers

Take ninety days of reporting and record six things: conversations per week, first response time, time to resolve, satisfaction score, when messages arrive, and your twenty most common subjects.

This takes twenty minutes and it is the highest-value thing on this page. Skip it and in six weeks you cannot tell whether the switch helped. You will have only opinions, and the loudest usually belongs to whoever disliked the change most. Those twenty subjects also become your first AI test script.

Step 4: know what breaks, before it breaks

Zendesk is a deep platform built for large support organisations, and depth is a real feature, not just a cost. What carries straight over is the conversation itself: EzyConn answers from your help centre pages and uploaded documents, shows the source, and hands the chat to your team, assigned by round robin, least busy, most recently active or by hand.

Step 5: rebuild, which is smaller than you fear

Four things. Install the widget, one snippet in your site template. Point the AI at your help centre so it learns your answers, a crawl of minutes rather than days. Set routing, meaning who picks up which topic. Set business hours, so the AI covers the night shift and humans join when they are in.

The fourth decision is where your team will actually work. Conversations arrive natively inside Microsoft Teams, Slack or Zoom. Native here means the agent types a reply into the Teams or Slack message itself and the customer sees it, rather than getting a notification linking to yet another dashboard. That removes the usual reason support tools go unused: nobody wants a fifth tab open all day.

Step 6: run both at once for two weeks

Do not switch everything on a Monday morning. Two safe patterns, both work.

Split by page. Leave Zendesk as it is on your highest-stakes pages, such as checkout, and put EzyConn on the help centre, pricing and blog pages where repeat questions live. Real volume, low risk.

Split by stage. Let EzyConn answer first everywhere and forward anything unresolved into Zendesk by email, where it lands as a normal ticket. Your workflows, macros and SLAs carry on untouched.

Step 7: the test list before you switch the old one off

• Ask the AI your twenty most common questions. Score each answer honestly.
• Ask something it should refuse, like a refund outside policy, and check it hands over instead of guessing.
• Send a message at 11pm.
• Do it all on a phone, on mobile data, not office wifi.
• Hand a live conversation to a person mid-sentence and check nothing is lost.
• Test a second language if you have overseas customers.
• Confirm notifications reach the right people, and nobody else is woken up.
• Check page load speed before and after.
• Ask someone outside support to use it cold.

A realistic timeline

What changes on the invoice

Zendesk charges per agent per month and bills automated resolutions on top. Per-agent pricing means every person on the rota costs the same, even a weekend stand-in who logs in twice. We pulled that apart in Zendesk pricing explained.

EzyConn is flat. There is a free plan at $0 forever with 1 agent seat plus the owner, 500 messages a month and one chatbot. Paid plans run Starter at $25 and Professional at $95 per month, priced per workspace rather than per agent, and annual billing takes 20% off. AI runs on GPT-4o and Claude and is included on every plan, with no per-resolution fee.

What each plan sets is messages and seats: 500 messages a month on Free, 5,000 on Starter and 25,000 on Professional, with 1, 3 and 10 agent seats plus the owner. Check that against the volume from step 3, because that number, with the size of your rota, decides your plan. See the pricing page and the Zendesk alternative comparison.

When to keep Zendesk alongside EzyConn

Put a cheaper chat and AI layer in front of Zendesk and revisit the seat count at renewal. We went through that trade in is Zendesk worth it.

Questions people ask before they switch

Competitor pricing is described as a model rather than a figure, since published amounts change.