A custom support desk can beat a Zendesk renewal once you run well over a hundred agents, your tickets drive internal operations with their own states and approvals, and you want ticket history queryable in PostgreSQL. Under about 30 agents, or without engineers to own the system later, renewing is the better answer. Decide with one comparison: agents × Zendesk per-agent price × 36, against build engineers × months × $7,000 plus a yearly run cost you write down.
Zendesk charges per agent, monthly, and discounts annual billing. As a reference point, Suite Professional is $115 per agent per month on annual billing (list price checked November 21, 2026; check your contract), against $149 month to month. Each plan bundles a fixed count of AI agent automated resolutions per agent per month; past that count, resolutions are metered. Suite Enterprise with Copilot has no public number: Zendesk routes it to sales.
Zendesk list prices as of November 21, 2026. Negotiated prices differ, so confirm against your contract.
Renewal quotes rise along a few predictable axes. Hiring is the first: a support floor that grows from 60 agents to 90 adds 30 × $115, or $3,450 a month, at Suite Professional list. The plan step is second: Suite Team to Suite Professional is $55 to $115 per agent, and a team may take that step just to get a Professional feature such as admin data exports. AI and optional bundles are third, since metered resolutions past the bundled 10, Copilot at $50 and the per-agent bundles all multiply by the same agent count. That is how per-agent software is priced everywhere; it simply means support cost follows hiring.
For most support organizations Zendesk remains the sensible choice. Owning starts to pay when several rows from the lower half apply together.
The hybrid is a low-risk first project. It produces the schema and an honest read on engineering effort while 200 agents keep the tool they know.
Zendesk side: agents × $115 × 36 months (Suite Professional, annual billing). Owned side: engineers × build months × $7,000, plus Zendesk seats through the build and one month of parallel running, plus a run cost that starts in the parallel month. The crossover is the first month from which the owned running total stays at or under the Zendesk running total for good. Run cost here is our assumption and you should overwrite it: engineer-months of upkeep per year at $7,000 each, plus hosting.
Suite Professional at $115 per agent per month, annual billing, checked November 21, 2026 (list price, check your contract). Zendesk stays paid for 6, 8 and 10 months on the owned side (build plus one parallel month).
The 120-agent row in full: $147,000 of build, 8 months of Zendesk at $13,800 ($110,400), and 29 months of run cost at $5,000 ($145,000) total $402,400, against $496,800 if you renew for three years. Month 25 still favors renewing ($347,400 owned against $345,000), and month 26 is the first where owning stays ahead ($352,400 against $358,800). At 400 agents that point arrives in month 21. At 25 agents the run cost of $2,250 a month eats almost all of the $2,875 seat bill, so the gap shrinks by only $625 a month.
Only seats are counted. If you buy metered resolutions or Copilot, that spend joins the Zendesk column. If your desk drafts replies or deflects tickets with a model, it pays an LLM API for every call, and that belongs in the run-cost column. Plug your own renewal quote and usage into the 3-year build vs buy TCO calculator.
Export the list of triggers, automations, views, ticket fields, forms and groups, and tag each as live, rare or dead from its recent activity. Pull ticket counts by channel and month, and weekly active agents. One trap: per Zendesk's archiving article, tickets are archived 120 days after closing and then vanish from views, triggers and list endpoints, though search and incremental export still return them. Count history from those two. Exit check: every rule has an owner and a keep or retire decision.
The admin export writes JSON, CSV or XML. It needs Professional or Enterprise, and it stays off until the account owner asks Zendesk Support to turn it on. Pick JSON, which delivers tickets, users and organizations as NDJSON and is Zendesk's recommendation past 200,000 tickets; CSV is tickets only, without comments or descriptions, and XML caps at 500 MB and disappears above 200,000 tickets. Zendesk's export article adds the edge cases: the emailed link lasts at least 3 days, accounts above 1 million tickets come in 31-day slices, any ticket over 1 MB arrives without comments, and AI agent tickets can't be exported. For full comments and a continuous feed, call the Incremental Export API on the cursor endpoint (/incremental/tickets/cursor), with per_page at most 1,000, the comment_events sideload for complete comments, and exclude_deleted=true if deleted tickets should stay behind. Its ceiling is up to 10 requests per minute, so a large backfill is a scheduled job, not an afternoon. Exit check: staged ticket and comment totals reconcile with Zendesk, with each exception listed.
Tickets, comments, requesters, organizations, groups, custom field values and a status-change event table cover most desks. Make the Zendesk ticket ID a unique column: reloads become idempotent and old ticket links can redirect. Promote the custom fields you report on to typed columns and park the rest in JSONB. Exit check: your ten most-used support reports, rewritten as SQL, return Zendesk's numbers.
Intake and routing, SLA clocks and escalation usually carry most tickets. Port each kept trigger and automation to tested code with identical conditions, and leave retired rules behind for good. A feature flag lets one agent group work the new desk while the rest stay in Zendesk. Exit check: a fixture built from real exported tickets backs each ported rule.
Connect your identity provider to the new desk and turn Zendesk groups into roles. Anything still calling Zendesk during the move should use OAuth, because Zendesk's security and auth reference lists API tokens as deprecated and tells basic-auth and token users to migrate. Size polling to the Support API rate limits (per minute: 200 on Team, 400 on Professional, 700 on Enterprise) and paginate by cursor, because offset paging returns an error past 100 pages or 10,000 records. For push instead of poll, Zendesk webhooks can fire on ticket events from triggers and automations with a signing secret that your receiver should check. Exit check: each integration has an owner, a test and a planned switch date.
Keep the incremental cursor or a webhook copying new Zendesk tickets into your database while a pilot group works only in the owned desk. Each day, compare routing, SLA breaches and resolution time on matched ticket mixes. Exit check: two straight weeks without an unexplained difference.
Move one channel at a time, web forms before email. Take a last incremental pass for late edits and restrict Zendesk to admin read access. Plan the cancellation around Zendesk's service data deletion policy: deletion begins 90 days after cancellation, tickets, attachments and users go within 40 days of that, and backups within 130. Exit check: the last reconciliation is signed before you cancel.
Our AI pod teams hand the tedious work to coding assistants, things like mapping Zendesk custom fields to columns, turning exported tickets into tests and drafting loader scripts. A person reviews each change, and tests run, before anything merges.
Expect a tech lead accountable for schema and switch order, senior full-stack engineers for the agent workspace and ported rules, a data engineer once the export reaches millions of tickets, and QA part of the week for the side-by-side comparison. Many teams begin with a pod of 3 to 5 senior engineers (a tech lead plus engineers), and a full pod is about seven. The hybrid on its own usually needs just a lead and one or two engineers; our data engineers often take the loader and reconciliation.
Ryz engineers on your team start from $7,000 per month (our published range is $7,000–$15,000 per engineer per month, mostly mid-level to senior), quoted per team. Bring your agent count and renewal date when you scope your team with us.
Only past a certain agent count, and your run cost decides where. Take agents times the per-agent list price times 36, then set it against build engineers times months times $7,000, plus Zendesk seats until one month after launch, plus yearly run cost. With Suite Professional at list, our 25-agent case needs more than ten years, 120 agents cross in month 26 and 400 agents in month 21.
For a one-time copy, have the account owner ask Zendesk Support to enable admin exports (Professional or Enterprise) and take JSON. For complete comments and a live feed, use the cursor-based Incremental Export API with the comment_events sideload, which allows up to 10 requests per minute. Tickets above 1 MB lose comments in the admin export, and AI agent tickets aren't exported there.
That comes from four inputs: how many rules survive the audit, how many tickets you backfill at the API's pace, how many integrations need rewiring, and how long side-by-side running takes to come clean. The week-one audit turns those into a schedule, so we don't name a duration before it.
Engineers times months times each engineer's monthly rate, from $7,000, plus your estimate of yearly hosting, upkeep and LLM API spend. Zendesk seats continue until each channel switches, so count those months on the owned side.
Yes. Agents keep working in Zendesk while the Incremental Export API feeds ticket history into your PostgreSQL, and reporting and internal approvals move to owned code. A full replacement can wait until that data shows whether it's worth it.
Questions we didn't answer? Email info@ryzlabs.com.
Thanks — your message has been sent. We’ll get back to you soon.
Something went wrong while sending your message. Please try again or email info@ryzlabs.com.