Switching from one chat platform to another
This article explains how to move Dailybot from one provider (for example Slack) to another (for example Microsoft Teams). The goal is one consistent Dailybot org with everyone on the new chat surface, minimal 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 (or a partner who has them).
- Read Disconnect and reconnect if you previously hot-swapped integrations.
- Communicate a cutover window so people know which bot messages to ignore temporarily.
What transfers vs what does not
| Usually transfers | Usually needs redo |
|---|---|
| Org membership in Dailybot (when accounts are linked or re-invited) | Channel-to-check-in mappings tied to the old chat IDs |
| Historical check-in data stored in Dailybot | Per-platform slash command training materials |
| Billing profile | Bot installs and OAuth grants on the new platform |
Exact behavior can vary when identities do not match between vendors — plan for a short period where some users have two chat accounts until they merge or you deactivate stragglers.
Steps
- Document 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 vendor (Slack, Microsoft Teams, Discord, Google Chat).
- In Dailybot Integrations or Platforms, choose Add or Connect for the new workspace and complete OAuth with the corporate admin account.
- Map members: invite missing users from the new chat, or ask them to sign in with the same email so Dailybot can merge profiles when supported.
- Recreate or edit each check-in so reminders and reports post to channels that exist 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; ask everyone to use Dailybot only on the new platform after that time.
- Disconnect the old chat integration from Dailybot once traffic has moved — avoid running two active connectors longer than necessary to prevent duplicate reminders.
- Archive old runbooks and 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. For stubborn channel errors, use platform-specific troubleshooting from the related articles list.