osTicket Had Its Moment

osTicket launched in 2003. For over 20 years, it's been the go-to free, open-source ticketing system. Install it on a PHP server, configure your email pipes, and you've got a working help desk for $0.

For IT departments, internal help desks, and budget-constrained teams, osTicket was (and sometimes still is) the right choice. It's stable. It works. It does exactly what it says: manage support tickets.

What osTicket Gives You

• Email-based ticketing
• Ticket forms with custom fields
• Basic agent assignment and SLA
• Dashboard and reporting
• Department-based routing
• Self-hosted (your data, your server)

All free. No per-agent fees. No monthly bill. Just the cost of hosting.

What It Doesn't

No AI. No intent classification, no auto-resolution, no AI-assisted responses. Every ticket is manually read, categorized, and responded to by a human.

No live chat. osTicket is email/form-based. No chat widget for your website. No real-time messaging. Customers submit a form and wait for a reply.

No modern integrations. No native Slack, GitHub, Linear, or Jira integration. Connecting external tools requires custom development or community plugins (which may or may not be maintained).

Dated UI. The admin panel and agent interface look like 2010s PHP software. Functional but not pleasant to use for 8 hours a day. New team members need training to navigate it.

Self-hosting burden. You're responsible for PHP updates, database maintenance, security patches, backups, and uptime. For teams without a sysadmin, this is a real cost — even if the software is free.

The Upgrade Path

If you're on osTicket and considering a move, here are your options:

Want free + open source + modern: Chatwoot. Open-source, self-hosted or cloud, modern UI, multi-channel. It's what osTicket would be if it were built today.

Want simple + cheap + managed: Help Scout or Groove (starting at $16/user/month). No self-hosting. Clean UI. Quick setup.

Want AI automation: Classification at $0.20/message. Auto-resolves 60-70% of tickets. No self-hosting. 15-minute setup.

Want to keep osTicket but add AI: Run classification alongside osTicket. Forward incoming emails to the classification API before they hit osTicket. Auto-respond to routine questions. Only create osTicket tickets for messages that need human attention.

The Migration

Export your osTicket data (the database is MySQL — straightforward to export). Map your custom fields and departments to the new tool's categories. Set up the new tool. Run both in parallel for 2 weeks. Then switch.

The biggest concern teams have: "We've been on osTicket for 5 years. We have thousands of old tickets." Honest answer: you probably reference old tickets less than once a month. Export them to CSV for the rare occasions you need them. Don't let historical data prevent you from upgrading.

When to Stay on osTicket

Stay if: you have a dedicated sysadmin, your volume is low (under 50 tickets/month), your needs are purely email-based ticketing, and you genuinely prefer self-hosting. osTicket works. It's not broken. It's just old.

Move if: you want live chat, AI automation, modern integrations, or you're tired of maintaining a PHP server for your help desk.