Tickets bot shut down: what happened, and where servers went
In March 2025, the most popular dedicated ticket bot on Discord went offline on purpose. Tickets (ticketsbot.net), the bot that introduced panel-based ticketing to hundreds of thousands of servers, announced its sunset on January 5, 2025 and shut down for good on March 5, 2025. If your server ran on it, you lived this story. If you are choosing a ticket bot today, it is worth ten minutes, because it changed how the whole category should be evaluated. Details and links below were last checked in August 2026.
What actually happened
The sunset announcement was unusually honest. The maintainer described the project as, behind the scenes, "a one-man show," and wrote plainly about having fallen out of love with running it. The service claimed roughly half a million server owners at the time. Two months of notice, an export tool for transcript data, and then the bot logged off.
Nobody did anything wrong here. A free tool maintained largely by one person served an enormous community for years, and the person was honest when it was over. But the operational fact remains: half a million servers lost their support system on sixty days' notice, with no way to migrate open tickets and no importer waiting anywhere, because ticket bots keep their data in their own databases.
The single-maintainer lesson
Tickets was not an outlier. Look across the category's recent history: Tikit is gone, tickety's original domain lapsed and now points at a domain-sale page, and several smaller ticket bots from the same generation simply stopped responding one day without a sunset letter. The pattern is structural. Ticket bots are mostly free, mostly maintained by one or two people, and mostly monetized far below the cost of the time they consume.
So when you evaluate a ticket bot, the feature table is only half the question. The other half: what happens to your transcripts, your panel setup, and your members' open tickets if the maintainer is done next year? Questions worth asking of any bot, including ours: is there a business behind it, is your data exportable, and what does the bot's own record say about maintenance?
Where servers went
Three real options came out of the migration wave:
Tickets v2. The community continuation at ticketsbot.cloud carries the original design forward under new maintainers, with a free tier and premium via subscription. If you loved v1 exactly as it was, this is the closest thing to staying.
The established classic bots. Ticket Tool, Ticket King, and Tickety-style bots offer the same open, route, and log model with bigger install bases. Familiar, proven, and your staff still answer every ticket themselves.
The AI-answering model. The newer generation treats the ticket as something to resolve, not just to file. OnyxBot is built on that model: the AI answers the ticket first from your docs and your past resolutions, escalates what it cannot solve to staff with a written briefing, and gets smarter every ticket. The honest comparison with classic ticketing is on OnyxBot vs Tickets, and the wider field is in best Discord ticket bots in 2026.
If you are migrating (from anything)
Whatever direction you pick, the safe path is the same and none of it requires a leap: run the new bot alongside the old one, let existing tickets close where they are, export any transcripts you need, then swap the panel. The step-by-step is in the migration guide. Anything that promises to import another bot's database is overpromising; the data model does not allow it, which is exactly why the sunset stung in the first place.