Skip to main content
Switching to TicketCord from another ticket bot? This guide helps make the transition smooth.

​
Before You Start

​
What to Prepare

  • Admin access to your Discord server
  • Access to your current ticket bot’s settings
  • List of your ticket categories/teams
  • Any custom settings you want to preserve

​
What Transfers

​
Migration Steps

1

Document Current Setup

Note your current configuration: categories, roles, messages, automation
2

Create TicketCord Bot

Sign up and create your bot at ticketcord.net
3

Configure Settings

Recreate your setup in TicketCord dashboard
4

Run /setup

Complete the setup wizard in Discord
5

Test Thoroughly

Create test tickets to verify everything works
6

Switch Over

Remove old bot, announce the change

​
Migrating from Ticket Tool

​
Equivalent Features

​
Configuration Mapping

Panels → Embeds:
  1. Go to Dashboard → Configuration → Embeds
  2. Create new embed with similar design
  3. Add buttons for ticket creation
  4. Deploy to your support channel
Teams → Staff Roles:
  1. Go to Configuration → Staff
  2. Add your existing Discord roles
  3. Set permissions for each role
Auto-close → Automation:
  1. Go to Configuration → Automation
  2. Enable auto-close
  3. Set timing and conditions

​
Migrating from ModMail

​
Key Differences

​
Equivalent Features

​
Migration Steps

  1. Enable DM Mode (if desired):
    • Configure bot to accept DM tickets
    • Set up welcome message for DM tickets
  2. Recreate Categories:
    • Create matching categories in TicketCord
    • Assign to appropriate Discord categories
  3. Import Snippets:
    • Create canned responses for your snippets
    • Use same shortcuts for consistency

​
Migrating from Discord Tickets

​
Feature Comparison

​
Additional TicketCord Features

When migrating, you gain:
  • AI-powered knowledge base
  • Automatic routing
  • Priority detection
  • Webhook integrations
  • Detailed analytics
  • Dashboard management

​
Migrating from Other Bots

​
General Migration Approach

  1. Export what you can: Take screenshots of settings
  2. List features used: Document what you actually use
  3. Find equivalents: Map to TicketCord features
  4. Configure gradually: Don’t rush the setup
  5. Test before switching: Ensure parity

​
Common Settings to Recreate

​
Handling Historical Data

​
Your Old Tickets

TicketCord cannot import tickets from other bots because:
  • Different data formats
  • No standardized export
  • Privacy considerations

​
Recommendations

Keep Old Bot Running (Temporarily) Run both bots briefly so you can reference old tickets if needed.
Export Transcripts If your old bot supports it, export transcripts before removing.
Screenshot Important Info Capture any critical ticket information manually.

​
Parallel Running

​
Safe Transition

Run both bots simultaneously during transition:
  1. Set up TicketCord in test channels
  2. Train staff on new system
  3. Gradually direct users to new system
  4. Monitor for issues
  5. Remove old bot when confident

​
Avoiding Conflicts

  • Use different channels for each bot
  • Clearly label which is which
  • Set old bot to read-only if possible

​
Staff Training

​
What’s Different

Educate your team on:

​
Training Resources

  • Share this documentation
  • Create channel for questions
  • Run practice sessions
  • Document server-specific workflows

​
Announcing the Change

​
Communication Plan

  1. Before switch: Announce upcoming change
  2. Transition day: Clear instructions
  3. After switch: Address questions

​
Example Announcement

​
Troubleshooting Migration

Remove or disable the old bot’s slash commands, or remove the old bot entirely.
Clearly differentiate channels and announce the transition prominently.
Check our documentation - the feature might exist under a different name. If not, suggest it in our Discord!
Provide training, share documentation, and allow time to adjust.

​
Need Help Migrating?

Discord Support

Get help from our community

Email Support

Contact us for migration assistance