Follow this short guide to migrate your existing setup and subscribers to Suby in just 3 steps.
Go to your Discord server, open any team channel, and type
This command launches the migration assistant directly in Discord.
You’ll go through a short, guided flow to select what should be imported into Suby.
Phase 1 — Select roles to migrate
In this step, you’ll tell Suby which roles represent paid memberships in your server.
These are usually roles like @VIP, @Premium, or @Pro.
Note: This phase only imports data. It doesn’t touch your existing members, roles, or permissions.
If you see the message “No active plans found for this server”, it means you haven’t created a plan yet.
Go to to create your subscription plans once done, you’ll be able to continue the migration.
Tip: Only migrate roles that correspond to active subscriptions. Free or inactive roles don’t need to be imported.
Phase 2 — Link roles to plans
Now you’ll connect each paid role to its corresponding Suby plan.
This ensures that when someone subscribes, they automatically receive the right Discord role.
Each role must be linked to a plan you’ve created in Suby.
If you have multiple tiers (e.g. “VIP Silver” and “VIP Gold”), make sure to match them accurately.
Progress indicator example:
Important: Only roles linked to a plan will be migrated.
If a role has no plan attached, its members won’t be included in the migration.
Phase 3 — Select your payment notification channel
In this phase, you’ll select the channel your previous bot used to send payment confirmation notifications. Here’s an example of the message it sends: the one highlighted in green.
This step is essential, Suby uses this channel to import your existing reminder data and correctly sync user subscriptions.
If you choose the wrong channel, Suby won’t be able to recover your past reminder data, and some users may not be migrated properly.
Tip: Check your old bot’s settings or message history to confirm which channel handled payment notifications.
Once selected, Suby will automatically read your past message logs and prepare a migration summary.
You can still update the reminder channel later using /setupreminders if needed.
Migration Summary
Before confirming, you’ll see a recap of everything being imported.
Double-check this summary carefully.
Once confirmed, Suby finalizes the import and displays a migration report.
Final Steps Before Going Live
Run /setupreminders to configure the reminder messages your users will receive.
Run /setupsubscription to publish your plans on Suby.
Remove your old Payment Bot to avoid conflicts.
Once these are done, your Suby setup is ready to go live
Want help setting it up?
Payments are sensitive, we totally understand that.
If you’d like a quick walkthrough of Suby, our vision, and our team, we’d be happy to guide you through it. Just open a ticket and we’ll take care of the rest.
