How to switch from Ticket Tool, TicketsBot, or another Discord ticket bot

What actually transfers

Tessolva has no importer for another bot. It cannot read another bot's tickets, transcripts, statistics, panels, or settings, and there is no upload format for any of it. Your Discord roles, categories, and channels transfer because they already belong to your server, not to the old bot; everything else in this guide is a manual rebuild, and historical tickets and transcripts stay with the old bot unless you export them first.

Inventory the old bot before you touch anything

Spend twenty minutes on this before creating anything new in Tessolva; every gap you miss here becomes a support gap after the switch.

• Every panel and its buttons: ticket type, category, pinged staff role, and any form questions.
• Staff roles: who counts as support, and who has admin access to the old bot's dashboard.
• Welcome, close, and DM messages members currently see.
• Canned replies or snippets and their shortcuts.
• Auto-close timing and any inactivity reminders.
• Business hours, SLA rules, and any webhook or Slack integrations.
• Transcript export settings, so you can pull an archive before removing the old bot.

Create your Tessolva bot

Create a Discord application in the Developer Portal, enable Server Members Intent and Message Content Intent, and paste the token into Dashboard → Add Bot. Invite it with the dashboard's Invite button so it gets the permissions it needs. The old bot can stay in the server while you do this; nothing about the switch requires removing it first.

• Read the full setup guide

Reuse or recreate your structure

Run /setup in Discord. If it finds existing ticket categories or staff roles, choose Use Existing (Recommended) to keep channel permissions and role mentions intact, or Create Anyway (New Names) for a clean separate set. Either way, select the ticket category, closed category, log channel, and transcript channel under Dashboard → Bots → your bot → Servers → the server → Structure, and add your support team's Discord roles under Staff.

Rebuild panels, messages, and quick replies

Build one embed per old panel under Panels & Embeds, with a button per old ticket type or a dropdown for a select-menu panel; attach a form to a button if the old panel collected answers first, though multi-step forms need Basic or higher. Post each panel with the dashboard's Post button or /embed <name> [channel]. Recreate the ticket welcome message as a design under Messages, and add each old snippet under Quick Replies with the same shortcut so staff keep their muscle memory; Basic and Pro allow 25 quick replies, Enterprise is unlimited. Saved panel limits are 1 on Free, 5 on Basic and Pro, and 15 on Enterprise, so count your old panels before you consolidate them.

Rebuild the ticket lifecycle

Set the per-user open-ticket limit under Opening, fixed at 5 on Free and configurable on Basic and higher, decide whether staff claim tickets under Claiming, and recreate the close confirmation and close DM under Closing. Auto-Close & Reminders needs Basic or higher for the inactivity timer. Recreate any rating or feedback prompt the old bot had under Feedback, and any tags staff used to sort tickets under Tags. Set the transcript channel and retention policy under Transcripts; the default is 90 days on Free and 365 days on paid plans, so pick Keep until manually deleted on a paid plan if the old bot kept transcripts forever.

Set up ModMail if the old bot handled DMs

If members used to DM the old bot instead of opening a panel ticket, turn on ModMail under the Channels tab: pick the category for ModMail channels, set staff and ping roles, the greeting and closing DMs, and any minimum account age or server membership requirements the old bot enforced. Staff and user reminders need Basic or higher.

• Read the Discord ModMail bot guide

Test with the old bot still running

Post the new panel in a private channel first. Open a ticket with each button, claim it, send a quick reply, close it, and confirm the transcript lands in the transcript channel and the ticket shows up under Dashboard → Tickets. Run /diagnose to catch permission gaps, such as a missing category permission, before members ever see the new bot.

Cut over and remove the old bot

• Announce the change and the date.
• Post the Tessolva panels in the real support channels and remove or disable the old bot's panels.
• Let open tickets on the old bot finish naturally, or ask staff to close them and reopen anything unresolved in Tessolva.
• Remove the old bot from the server, or at least strip its channel-creation permissions, so members cannot open tickets in two systems.
• Keep the old bot's transcript channel or exported files for as long as you need the history.

Common mistakes during a switch

• Leaving both bots' panels live at once, which shows members two ticket buttons and confuses which bot owns a new ticket.
• Forgetting to reassign per-button staff role restrictions, so a panel that used to ping a specific team ends up pinging nobody.
• Skipping /diagnose after the switch and only discovering a missing permission when the first real ticket fails.
• Deleting the old bot's transcript channel before exporting or archiving the history you still need.

Which plan you need for the switch

Every new Tessolva account starts with a 7-day Enterprise trial, no card required, so rebuild your setup with every feature available and compare what you actually used against the pricing page afterward. Auto-close, quick replies, application forms, and DM on join need Basic; AI and a knowledge base need Pro; webhooks, SLA management, business hours, and approvals need Enterprise. If you settle on a lower plan than the trial, the paid features you configured are switched off rather than deleted, so you can turn them back on later without rebuilding anything.

• See plans and pricing
• Compare a switch from Ticket Tool