Switch chat platforms
Move Dailybot from one chat provider (for example Slack) to another (for example Microsoft Teams). The goal is one consistent Dailybot organization with everyone on the new platform, no duplicate notifications, and check-ins pointed at the right channels.
Before you begin
- You need Organization admin access in Dailybot and admin rights on both chat platforms.
- Communicate a cutover window to your team so people know which bot messages to ignore temporarily.
What transfers vs. what needs redo
| Transfers automatically | Needs manual setup |
|---|---|
| Org membership (when accounts use the same email) | Channel-to-check-in mappings tied to old chat IDs |
| Historical check-in data stored in Dailybot | Bot installs and OAuth grants on the new platform |
| Billing profile | Platform-specific slash commands |
Plan for a short period where some users have two chat accounts until they merge or you deactivate stragglers.
Steps
- Document your current check-ins, kudos destinations, and private channel dependencies on the old platform.
- Install Dailybot on the new chat workspace following the setup guide for that platform (Slack, Microsoft Teams, Discord, Google Chat).
- Click Settings in the sidebar, then select API & integrations. Choose Add or Connect for the new workspace and complete the authorization with your admin account.
- Invite missing users from the new chat, or ask them to sign in with the same email so Dailybot can merge profiles.
- Edit each check-in so reminders and reports post to channels on the new platform.
- Run a pilot with one team: submit a test check-in, verify summaries, and confirm permissions on private channels.
- Announce the go-live date and ask everyone to use Dailybot only on the new platform after that.
- Disconnect the old chat integration from Settings once traffic has moved. Avoid running two active connectors longer than necessary to prevent duplicate reminders.
- Update internal docs with the new slash commands or app names.
What to expect after
Members should see a single Dailybot experience tied to the new workspace. If duplicate bots appear, revisit step 8 and confirm only one integration remains active.