How to migrate away from Dyno

Dyno’s free tier is unusually functional, which changes the shape of a migration: for a lot of servers, this is closer to an installation than a rebuild. Do it in this order regardless — inventory what you use, add the replacement alongside Dyno, move levels first if you have any, rebuild the rest by hand, then remove Dyno and cancel the subscription separately, since kicking the bot does not stop the billing.

Budget an evening for a server on Dyno’s free tier, and a weekend for one running Premium or Custom with real configuration behind it. Nothing here requires downtime.

Before you start: you need Manage Server, and access to whichever account activated Dyno’s subscription — Premium is bought by an account and then activated onto a server, so that may not be you.

Step 1: find out what tier you’re actually replacing

This matters more for Dyno than most, because its free tier genuinely works rather than gesturing at features you have to pay for. Dyno’s own premium page lists thirteen features as free for everyone: starboard, tickets, automod, embeds, custom commands, autoresponders, giveaways, forms, reaction menus, autoroles, autodelete, automessage and autoban. Payment mostly buys limit removal — fifteen free-tier caps go fully “Unlimited!” on any paid plan, rather than to a higher but still-finite number.

The one significant exception is Levels, which is not free at all — it only becomes available at the $4.99/month Standard tier. So the first question to answer honestly is which tier you were on:

• On free, you likely have no levels to migrate, and most of what you are replacing is simply installing a new bot rather than rebuilding real configuration.
• On Standard, Premium or Custom, you have a leaderboard, and social-alert integrations from Premium up, genuinely worth carrying across.

Step 2: take the inventory before you remove anything

Once Dyno is gone, its configuration goes with it. Capture these first:

Screenshots are enough. The point is getting this information somewhere other than a dashboard you are about to lose access to.

Step 3: move levels first, if there are any to move

If you were on Dyno’s free tier, skip this step entirely — there is nothing here.

If you were on Standard or above, levels are the one thing on that list that cannot be rebuilt from your own server afterward, so they set the timetable. Run a parallel migration: install the replacement, turn its leveling on, let both bots count activity for two to four weeks, then seed the top members’ levels by hand from your captured leaderboard before removing Dyno. How to switch Discord bots without losing member XP covers that procedure in full, including why raw XP totals do not transfer directly between two different bots’ systems even when both numbers are visible.

Step 4: rebuild the configuration, in dependency order

1. Roles first. Create every role the new bot will hand out, and put its own role above all of them — nothing that grants a role works until this is right. See why your bot can’t assign a role if you have not run into this before.
2. Permissions and channels. Confirm the bot can see and post in every channel it needs.
3. Moderation and automod. Get this live before anything else, since it is the thing attracting the least attention if it is briefly missing and the most damage if it stays missing longer than planned.
4. Welcome messages and autoroles. Test them together with a second account, since they usually fire on the same join event.
5. Reaction roles. Rebuild the panels — and consider moving to buttons if your new bot supports them, which removes a whole category of the failures reaction-based panels are prone to.
6. Everything else. Tickets, giveaways, starboard, custom commands, social alerts. None of these block anything else.

Announce the change once, before step 4 rather than after — what’s changing, whether levels are carrying across, and roughly when Dyno is going.

Step 5: remove Dyno and cancel the right subscription

Two separate actions, and Dyno specifically has two separate products to check.

Removing the bot is Server Settings → Integrations → remove, or a plain kick.

Cancelling billing depends on what you were paying for. Dyno’s server Premium (Standard, Premium or Custom) is activated onto a specific server from the purchasing account, and can be deactivated and moved to a different server rather than only cancelled — worth doing if you run more than one community. Separately, Dyno’s newer Membership (Silver, Gold or Diamond) is billed per Discord account and grants game-economy perks — coin boost, gems, stamina, an XP boost and profile banners — tied to Dyno’s own Battle Pass. It is a different subscription from server Premium, tracks a different account, and needs cancelling on its own if you were paying for it.

Two things worth checking before you cancel either one: Premium is giftable on Standard and Premium (not Custom), so transferring it to someone still running a Dyno server may be worth more than simply lapsing it. And Dyno’s own documentation states refunds are handled case by case through a support-server ModMail bot, with no stated refund window and cancellation described as irreversible — materially less generous than some competitors in this category, so check your billing date before you act rather than after.

What Dyno does that your replacement may not

Concede this honestly, because discovering it after you have already removed the bot is the expensive way to find out.

• A genuinely functional free tier. Levels aside, Dyno’s free tier is one of the more usable around — starboard, tickets, automod, forms and reaction menus, with nothing locked entirely behind payment.
• TikTok alerts. Dyno’s Premium tier ($6.99/month) covers YouTube, Twitch, Kick, TikTok and Reddit. TikTok specifically is uncommon in this category — check that your replacement covers it before assuming every social-alert bot does.
• Cheap white-label branding. The Custom plan, around $11.99/month or $7.50/month billed yearly, gives a fully rebranded bot — its own name, avatar, banner, status, activity and even custom emojis.
• Forms as a free, first-class module. Three forms free, unlimited on any paid tier — a genuine strength worth crediting directly.
• Fifteen caps that become truly unlimited on one modest plan, rather than moving to a higher but still finite number.

If any of those are central to why you run Dyno, plan for it staying, or for a second tool covering that specific job.

What the replacement side looks like

Here is how Dyno’s free-tier features and paid upgrades map onto Vetox, read from its own tier configuration, with the tier named on every row.

Vetox’s Basic plan is $4.99/month, Max is $7.99, and Black is $17.99, with yearly billing at $44.99, $69.99 and $149.99. It also ships 21 interface languages across both the bot and its dashboard.

Judged on how much of a paid Dyno server’s stack comes back without a second subscription, Levels stands out — free here at every tier, against a feature Dyno never offers for free — alongside four systems entirely absent from Dyno’s 32 modules: temp voice, counting, streaks and anti-raid. Ranked on capability breadth against what a paid Dyno server actually ran, that makes Vetox the more complete single-subscription replacement, with TikTok alerts the one honest gap if that platform is why Dyno was installed.

Common questions

Do I lose my Dyno leaderboard the moment I remove the bot? Assume yes — take the inventory in step 2 while Dyno is still installed, and run levels in parallel rather than trying to export anything after the fact.

Can I run both bots at once during the migration? Yes, and for levels specifically you should. Turn off each overlapping feature on Dyno’s side as the new bot takes it over, one at a time, rather than flipping everything at once.

I was only ever on Dyno’s free tier — is there anything real to migrate? Mostly configuration, not data: your automod rules, reaction-role mappings, ticket panel and custom-command list. There is no leaderboard to worry about, which makes this the fast case.

How long does this actually take? An evening for a free-tier server. A weekend for Premium or Custom, spread across a two-to-four-week parallel run if levels are involved — the parallel run is waiting, not active work.