Migration notes for V2
Many things have changed and some things are now stored in the database which wasn't done before. In order to carry certain configurations and other things, please read this article carefully.
What is not migrated until the mid of February of 2025, will be lost and has to be set up from point zero again! (The exact date will be updated here at the end of December 2024)
Forum tags
Forum tag IDs are now stored in the database, which wasn't done before. It's easier to do this because of possible performance and caching issues.
Run the command /debug and select the option Check channel setup.
The bot will then check and fix the tags as well.
Migrated data
The database system has changed and old data was migrated. Below you can see the details of the migration.
Guild configs
Yes
Tickets
Yes*
Only where all necessary data was given
Reports
Yes*
Only where all necessary data was given
Blacklists
Yes
Close Requests
No
They were not deleted every time, so there were still some close requests from months ago in the DB
No
Something was wrong here too, and there were still about 7000 references stored - not all of them from open tickets.
Language preferences
Yes
Data conflict
There may be some tickets that already appeared to be closed but now appear to be ‘open’ again for users. I can't explain it any other way than that something was wrong with the old code. This should no longer happen, but it is possible that users are replying to tickets that are already closed. If you have too many problems like this, please create a ticket on the support server so that all your tickets can be reset (deleted). This will fix the problem absolutely.
Last updated
Was this helpful?