Moving from Dyno or MEE6
Kovu imports your MEE6 levels and matches Dyno module for module. Keep your old bot running while you set Kovu up, so members never notice the switch.
On this page
Before you startLink to this section
Add Kovu next to your old bot and set your staff roles in Bot Settings (see Getting started). Then open Modules → Moving from Dyno or MEE6 in the dashboard: it maps each of your old bot’s modules to Kovu’s, links to its settings and keeps a checklist your whole team shares.
From MEE6Link to this section
Kovu imports members’ XP, levels and level roles from MEE6’s public leaderboard. Set up MEE6’s other plugins with the checklist.
Make MEE6’s leaderboard public
In MEE6’s dashboard, pick your server, open Leaderboard and turn on “Make my server’s leaderboard public”. Do this last, right before you switch off MEE6’s Levels plugin: XP members earn in MEE6 after Kovu reads the leaderboard doesn’t come over.
Open MEE6’s dashboard to do it. MEE6’s own help explains it in How to make your MEE6 leaderboard public. Kovu reads only what that public leaderboard shows.
Read the leaderboard and check the preview
On Kovu’s Levels page, press Read the MEE6 leaderboard under Import from MEE6. Kovu shows how many members come over, how their levels map and which level roles it can add. Nothing changes yet.
Choose how levels come over, then import
Import their XP (recommended) or keep their MEE6 levels, choose what happens to XP members already earned on Kovu, pick whether to add MEE6’s level roles, then press Import. Nobody gets a level-up message for imported XP.
- How levels come over. MEE6 and Kovu use the same level curve, so importing XP keeps everyone’s level. Keep their MEE6 levels only if staff set levels by hand in MEE6: the preview counts those members.
- Members who already have Kovu XP. Keep whichever is higher (the default), replace it with their MEE6 XP, or add the two together.
- Level roles. Kovu lists MEE6’s level roles and adds the ones it can give. A role that was deleted, sits above Kovu’s role or would hand out risky permissions is left out, and Kovu holds up to 100 level roles.
Switch off MEE6’s Levels plugin
Do it right after the import, so two bots don’t both count XP and announce level-ups. You can make the leaderboard private again in MEE6 too.
What comes overLink to this section
- Each member’s XP, and with it their level.
- MEE6’s level roles, added to Kovu’s Levels settings if you choose.
What doesn’t
- MEE6’s other settings: welcome messages, moderation, custom commands, reaction roles and every other plugin. Set those up with the checklist.
- MEE6’s XP per message and its no-XP channels and roles. Set Earning XP on the Levels page.
- Members below the top 250,000 of a very long leaderboard.
Undoing the importLink to this section
For 14 days, Undo the import on the Levels page takes back the XP the import gave each member. XP they earned since stays, and nobody loses a role. After that, the import can’t be undone.
Every Levels setting is explained in the Levels how-to.
If the import doesn’t workLink to this section
“MEE6’s leaderboard is private”
Kovu can only read a public leaderboard. Do step 1, then press Read the MEE6 leaderboard again. You can make it private again once the import is done.
“MEE6 has no leaderboard for this server”
MEE6 doesn’t know this server, or its Levels plugin is off. Check that MEE6 is still in the server and its Levels plugin is on, then read again.
“MEE6’s leaderboard for this server is empty”
Nobody has XP in MEE6 yet, so there’s nothing to import.
The Import button is grayed out
A preview is good for 24 hours. After that, press Read again so the import uses MEE6’s latest XP.
Members level up faster or slower than in MEE6
The import keeps XP as it was, but each bot gives its own XP per message. The preview says when MEE6’s pace was different; change Earning XP on the Levels page to match it.
From DynoLink to this section
Dyno has no export, so Kovu can’t read your Dyno settings or levels. Kovu matches Dyno module for module and keeps its command names, so rebuilding is quick.
Follow the Moving from Dyno checklist
In the dashboard, Modules → Moving from Dyno or MEE6 lists every Dyno module with the Kovu module that replaces it. Open Dyno’s dashboard next to it and go module by module: turn on the Kovu module, copy over the settings you used and tick it off. The Dyno comparison shows what maps to what.
Set up the Dyno-style defaults
One click on the same page sets defaults close to Dyno’s: Moderation and Automod on, moderation DMs with the reason, starter rules against spam, mass mentions, invites and phishing, and ? as Kovu’s prefix. Dyno no longer takes ? commands, but Kovu does, so staff who still type them keep working. You see every change first and can undo it.
Bring your moderation history over
If Dyno posted a moderation log in a channel, Kovu can read it and add those cases to each member’s history, so warnings and bans aren’t forgotten.
Remove Dyno
When everything you used runs in Kovu, remove Dyno from the server.
Importing history from Dyno’s mod logLink to this section
Open Import from Dyno
In the dashboard, open Moderation, then the Import from Dyno tab. The Dyno checklist on the Moving page links there too. You need Manage Server, or a Kovu manager role.
Pick Dyno’s mod log channel
Choose the channel Dyno posted its moderation log to and press Read the channel. Kovu needs View Channel and Read Message History there and tells you which one is missing. It reads up to 50,000 messages, oldest first, in the background; it can’t reach Dyno itself.
Check the preview
Kovu shows the cases it found by type, the dates they cover, how many members they’re about, a sample, and what it skipped and why. Only cases Dyno’s bot account posted count. With Dyno Premium you can pick your custom Dyno bot instead. Messages from webhooks or people never count. Nothing changes yet.
Import the cases
Press Import. The cases appear in each member’s moderation history marked Imported from Dyno, with Dyno’s case number, and Kovu’s own case numbers carry on. Imported warnings count toward automatic punishments only if you tick that box. You can undo the import for 14 days.
What importing never does:
- It doesn’t message members, post in Kovu’s mod log, or ban, mute, unban or unmute anyone.
- Timed mutes and bans that are still running end only while Dyno is still in the server. Kovu doesn’t take them over.
- Dyno’s settings, levels and custom commands can’t be imported.
From another botLink to this section
Kovu can’t read other bots’ settings or levels, so you set up most features again. Word lists and messages can be pasted in. Most servers are done in an afternoon.
List what your old bot does
Open its dashboard and note each feature your server uses: moderation, automod, logs, welcome messages, roles, levels and the rest.
Find the Kovu module for each
The comparison pages map each bot’s features to Kovu’s modules, with links to their settings. For a bot without a page, search the help center or ask in the support server.
Copy over what you wrote
Paste word lists into an automod word group, one per line or separated by commas, and paste a message’s JSON into the Message Embedder.
Switch the old bot off as you go
Once a Kovu module is set up, turn off the feature it replaces in the old bot, so members don’t get two welcomes or two level-up messages. When everything runs in Kovu, remove the old bot.
With an AI assistantLink to this section
An AI app connected to Kovu can do the module-by-module work for you (see Set up with AI). Ask it to move your server from Dyno or MEE6. It can’t read your old bot’s settings, so open its dashboard and tell the assistant, or show it, what each module does. It maps each one to Kovu and shows you every change before it’s made.
The steps outside Kovu stay with you: making MEE6’s leaderboard public, switching off your old bot’s plugins and removing it.