Skip to content
Zulip help center

Moving from Discord

Welcome to Zulip! This page will guide you through the process of transitioning your organization to Zulip. It assumes that you have completed your initial evaluation of Zulip, decided whether to use Zulip Cloud or self-host, and are ready to introduce Zulip to your organization.

The following steps are described in more detail below:

  1. Create your organization.
  2. Sign up for a plan.
  3. Configure your organization.
  4. Review and update communication policies.
  5. Prepare users for the transition.
  6. Invite users to join.

Each organization is unique, but we hope these common practices will help you think through the transition process in your own context.

Create your organization

Section titled “Create your organization”
  1. If you plan to self-host, set up your Zulip server. You can self-host Zulip directly on Ubuntu or Debian Linux, in Docker, or with prebuilt images for Digital Ocean and Render.
  2. Create a Zulip organization on Zulip Cloud or on your self-hosted server. You can create a new Zulip Cloud organization in less than two minutes. Setting up a self-hosted server will take a bit longer, but is easy to do with Zulip’s robust installer.

Sign up for a plan

Section titled “Sign up for a plan”

If you require features that are not available on Zulip Cloud Free or the Zulip Free plan for self-hosted organizations, you will need to upgrade your plan.

  1. Follow the instructions to upgrade to a Zulip Cloud Standard or Plus plan. If your organization may be eligible for a free or discounted plan, you can apply for sponsorship.

Configure your organization

Section titled “Configure your organization”
  1. Create your organization profile, which is displayed on your organization’s registration and login pages.
  2. Create user groups corresponding to roles in your Discord.
  3. Review organization permissions, such as who can invite users, create channels, etc. Use groups to recreate role-based permissions.
  4. If your organization uses an issue tracker (e.g., GitHub, Salesforce, Zendesk, Jira, etc.), configure linkifiers to automatically turn issue numbers (e.g., #2468) into links.
  5. Set up custom profile fields, which make it easy for users to share information, such as their pronouns, job title, or team.
  6. Review default user settings, including language, default visibility for email addresses, and notification preferences.
  7. Create channels. Zulip’s topics give each conversation its own space, so you likely need fewer channels than in Discord.
  8. To recreate your Discord bots in Zulip, check out Zulip’s native integrations, and the guide on writing your own interactive bots.

Review and update communication policies

Section titled “Review and update communication policies”

Consider updating your organization’s communication policies and practices to take advantage of Zulip’s organized conversations:

  • Many organizations find that with Zulip, there’s no longer a reason to use email for internal communications. You get the organization of an email inbox together with all the features of a modern chat app, like instant delivery of messages, emoji reactions, typing notifications, @-mentions, and more.
  • Because Zulip further organizes messages into conversations labeled with topics, there is generally no need to create dedicated channels for specific projects.
  • With conversations organized by topic, you can review prior discussions to understand past work, explanations, and decisions — your chat history becomes a knowledge base. Should it be standard practice to link to Zulip conversations from docs, issue trackers, etc. for additional context?
  • Using Zulip, you can discuss complex topics and make decisions with input from all stakeholders, without the overhead of scheduling meeting. Are there standing meetings you might not need? For example, stand-ups can be replaced with dedicated check-in topics for each team member.
  • If you’ve been maintaining a forum in addition to your Discord server, it’s common to discontinue it when moving to Zulip. Conversations in Zulip are organized enough to fulfill the role of a forum, and can be configured for public access if desired.
  • Zulip makes it easy to find conversations and follow up, so you may be able to reduce your reliance on @-mentions. Silent mentions make it easy to refer to someone without calling for their attention.
  • Because in Zulip messages are organized by topic, it’ll generally be clear what you’re responding to when you send a message. Consider encouraging users to simply send messages to the appropriate topic, rather than replying as in Discord.
  • If moving a community, be sure to check out Zulip’s community moderation toolkit.

Prepare users for the transition

Section titled “Prepare users for the transition”

Prepare an introduction to Zulip for your organization. It often works well to combine a written announcement with a live presentation. Recommended topics to cover include:

  1. Brief introduction to Zulip.
  2. Why you’re making this change. How do you expect it to improve communication in your organization?
  3. Accompanying changes to your communication policies. Are there any changes to common workflows?
  4. Pointers to additional resources, such as Zulip’s getting started guide.
  5. Transition timeline.
  6. How users will be supported during the transition.

Invite users to join

Section titled “Invite users to join”
  1. Configure allowed authentication methods. Zulip offers a variety of authentication methods, including email/password, Google, GitHub, GitLab, Apple, LDAP and SAML. Users can log in with any allowed authentication method, regardless of how they signed up.
  2. Invite users by sending email invitations or sharing a reusable invitation link.

Congratulations on making the move! If you have any questions or feedback throughout this process, please reach out to the Zulip team.

Section titled “Related articles”