Zammad support platform cost calculator

Estimate operated Zammad costs from agents, ticket history, search, attachments, channels and migration, including Zendesk features you retain.

Last updated

In short

  • Agent licences are only one part of a support platform bill.
  • Separate ticketing from telephony, AI, messaging and reporting that may remain elsewhere.
  • Attachment history and search indexing can matter more than the number of agents.
On this page (4)

Costs and savings · Part of Zammad

Interactive worksheet · no sign-up

Estimate Zammad support desk costs

Use the same currency and scope for both options. Inputs stay in this page; they are not included in analytics or sent with an enquiry.

1. Your current bill
2. The replacement

Business management: CHF 1,590/month for up to 3 apps; onboarding from CHF 9,900. Infrastructure and paid licences are extra.

Additional billable backup storage

Include copies and retention. Enter only costs outside the infrastructure quote and Pilae plan.

Email, SMS or delivery units

Use the delivery vendor’s unit. Keep phone, AI and messaging charges outside the base licence visible.

Ticket history, voice, AI assistance and reporting are separate acceptance requirements. Do not assume a base help-desk price replaces every suite feature.

3. Transition and overlap
Optional: value internal operating time

Time released is capacity, not automatically payroll or cash saved. Keep time already billed by Pilae or another supplier out of these fields.

How the calculation works
  1. Current monthly invoices = billed units × unit price + additional current spend.
  2. Replacement monthly invoices = Pilae management + additional infrastructure + target licences + workload usage + retained services.
  3. Transition = plan onboarding + new hardware + extra migration + training + parallel months × max(0, current invoices − retained services). Parallel months are capped at the comparison horizon.
  4. Total invoices = monthly invoices × horizon, plus transition for the replacement. Payback uses the full transition commitment divided by positive monthly invoice saving, including all entered overlap months even beyond the selected horizon.
  5. Economic saving adds the change in valued internal operating time. It does not assume headcount reduction.

Business includes up to 3 apps, then a published per-app fee (CHF 390 in CHF). Starter’s published CHF price is CHF 449/month. All Pilae figures come from the same price data as the pricing page. Workload inputs are your estimates, not supplier quotes. Taxes, price growth, discount rates, opportunity costs and differences in functionality are outside this arithmetic.

A support platform budget starts with the work arriving in the inbox: how many conversations, which channels, how much history and how agents search it. Zammad’s software licence and a managed operating service are separate items. The calculator on this page helps compare recurring costs and transition; the workload review determines whether the chosen capacity and features are appropriate.

Compare a support workflow, not two product names

Zendesk’s pricing page groups capabilities into different plans and add-ons. A plain email-ticketing workload should not be compared against a high-end suite merely to produce a larger percentage. Conversely, a team using voice routing, AI resolution and specialized analytics cannot assume that those costs disappear when tickets move.

Input What to count Why it matters
Active agents People who work tickets, plus required access roles Current licence baseline and concurrency
Ticket flow Monthly volume and arrival peaks Application and background-job load
Retained history Tickets, articles, attachments and time span Database, file and search capacity
Channels Email, chat, messaging, voice and integrations External services and feature scope
Search Index size and complex reporting needs Memory, storage and maintenance
Response coverage Operating hours and recovery expectations Service level and support cost

The Zammad hardware guidance describes workload-dependent requirements. Its sizing recommendations are a starting point, not a guarantee for a particular number of agents or imported attachments.

Separate software rights from running the service

Zammad’s licence guidance states that using the application does not require a software licence fee. Operation still needs infrastructure, security maintenance, backups and people to respond when mail ingestion or search fails. Optional vendor support, integrations and external channel services belong in the estimate if required.

Include the search system and database in the bill of materials. A low-cost application VM is not the whole stack when historical tickets and attachments need indexing. Recovery must restore the records and files coherently; rebuilding a search index can add time even when the primary data is safe.

An example that exposes the break-even point

Suppose a team’s actual support subscription is 1,200 units per month. A proposed service costs 850, while retained voice and messaging add 200. The recurring difference is 150. With 6,000 of migration and training, simple payback is 40 months. If the current contract still has a year to run, include the overlap rather than claiming immediate savings.

These are illustrative inputs. If a higher Zendesk tier is genuinely being discontinued, use that invoice; if its features remain necessary, keep their replacement cost. Never use a suite price while modelling only basic ticketing.

Price migration from a representative sample

Choose tickets containing attachments, internal notes, merged conversations, custom fields and different user roles. Record which objects import, which need mapping and which history can only be archived. Check original timestamps and access permissions as well as record counts.

Test incoming and outgoing mail, replies, routing, notifications and an unavailable channel. A technically complete import is not ready for cutover if agents cannot find the information needed to resolve a case. Keep a written rollback and write-reconciliation plan during the parallel period.

Use Pilae pricing for the operating model and a separate migration scope. The Zendesk migration guide and alternative assessment help establish functional fit. Bring actual agent billing, channel spend and a history sample; those inputs make the cost comparison useful.

Sources and further reading

Use the linked documentation to confirm the version, edition and contract that apply to your project.

Scope our support platform

Bring your current bill, required capabilities and workload assumptions. We will separate recurring operation from migration and retained services.