Move from Discord to Taverns without rebuilding supported setup by hand.

The person installing Discord Ripper needs Manage Server permission. The administrator who runs /migrate must have Administrator permission. The new Tavern belongs to the Taverns account that confirms the import.

The import URL is a private bearer link that expires after one hour. Do not share it. A signed-in account with a valid link can currently preview or import it, because the capability is not yet bound to the Discord user who invoked the command.

1. 01

   Install Discord Ripper

   Open the explicit guild-install link, choose the source server, and approve the requested View Channel permission.

2. 02

   Run /migrate

   A Discord administrator runs the command inside the server.

3. 03

   Open the private link

   The bot returns an ephemeral response with a Taverns import URL.

4. 04

   Sign in to Taverns

   Create an account or sign in. Authentication returns you to the same private import URL.

5. 05

   Review the preview

   Check the supported channels, roles, assets, and limits before anything is created.

6. 06

   Confirm the import

   The API creates the Tavern only after explicit confirmation, then opens it in the web app.

• Server identity

  Name, description, icon, and banner.

• Structure

  Supported channels and categories, including ordering and topics.

• Access model

  Supported roles, permission mappings, and channel or category overrides.

• Community expression

  Custom emoji and supported stickers.

• Shared fields

  NSFW and slowmode settings where both products represent them.

Messages, message history, members, member-specific overrides, webhooks, integrations, connected apps, audit logs, scheduled events, and auto-moderation rules are not copied. Managed bot roles are not recreated as ordinary community roles.

Unsupported channel types, permission bits, or sticker formats can be skipped or mapped differently. Lottie stickers are not supported. Keep Discord available during verification instead of treating the import as a destructive cutover.

The importer prepares structure, not people. Members and member-specific roles do not transfer, so plan a deliberate rollout after the Tavern preview looks right. The source server remains read-only throughout the Ripper flow.

1. 01

   Invite moderators first

   Verify permission mappings, hall visibility, rules, and the path a new member will take before sharing the Tavern widely.

2. 02

   Rebuild Discord-specific systems

   Recreate required bots, webhooks, scheduled events, auto-moderation rules, and other integrations manually.

3. 03

   Explain the transition

   Tell members what is moving, what remains in Discord, when invitations open, and where to ask for help.

4. 04

   Use an overlap window

   Keep Discord available while people join, learn the new space, and receive any roles that must be assigned manually.

5. 05

   Choose the long-term role of Discord

   After the community settles in, decide whether Discord stays active, becomes an archive, or remains a fallback.