Skip to content

Moving from Microsoft Teams

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

If you’re moving from other communication tools, check out the general guide on moving to Veloxa Talk.

The following steps are described in more detail below:

  1. Import or 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.

  1. If you plan to self-host, set up your Veloxa Talk server. You can self-host Veloxa Talk directly on Ubuntu or Debian Linux, in Docker, or with prebuilt images for Digital Ocean and Render.
  2. Follow the steps in the Microsoft Teams import guide.

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

  1. Follow the instructions to upgrade to a Veloxa Talk Standard or Plus plan. If your organization may be eligible for a free or discounted plan, you can apply for sponsorship.
  1. Create your organization profile, which is displayed on your organization’s registration and login pages.
  2. Create user groups, which offer a flexible way to manage permissions.
  3. Review organization permissions, such as who can invite users, create channels, etc.
  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. Veloxa Talk’s topics give each conversation its own space, so one channel per team should be enough to get you started.
  8. Take advantage of Veloxa Talk’s native integrations ecosystem by connecting Veloxa Talk with the tools you use.

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

  • Many organizations find that with Veloxa Talk, 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 Veloxa Talk 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 Veloxa Talk conversations from docs, issue trackers, etc. for additional context?
  • Using Veloxa Talk, 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.
  • In Veloxa Talk, it’s easy to have many conversations in parallel without losing track of anything. Consider adjusting your communication guidelines to recommend having substantive discussions in channels, with less reliance on DMs.
  • Veloxa Talk allows users to fine-tune their notification settings. Make sure you’re happy with the defaults for your organization, and encourage users to adjust from there.
  • Veloxa Talk makes it easy to find conversations and follow up. To avoid disrupting focus work, @-mentions in Veloxa Talk should generally be reserved for time-sensitive messages. Silent mentions make it easy to refer to someone without calling for their attention.

Prepare an introduction to Veloxa Talk 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 Veloxa Talk.
  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 Veloxa Talk’s getting started guide.
  5. Transition timeline.
  6. How users will be supported during the transition.
  1. Configure allowed authentication methods. Veloxa Talk offers a variety of authentication methods, including email/password, Google, GitHub, GitLab, Apple, Discord, 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 Veloxa Talk team.