Migrating from Dailybot v2 to v3
This article walks Organization admins through what changes between Dailybot v2 and v3, what moves automatically, what you must reconfigure, and a checklist to reduce downtime for your team.
Key differences (at a glance)
- Home: v3 centers collaboration around a Home feed that aggregates human and agent activity; v2 users often lived primarily in chat threads.
- Agents and AI: v3 assumes coding agents and AI workflows can post structured updates; v2 setups may lack those integrations.
- Dashboard: Navigation, analytics tiles, and admin surfaces were reorganized — muscle memory from v2 may not map one-to-one.
- Billing and seats: Seat logic and admin tooling may show new labels; confirm active members against billing after cutover.
What carries over automatically
In most migrations, org membership, core chat platform connections, and historical check-in data continue to exist in the backend — you are not re-inviting everyone from scratch unless your project plan says otherwise. Single sign-on and billing profile links typically persist when the same legal entity keeps the contract.
What needs manual reconfiguration
| Area | Why it may need work |
|---|---|
| Agent reporting | Repoint reporters, MCP servers, or CI secrets to v3-compatible commands and project names. |
| Webhooks and API consumers | Validate base URLs, signing secrets, and payload assumptions against v3 docs. |
| Custom workflows | Re-test automations that referenced deprecated v2 screens or commands. |
| Training | Update internal wiki screenshots and Slack pinned messages to v3 paths. |
Migration checklist
- Read What’s new in Dailybot v3 for admins with your IT and People partners.
- Export any compliance snapshots you need from v2 reports or admin exports before you change settings aggressively.
- In a staging or pilot team, connect one chat workspace and run a full check-in cycle on v3.
- Update agent instructions and CI env vars so
dailybot-report(or your API client) targets the correct org and project. - Reauthorize integrations that prompt for OAuth again after the upgrade banner appears.
- Open Home as a non-admin member and confirm they see the feed without extra setup.
- Review roles — confirm only intended users remain Organization admin.
- Compare billing seats to active members in the org grid after migration weekend.
- Send a changelog email to the company with links to Home and updated help articles.
- Keep a rollback contact (support or CS) handy until two full business weeks pass without incidents.
What to expect after
Teams may ask where a v2 menu went — point them to Home and the reorganized settings. If you also change chat vendors, stack this guide with Switching from one chat platform to another.