Choose Zendesk or osTicket for a small support team?
Zendesk fits a small team that wants a managed help desk and can accept Zendesk's cloud and per-plan terms, while osTicket fits a team that needs to keep tickets on its own servers and has someone to run a PHP and MySQL application. If your team takes support by email, phone and web forms and is weighing a Zendesk renewal or a data control requirement, the decision turns on four things: channel needs beyond those three, the support model you can staff, where data must live, and how much in-house time you can give to operating the application.
Start with channels. osTicket's README describes integrating email, phone and web form inquiries into a multi-user web interface, where tickets are saved and assigned to agents. If you also need live chat, WhatsApp, social messaging or a help center, osTicket does not cover those in its core scope, so check whether a plugin or a separate tool closes the gap before you commit. Next, look at support model. osTicket's free download comes with community support only, while its cloud and virtual appliance editions are paid. If your team cannot absorb troubleshooting through public channels, ask osTicket which paid edition fits and what it costs, using the osTicket editions page as the starting point.
Then check data location and operations. Self-hosting means your team owns the server, database, attachments and backups. Confirm the PHP 8.2 to 8.4 and MySQL 5.5 or greater requirements against your platform, and plan for php manage.php deploy and git pull upgrades, backing up attachments, the database and the codebase first. Ask your Zendesk account owner whether exports are enabled before any renewal decision, since exports are not on by default. The question to settle internally is who patches the stack and who answers the pager when mail stops flowing.
Which scenarios favor osTicket and which favor Zendesk
This table maps common small-team situations to the option that fits better and the condition that decides it. Read each row against your own channels, hosting rules and staff capacity, since the right answer depends on those conditions more than on feature lists.
| Scenario | Better fit | Condition that decides it |
|---|---|---|
| One shared support inbox fed by email, phone and web forms | osTicket | Your work is ticket intake and assignment across a few agents, and you do not need a suite of bundled tools around it |
| Support data must stay only on your own servers | osTicket | You can host the PHP application and MySQL database inside your own network or cloud account and keep backups there |
| Team already runs PHP and MySQL in production | osTicket | Existing staff can patch Apache or IIS, PHP 8.2 to 8.4 and the database on the same schedule as current systems |
| Live chat, social channels or messaging are central | Zendesk | Customers reach you through website chat, Facebook, Instagram or WhatsApp and need those conversations in one queue |
| Vendor support contract with a service level | Zendesk | Your procurement requires a named vendor to answer incidents, since osTicket's free download offers community support only |
| No one available to apply upgrades and plugin updates | Zendesk | You cannot assign an owner for backups before upgrades, security patches and plugin compatibility checks |
| Need for LDAP, OAuth2, two-factor or S3 attachments | osTicket | Core plugins from the osTicket-plugins repository cover these, and you will test each one against your osTicket version |
| Need for a fully managed service with no server work | Zendesk | Hosting, uptime and software upkeep should sit with the vendor rather than your team |
Where osTicket's channel coverage stops
osTicket's README describes the product as a system that takes inquiries created by email, phone and web forms, saves them as tickets in one multi-user web interface, and assigns them to agents. That is the scope the project documents. If your Zendesk support runs on those three channels, osTicket covers the core intake path. If it also runs live chat, messaging apps or social channels, you need to confirm each one before you decide, because the README does not list them as built-in channels.
Start by writing down every channel that creates a support conversation in Zendesk today, including website chat, WhatsApp, Facebook or Instagram messages, SMS and any Zendesk Talk phone numbers. For each one, check osTicket's current documentation and the list of plugins in the osTicket-plugins repository. Core plugins in that repository cover authentication, two-factor authentication, password policy, audit and attachment storage, so do not assume a messaging or chat connector exists. If you find one only in a third-party repository, treat it as a separate software risk with its own review, patching and support plan.
Where a channel has no supported connector, your options are a different tool for that channel, an email bridge that turns the channel's messages into mailbox traffic, or keeping that channel on Zendesk during a transition. Each option changes who is paid for what: a bridge or custom connector is implementation and ongoing maintenance work, and a second tool adds licenses, hosting and a second set of agent logins. Ask any implementation partner to price these as written scope items, and confirm with your own support leads which channels generate the most volume before you accept the gap.
Capabilities side by side: Zendesk and osTicket
This table compares the capabilities a small support team usually needs from a help desk, from ticket intake and agent assignment to authentication, storage, export and support. Read the cells as a checklist: where osTicket relies on a plugin or a paid edition, confirm the exact feature set in your own environment before deciding. The main takeaway is that osTicket covers core email, phone and web form ticketing on your own servers, while several items on the Zendesk side depend on your plan and need checking.
| Capability | Zendesk | osTicket (GPL-2.0) |
|---|---|---|
| Ticket intake | Email, web, messaging and phone channels, depending on Suite plan and add-ons. Confirm channel coverage for your plan. | Inquiries created via email, phone and web forms, saved into one multi-user web interface. |
| Ticket assignment to agents | Assignment and routing rules in the Zendesk admin console. Confirm the rule types included in your plan. | Incoming tickets are saved and assigned to agents in the multi-user web interface. Confirm the automation depth you need. |
| Authentication (LDAP, OAuth2, 2FA) | Built-in SSO and two-factor options on higher plans. Confirm which protocols your plan includes. | LDAP, OAuth2, CAS and passthrough authentication, plus two-factor authentication, from the osTicket-plugins repository. Plugins need installing and testing. |
| Attachment storage | Managed by Zendesk in its cloud. Data location depends on your account settings and add-ons. | Stored on the filesystem by default, or on S3 through the attachment storage plugin. Choose storage during design. |
| Data export | JSON, CSV and XML exports on Suite Growth and higher and Support Professional and higher, not on Team plans. The owner must ask Zendesk support to enable them. | Data sits in your own MySQL database and file storage, so you export through your own tooling. Confirm the reporting or export routines you need. |
| Reporting | Built-in reporting dashboards on Suite plans. Confirm the report types included in your plan. | Reporting depends on what your team builds on the database or through plugins. Verify available reports with a test instance. |
| Knowledge base | Zendesk Guide is a separate product tied to the Zendesk account. Confirm its inclusion in your plan. | osTicket includes knowledge base and FAQ features in the core product. Confirm the features in the version you deploy. |
| Upgrade path | Vendor-managed cloud upgrades with no server work on your side. | Upgrades supported from 1.6-rc1 and later. Back up attachments, database and codebase before each upgrade. |
| Support model | Vendor support tiers by plan, with contractual response terms. Confirm the level included in your subscription. | Free download comes with community support only. Paid cloud and virtual appliance editions are listed on the osTicket editions page. Confirm support terms before you choose. |
What osTicket's free download, cloud and appliance editions change
The free open-source download is the GPL2 codebase from the public repository, deployed on your own Apache or IIS server with PHP and MySQL. Your team installs it, configures the mail and phone channels, applies upgrades and keeps backups. The only support included is community support, so fixes and answers depend on public forums and your own staff or contractors. This edition suits teams with in-house PHP and database administration skills, a tolerance for self-directed troubleshooting and a need to keep every ticket, attachment and log inside their own network.
- Operator: Your team runs the server, database and attachment storage.
- Patching: You pull updates with git pull, test them and redeploy, and you own the timing of security fixes.
- Support: Community support only, with no contractual response commitment.
- Cost driver: The software has no license fee, so cost comes from staff time, hosting and any outside help you buy.
- Fit: Suits teams that accept operational ownership in exchange for full control of the software.
Before relying on this edition, confirm in writing with osTicket what, if anything, sits behind the community channel for your use case, and who would answer a security advisory on your version.
The cloud-hosted edition is osTicket's own managed service, listed on its editions page from $12 per agent per month. The vendor hosts the application, so your team no longer administers the web server or database. Your ticket data then sits in a provider environment rather than your own infrastructure, which changes the data residency and audit evidence you must collect. This edition suits small teams that want a hosted helpdesk on a predictable per-agent subscription and do not need to control where the data is stored.
- Operator: osTicket hosts and runs the service.
- Patching: The provider applies platform updates, though the timing and notice terms are yours to confirm.
- Support: Support tier, response times and channels depend on the subscription, so read the terms rather than assuming parity with the free edition.
- Cost driver: The per-agent rate scales with headcount, and the total depends on the plan selected and any add-ons.
- Fit: Suits teams that prefer a subscription and vendor operation over running servers themselves.
Request the current price sheet, service terms, data location, backup and exit provisions, and support levels in writing from osTicket before comparing totals.
The virtual appliance edition is a packaged osTicket image that runs in your own virtualization platform, priced by quote. It keeps the data on your infrastructure while reducing the setup work of building the stack yourself. Ownership of the hypervisor, network, backups and access control stays with your team, and the software itself comes from the vendor under the edition's terms. This edition suits organizations that want a packaged deployment inside their own data center but are willing to pay for vendor-backed support instead of relying on the community.
- Operator: Your team runs the appliance on your own hypervisor, with osTicket supplying the image.
- Patching: Confirm with the vendor how updated images are delivered and whether you apply them or they do.
- Support: Support is part of the commercial quote, so confirm its scope, hours and escalation path.
- Cost driver: Pricing is custom, so the quote depends on the scope, number of agents and support level you request.
- Fit: Suits teams that want data on their own servers with a vendor-supplied package and a support contract.
Ask osTicket to state in writing what the appliance includes, how updates and security fixes are delivered, what support covers, and what happens to your data and licensing if you stop renewing.
How hosting and data control differ between the two
Zendesk keeps support data in its own cloud, while osTicket runs on servers you choose and operate. Each card below names a control point where that difference changes your work, from where records and files sit to who proves the controls during an assessment.
Data location and hosting model
Zendesk is a hosted service, so ticket content, attachments and user records sit in Zendesk's infrastructure under its terms. osTicket is a PHP application you deploy into your own cloud account, data center or private network, so you choose the region and the hosts. Confirm with your data protection team which regions and sub-processors are acceptable, and whether the location of backups and logs must follow the same rule.
Attachment storage location
osTicket's attachment storage plugin can keep files on the local filesystem or send them to S3-compatible object storage. Local storage keeps files on the same host as the application, while S3 storage moves them to a bucket you control and can place in a region of your choice. Check whether customer attachments, which often carry personal data, need encryption at rest and a separate retention rule from ticket records.
Identity integration through LDAP and OAuth2
Zendesk authenticates agents through its own accounts and its supported SSO options. With osTicket, the LDAP and OAuth2 plugins from the core plugin set let staff sign in with your directory, so joiner and leaver changes flow from one place. Confirm how each plugin maps directory groups to agent roles, how disabled accounts are handled, and whether the session lifetime matches your access policy.
Backup responsibility
On Zendesk, the vendor operates the platform, but you still need your own export copy to restore or move data, and exports on Team plans are not available. On osTicket, you own the full backup chain. The README recommends backing up attachment files, the database and the codebase before any upgrade. Assign an owner, set a restore test schedule, and record the recovery point and time you can meet.
Compliance evidence you produce
With a hosted helpdesk, part of the control evidence comes from the vendor's own reports. With osTicket, the configuration, access reviews, patch records, backup logs and encryption settings are your evidence. DeployOpen prepares controls and evidence for assessments but does not issue audit reports, attestations or certifications, and independent auditors make that determination. Confirm each control against your assessment scope before you rely on it.
Operational ownership of patches
Zendesk applies platform updates on its schedule. With osTicket you run the upgrade path yourself, including the PHP 8.2 to 8.4 runtime, the MySQL version and the plugin versions, which must be tested together. The stack requirements in the README set the baseline, so write down who watches security releases and how long a patch may wait before it is applied to production.
What each option costs to run and what drives it up
Start by separating the two cost models. Zendesk bills a subscription per agent, and the plan tier decides what you can take out of the account: data exports are available on Suite Growth and higher and Support Professional and higher, not on Team plans, and the account owner must ask Zendesk support to switch them on. The osTicket download has no license fee under GPL2, but the cost moves to the servers you run: a web server with Apache or IIS, PHP 8.2 to 8.4, MySQL 5.5 or greater, storage for attachments, and admin time to patch all of them. Those components recur every month whether or not anyone opens a ticket. If you want vendor support instead of community support, the osTicket editions page lists a cloud edition starting at $12 per agent per month and a virtual appliance priced by quote, so confirm which edition your comparison depends on.
One-time costs cluster around setup and migration. Deploying from the public repository with php manage.php deploy is quick in a lab, but a production install needs a staging copy, TLS, mail routing for the email channel, and configuration of the core plugins from the osTicket-plugins repository: LDAP, OAuth2, two-factor authentication and S3 attachment storage. Plugin needs and attachment volume are the two largest drivers. Heavy attachment use grows the database and disk, and moving files to S3 shifts that cost to an object store you must pay for and secure. Agent count drives Zendesk and cloud edition fees directly and drives admin time more loosely. Upgrades add a recurring obligation: the README recommends backing up attachment files, the database and the codebase before each upgrade, so a tested backup and rollback plan costs staff time every cycle.
When you request a written quote, ask each vendor or partner to state the per-agent rate at the plan tier you need and whether data exports are enabled and included. For osTicket, ask whether agents are counted the same way in the cloud edition, what the virtual appliance price covers, and whether upgrades and plugin configuration are included. For any outside implementation work, ask for fixed deliverables, the hosting assumptions behind the estimate, how backups and restore tests are handled, who performs each upgrade, and what support response terms apply after go-live. Confirm these terms with the vendor and with your own environment before you compare totals, because the same workload can produce very different recurring costs depending on the answers.
What moving from Zendesk to osTicket involves
The sequence confirms what osTicket must cover, moves tickets and users out of Zendesk with a verified copy, and ends with a tested osTicket instance that agents use alongside a short parallel run before Zendesk is switched off.
Confirm channels, plugins and import tooling
The support lead lists every channel in use today, including email addresses, phone intake and web forms, and marks which ones must keep working after cutover. The IT lead maps each need to an osTicket feature or plugin from the core plugin set, such as LDAP or OAuth2 for agent sign-in, two-factor authentication, and filesystem or S3 attachment storage. Because no migrator is supplied for this pairing, ask osTicket directly whether it offers or endorses an import tool, and confirm what Zendesk integrations, macros, triggers and views have no equivalent. The output is a written channel and plugin list signed off by the support lead.
Export tickets and users from Zendesk
The Zendesk account owner confirms the plan includes data exports, since they are not available on Team plans, and asks Zendesk support to enable them because they are off by default. Export tickets and users in JSON, which carries comments and descriptions, and treat the CSV export as incomplete because it omits both. For large accounts, check the XML size and ticket-count limits before choosing a format. Store the exports in encrypted, access-controlled storage. The output is a complete, checksummed export set that someone other than the exporter has opened and spot-checked against live tickets.
Map agents, groups and custom fields
Build a mapping sheet that pairs Zendesk agents, groups, organizations and custom ticket fields with osTicket staff accounts, teams, departments, help topics and custom forms. Decide who keeps administrator rights and which groups receive assignment rules. Record where a Zendesk field has no direct osTicket form equivalent and agree how that data will be kept, such as a custom form or an archived attachment. Users must be mapped with their email addresses, since passwords do not transfer. The output is an approved mapping document that the support lead and the osTicket administrator both sign.
Deploy osTicket on your own infrastructure
The platform team installs osTicket from the public repository in your cloud account, data center or air-gapped network, using the deploy command in the README. Confirm the stack the README specifies: Apache or Microsoft IIS, PHP 8.2 to 8.4 with 8.4 recommended, the mysqli extension and MySQL 5.5 or greater. Set up TLS, backups of the database, attachments and codebase, and inbound mail routing for each support address. The output is a reachable staging instance with its service accounts, backups and mail ingestion tested.
Configure authentication, plugins and attachment storage
The administrator enables the chosen plugins from the osTicket-plugins set, such as LDAP or OAuth2 for sign-in, two-factor authentication, password policy, audit and S3 or filesystem attachment storage. Each plugin's settings are checked against the documentation and against a test account, and any plugin not in the core set is reviewed for maintenance and security before it is installed. The output is a configuration record listing each enabled plugin, its version, and the test results for sign-in and attachment upload.
Run test imports and reconcile results
Load the exported tickets, users and mappings into the staging instance, starting with a small sample and then a full run. Compare ticket counts, requester emails, timestamps, attachments and comment threads against the Zendesk export, and log every record that fails or changes. Because the import method must be confirmed in the first step, record exactly how each run was performed so it can be repeated. The output is a reconciliation report with zero unexplained differences, or each difference accepted in writing.
Cut over email, forms and phone routing
Change the MX records, mail forwarding rules, web form targets and phone routing so new inbound messages reach osTicket. Update the external links that customers and partners use, and retire Zendesk triggers that would duplicate tickets. Agree the cutover window with the support lead and keep the rollback steps written down. The output is a confirmed routing change, with test messages from each channel arriving as tickets in osTicket.
Run in parallel and close out Zendesk
For an agreed period, agents work in osTicket while Zendesk stays available for reference, and the team tracks missed messages, misassigned tickets and any channel gaps. Once the support lead accepts the results, keep a final Zendesk export and a dated record of the decommission decision, then cancel the subscription on the account owner's instruction. The output is a closure record listing open issues, the retained archive location, and the date Zendesk access ended.
Questions buyers ask before moving from Zendesk to osTicket
What does moving from Zendesk to osTicket cost in total?
The software itself has no license fee under the GPL-2.0 free download, so the total is driven by hosting, setup, data migration, plugin work and internal admin time. Hosting is a recurring cost you pay a cloud or data center provider for servers, PHP, MySQL or MariaDB, storage and backups. Setup, migration and plugin configuration are usually one-time costs paid to your own staff or an implementation partner. Zendesk subscription fees stop at cutover, but you should keep a read-only export for records. Ask any partner for a fixed-scope written quote that lists each component separately.
How long does a move from Zendesk to osTicket take?
The timing depends on how many channels you cut over, how much history you must keep, how many plugins you need, and how many agents must be trained. Email routing, phone logging and web form intake each need testing against real messages before you switch. Historical tickets are usually the slowest part because Zendesk exports cover tickets, users and organizations, and the CSV export omits comments and descriptions, so you need a plan for those fields. Confirm a schedule with your team or a partner once the scope is written, rather than relying on a generic duration.
Can our own team migrate from Zendesk to osTicket without a partner?
A team with Linux, web server and PHP experience can deploy osTicket from the public repository using the php manage.php deploy command described in the README, then configure mail, departments, help topics and agents. The harder work is mapping your Zendesk data, reviewing attachments and checking that routing rules match what your agents expect. If nobody on staff has run a PHP application in production, or you have to meet audit evidence requirements, a partner may be the better route. Decide based on your skills inventory, not on the software alone.
What skills and staff time does an osTicket deployment need?
You need someone who can administer a Linux server, manage the Apache or IIS web tier, run PHP 8.2 to 8.4 with the mysqli extension, operate MySQL 5.5 or greater, and configure outbound and inbound mail. A help desk administrator must also set up departments, staff roles, SLAs and email routing. Plan for ongoing time in patching, backups and plugin updates. Ask any partner which of these tasks they will deliver and which will stay with your team, and get that split in writing.
How do osTicket upgrades work, and what does the README say to do first?
The osTicket README states that upgrades are supported from 1.6-rc1 and later, and it recommends backing up attachment files, the database and the codebase before you upgrade. For a git-based install, you pull later updates with git pull and then redeploy. Test upgrades in a staging copy first, because plugins from the osTicket-plugins repository may need their own updates. Community support covers the free download, so budget for internal testing or a retainer if you need someone on call for upgrade issues.
What happens to support after cutover on the free osTicket download?
The free osTicket download comes with community support only, so there is no vendor-backed response commitment for the core product. Your team owns incident response, patching, backup testing and troubleshooting, or you contract a partner for that work. The osTicket editions page also lists a cloud-hosted edition and a virtual appliance edition, which have different commercial terms and are quoted separately. Confirm the support model you need before you retire the Zendesk subscription.
When should we bring in an implementation partner for osTicket?
Bring in a partner when the migration touches regulated data, requires LDAP or OAuth2 integration, needs two-factor authentication or S3 attachment storage configured to a tested standard, or when your team lacks the time to run cutover. DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades and documents self-hosted open-source platforms inside your own infrastructure, and most engagements are fixed-scope with agreed deliverables and timelines in writing before work starts. DeployOpen does not publish a price list, so a quote follows from that written scope.
How DeployOpen helps evaluate, implement and move your help desk
DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For a Zendesk vs osTicket decision, we start by confirming which channels and workflows your team actually depends on, then put the written scope in front of you before any work begins.
How we scope
- Map your email, phone and web form intake to what osTicket covers and what needs a separate tool
- Confirm which agent assignment rules, queues and SLA expectations must carry over
- Agree required plugins for LDAP, OAuth2, two-factor authentication and S3 attachment storage in writing
- Engagements are fixed-scope, with deliverables and timelines agreed before work starts
How we build
- Deploy osTicket from the public repository in your environment, using the documented deploy and update steps
- Configure PHP, MySQL and web server hosting to the versions the project documents for your build
- Integrate identity, mail routing and attachment storage with your existing systems and access controls
- Test ticket intake, assignment and notification paths against the scenarios your support team uses
How we hand over
- Document the architecture, configuration, plugin choices and backup procedure for your own administrators
- Provide runbooks for upgrades, including backing up attachments, the database and the codebase first
- Walk your support leads through agent, queue and assignment administration in your own environment
- Record which channels stay outside osTicket so ownership of those gaps is clear from day one
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover
- Because osTicket's free download carries community support only, we can cover the operational gap under contract
- Ask us to confirm the support path, response expectations and upgrade cadence in the written scope
- Quotes follow from the written scope, and we do not publish a price list
