Migration Guide
A concrete, honest checklist for moving from another ticket bot to TicketCord, including what cannot be imported
This guide is for servers that already run a ticket bot and want to move to TicketCord without losing their workflow. It tells you up front what transfers (nothing automatically), how to rebuild each part of your old setup using the real dashboard settings pages, and how to run both bots side by side while you switch.
TicketCord has no importer for other bots. It cannot read another bot's tickets, transcripts, statistics, panels, or settings, and there is no file format you can upload. Everything below is a manual rebuild. Plan for an hour for a typical server, longer if you have many panels or canned responses.
What transfers and what does not
| You can keep | You have to rebuild | You cannot bring over |
|---|---|---|
| Your Discord roles (staff, admin), categories, and channels: TicketCord can use the ones you already have | Ticket panels (embeds and buttons), welcome and close messages, canned responses, tags, auto-close timers, business hours, response targets, webhooks | Historical tickets and transcripts from the old bot, its statistics, its user or staff metrics, and any integrations built against its API |
Old tickets stay wherever the old bot stored them. Export them from the old bot before you remove it, or keep the old bot's transcript channel in Discord.
Before you start
- You need to be the TicketCord account owner to set up the server in the dashboard, configure staff roles, and grant dashboard access. Running
/setupin Discord needs Administrator, or Manage Channels plus Manage Roles. - Open the old bot's settings and write down: which roles are staff, which categories tickets go to, every panel and its buttons, every welcome or close message, every snippet or canned reply, auto-close timing, and any Slack, webhook, or logging integrations.
- Decide whether you will reuse the old categories and roles or let TicketCord create fresh ones. Reusing keeps channel permissions and role mentions intact; fresh ones avoid mixing old and new tickets.
- Every new TicketCord account has a 14-day Enterprise trial, so you can rebuild with every feature available and choose a plan once you know what you use. See Free Trial.
The migration checklist
Create and invite your TicketCord bot
Follow Installation: create a Discord application, paste the bot token into the dashboard (the guided setup on your first sign-in, or Add a bot under Your bots), and invite the bot from the dashboard so it gets every permission it needs. The old bot can stay in the server for now.
Run /setup, or point TicketCord at existing resources
To reuse your old categories and staff roles, pick them in the setup form in the next step.
For fresh ones, click Create them for me in that form: it creates whatever you have not picked (🎫 Tickets, 📁 Closed Tickets, and 📝 Ticket Logs with #ticket-transcripts and #ticket-logs, plus the Ticket Admin and Ticket Support roles) and picks them.
In Discord, /setup does the same; if it finds existing ticket categories or roles it offers Create Anyway (New Names) (a separate 🎫 TicketCord Tickets, 📁 TicketCord Closed, and 📝 TicketCord Logs set), Use Existing (Recommended), or Cancel.
Rebuild the structure and staff
Go to your server (click the server's tile on the dashboard home). A server that was never set up shows its setup form first: pick the staff roles, categories, transcript channel, and logs channel there and click Finish setup. Afterwards the same choices live on the settings pages in the sidebar:
- Opening tickets → Ticket categories: the ticket category. Use the old bot's categories if you kept them. Move closed tickets to is under Closing tickets → Closing rules. The logs channel and the transcript channel are under General → Where the bot posts (Staff logs and Transcripts).
- Staff → Staff roles: add the Discord roles your support team already has. TicketCord checks roles live, so nobody needs a new role. Under Dashboard access grant dashboard access to the staff who managed the old bot's web panel.
- Opening tickets → Who can open tickets: recreate any block or allow lists (members and roles) the old bot enforced for who may open tickets.
Recreate panels and messages
- Panels → Ticket panels: build one panel per old panel (New panel). Add a button per old ticket type, or a dropdown if the old panel used a select menu. If the old bot collected answers in a form before opening the ticket, attach a form to the button; multi-step application forms need Basic or higher. Post each panel to its channel from the dashboard or with
/embed <name> [channel]. - Messages: recreate the message users see when a ticket opens. Welcome messages are reusable designs: set one as the default for each ticket type, and pick a different design on any button, dropdown option, form, or application that needs its own text. See Welcome Messages.
- Staff → Quick replies: add each of the old bot's snippets or canned replies with the same shortcut so staff keep their muscle memory. Staff send them with
/reply <shortcut>. Basic and Pro allow 25, Enterprise unlimited.
Plan limits for saved panels: Free 2, Basic and Pro 5, Enterprise 15. If you are consolidating several old panels, count them first.
Recreate the ticket lifecycle
- Opening tickets → Ticket options: a role while a ticket is open, thread tickets and their archiving, and the per-user open-ticket limit under Ticket limits (1 to 5 on Free, any limit on Basic and higher).
- Staff → Claiming: whether a claim removes the rest of the team (Exclusive claims) and which supervisor roles keep access.
- Opening tickets → New ticket defaults: how new ticket channels are named and who is pinged when a ticket opens, if the old bot named or pinged a certain way.
- Closing tickets → Closing rules: the close confirmation, whether the member gets a DM when their ticket closes (Message the member), and whether the channel is moved (Move closed tickets to) or deleted (After closing). The text of the close notice and the close DM is a design you pick on Messages: switch Automatic messages to Ticket closes (Basic and higher).
- Closing tickets → Auto-close and reminders: the inactivity timer (
/auto-close 2H,1D, and so on; minimum 15 minutes, maximum 30 days) (Basic and higher) and the reminders sent before closing (Basic and higher). - Closing tickets → Ratings: rating prompt after close, if the old bot had one; turn on RestoreCord reviews in the same card if you use RestoreCord.
- Staff → Tags: recreate any categories or labels staff used to sort tickets; staff apply them with
/tag. - Closing tickets → Transcripts: whether a transcript is posted on every close. How long closed tickets are kept is Keep closed tickets for under General → Privacy and data. If the old bot kept transcripts forever, note that TicketCord's default is 90 days on Free and 365 days on paid plans; choose Until you delete them on a paid plan if you need indefinite retention.
Set up ModMail if you are replacing a DM-based bot
Go to Opening tickets → How members open tickets, set Members open tickets with to A DM to the bot (ModMail), and save. Then:
- pick the category for ModMail ticket channels under Opening tickets → Ticket categories (Create tickets in);
- set channel names and who is pinged under Opening tickets → New ticket defaults;
- set minimum account age or time in the server, and any blocked members, under Opening tickets → Who can open tickets if the old bot had anti-spam rules;
- choose whether members can close their own ticket under Closing tickets → Closing rules (Only staff can close);
- on ModMail → ModMail, set anonymous replies (a team name such as "Support Team", or one you choose, instead of staff names) and the reopen cooldown; the greeting and closing DMs are on Messages.
ModMail reminders for whoever needs to reply next need Basic or higher. DM to new members on Messages (Basic and higher) replaces bots that greeted new members by DM.
Recreate AI, service levels, and integrations
- AI assistant → Atlas (Pro and higher): add the documentation URLs or FAQ text the old bot answered from under AI assistant → Atlas → Sources, then turn on the features you want. Nothing here has an equivalent in most ticket bots, so this is optional.
- General → Business hours, Staff → Response targets (SLA), Staff → Approvals, General → Scheduled reports (Enterprise): recreate response-time rules and reporting if the old bot had them.
- General → Webhooks: outgoing webhooks (Enterprise, 20 per server) replace Slack or custom webhook integrations. Webhook payloads differ from the old bot's, so anything that consumed them needs updating. See Webhooks. Status page integrations (Pro and higher) are on AI assistant → Atlas → Sources.
- General → Bot language: set the bot language for this server (19 available).
Test with the old bot still present
Post the new panel in a private channel first. Open a ticket with each button, claim it, add a user, send a quick reply, close it, and confirm the transcript lands in the transcript channel and the ticket appears in Tickets. Run /diagnose to catch permission gaps. If the old bot also responds to ticket buttons in the same channel, keep the new panel in a separate channel until the switch.
Switch over
- Announce the change and the date.
- Post the TicketCord panels in the real support channels and delete 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 TicketCord.
- Remove the old bot from the server, or at least strip its ability to create channels, so members cannot open tickets in two systems. If both bots register similar slash commands, removing the old bot is the only reliable way to avoid confusion.
- Keep the old bot's transcript channel or exported files for as long as you need the history.
Where each old setting goes
| Old bot setting | TicketCord page → block | Notes |
|---|---|---|
| Support team / staff roles | Staff → Staff roles | Reuse existing Discord roles |
| Ticket category | Opening tickets → Ticket categories | Reuse existing categories or use the ones from /setup |
| Closed category | Closing tickets → Closing rules | Move closed tickets to; hidden while After closing is Delete the channel |
| Log channel | General → Where the bot posts | Staff logs; the other channels default to it |
| Blacklist / allowlist | Opening tickets → Who can open tickets | Members and roles |
| Panels, reaction or button menus | Panels → Ticket panels | One panel per old panel; buttons, dropdowns, modals, application forms |
| Ticket welcome message | Messages | Designs reusable across buttons |
| Snippets / canned replies / macros | Staff → Quick replies | Same shortcuts, /reply |
| Per-user open-ticket limit, thread archiving | Opening tickets → Ticket options | Free allows 1 to 5 open tickets per user; any limit from Basic |
| Claim settings | Staff → Claiming | |
| Close confirmation, close DM | Closing tickets → Closing rules | Message the member sends the close DM. The close notice and close DM text are designs picked on Messages (Basic and higher) |
| Inactivity auto-close and reminders | Closing tickets → Auto-close and reminders | Basic and higher |
| Rating / feedback prompt | Closing tickets → Ratings | |
| Ticket categories or labels | Staff → Tags | |
| Transcript channel, retention | General → Where the bot posts, General → Privacy and data | Transcripts and Keep closed tickets for |
| DM-based tickets, anti-spam rules | Opening tickets → How members open tickets, Opening tickets → Who can open tickets | ModMail's own options are on ModMail → ModMail |
| Slack / webhook integrations | General → Webhooks | Enterprise |
| Bot language | General → Bot language | 19 languages |
Migrating from a specific bot
The mapping is the same for every source bot; the differences are in what you have to look up in the old bot.
From a panel-based ticket bot (Ticket Tool, Tickets, Discord Tickets, and similar)
Take a screenshot of every panel and note each button's ticket type, the category it opens in, the support roles it pings, and any form questions.
Rebuild them under Panels → Ticket panels, and their welcome messages under Messages. Reuse the old support roles under Staff → Staff roles. Recreate auto-close under Closing tickets → Auto-close and reminders and transcripts under Closing tickets → Transcripts.
Old transcripts stay with the old bot; download them before removing it if it offers an export.
From a ModMail bot
Turn ModMail on under Opening tickets → How members open tickets. Its category is under Ticket categories, account-age and membership requirements under Who can open tickets, and anonymous replies and a reopen cooldown on the ModMail page. Recreate snippets under Staff → Quick replies. Old ModMail threads and logs are not imported; keep the old log channel or export it. Once enabled, tell members to DM the new bot instead of the old one and remove the old bot so DMs are not handled twice.
From a bot with a web dashboard or API
Any web configuration must be rebuilt by hand on the settings pages above. Anything that consumed the old bot's API or webhooks needs to be rewritten against TicketCord's outgoing webhooks (Enterprise). There is no compatibility layer.
Running two bots at once
- Use separate channels for the old and new panels and label them clearly.
- Keep the old bot's ability to create tickets only as long as you need it to finish open tickets.
- Staff can use both systems in parallel because TicketCord only manages the channels it created.
- Remove the old bot once its last ticket is closed; two bots registering similar slash commands is the most common source of confusion during a switch.
Troubleshooting a migration
| Symptom | Cause | Fix |
|---|---|---|
| Members see two ticket buttons | Both panels are live | Remove the old panel or its bot |
| Old bot's commands still appear | Its application commands stay registered while it is in the server | Remove the old bot from the server |
| TicketCord cannot create tickets in the old category | Bot lacks Manage Channels or Manage Roles there, or the category has 50 channels (TC002 or TC019) | Grant the permissions in the category, or move old channels out. Run /diagnose |
| Staff cannot see new tickets | Their role is not listed under Staff → Staff roles | Add the role, or give staff the roles from /setup |
| Transcripts missing | No transcripts or logs channel selected, or the Transcripts switch is off | Choose a channel under General → Where the bot posts and turn on Closing tickets → Transcripts |
| A feature from the old bot seems missing | It may have a different name | Check the FAQ and the feature pages; if it is genuinely missing, suggest it in the support Discord |
Common questions
Can TicketCord import my old tickets or transcripts?
No. There is no importer and no upload format. Export from the old bot before removing it and keep the files or its transcript channel.
Do I have to make new staff roles?
No. Pick the roles you already use in the setup form on your server, or later under Staff → Staff roles. If you prefer fresh ones, Create them for me in the setup form (or /setup in Discord) creates Ticket Admin and Ticket Support roles.
Can I keep my old categories and channels?
Yes. Pick them in the setup form, or later under Opening tickets → Ticket categories. (If you run /setup, choose Use Existing (Recommended) when it detects them.) Make sure the bot has Manage Channels and Manage Roles in those categories.
Can I test TicketCord without removing the old bot?
Yes. Post the new panel in a private channel, run through a full ticket, and only switch the public channels when you are happy. Remove the old bot at the end to avoid duplicate buttons and commands.
Which plan do I need for the migration?
Every new account has a 14-day Enterprise trial, so rebuild with everything available and then compare what you used against Plans & Pricing. Auto-close, quick replies, application forms, and DM on join need Basic; AI needs Pro; webhooks, response targets, business hours, and approvals need Enterprise.
Ask for help with your switch
Contact us for migration questions
Was this page helpful?
Last updated on