Migrating from Dailybot 2 to Dailybot 3

Dailybot v3 is a significant platform update that introduces agent reporting, AI-powered intelligence, and a redesigned workflow engine. If your team has been running on v2, this guide walks you through everything you need to know to migrate smoothly.

What changed in v3

Agent reporting system

The headline feature. Dailybot v3 introduces native support for coding agent progress reports. Agents like Cursor, Claude Code, Copilot, and others can now report their work directly into your Dailybot workspace. Human check-ins and agent reports appear in a unified feed.

Redesigned check-ins

Check-ins received a visual refresh and new capabilities. AI-powered smart summaries automatically condense team responses into key takeaways. Conditional logic is more flexible, supporting multi-branch follow-ups. The response experience in chat platforms is smoother with better formatting and inline previews.

New workflow builder

The v2 rule system has been replaced with a visual workflow builder. You can now create complex automation chains with drag-and-drop — triggers, conditions, actions, and delays are all configurable without writing code. Existing v2 rules are converted automatically, but custom configurations may need review.

Improved dashboard

The dashboard is faster and more information-dense. Team feeds, analytics, and settings are accessible from a redesigned navigation. Widgets are customizable — pin what matters, hide what does not.

MCP support

Dailybot v3 supports Model Context Protocol for tool integrations. Coding agents that speak MCP can connect natively, and Dailybot’s own capabilities are exposed as MCP tools for agent orchestration.

What stays the same

Not everything changed. These core elements carry over from v2:

• Chat platform integrations — Slack, Microsoft Teams, Discord, and Google Chat connections work the same way. No need to reconnect.
• Team structure — Your teams, members, and permissions transfer automatically.
• Check-in history — All past responses, summaries, and analytics data are preserved.
• Core check-in flow — Team members still receive prompts in their chat platform, answer conversationally, and responses are collected centrally.
• Kudos — The kudos system works the same, now with enhanced analytics.
• Scheduling — Timezone-aware scheduling, response windows, and recurrence patterns are unchanged.

What needs manual migration

API integrations

If your team built custom integrations using the v2 API, you will need to update them. Key changes:

• Base URL — API endpoints moved to a new versioned path.
• Authentication — v3 uses workspace-scoped API keys instead of user-scoped tokens. Generate new keys from the settings panel.
• Webhook payloads — Event payloads have a new structure with additional fields. Review the webhook reference for updated schemas.
• Deprecated endpoints — Some v2 endpoints are deprecated. A compatibility layer is available for 6 months, but plan to migrate to v3 endpoints.

Custom workflow rules

Automated v2 rules are converted to v3 workflows, but complex rules with multiple conditions may need manual review. Open each converted workflow in the builder and verify the logic matches your intent. Pay special attention to notification routing — v3 uses a different channel selection model.

Third-party tool connections

If you connected Dailybot to external tools via Zapier, custom webhooks, or API calls, test those connections after migrating. Most will work, but payload structure changes may require updates to your Zap configurations or webhook handlers.

Step-by-step migration checklist

Before you start

• Review this guide completely
• Identify any custom API integrations your team uses
• Note any custom workflow rules that need verification
• Schedule a 1-hour migration window during low-activity hours

Migration steps

1. Upgrade your workspace. Open Dailybot settings and click “Upgrade to v3.” The platform migrates your data — teams, members, check-in history, and basic workflows — automatically.

2. Verify check-ins. Open each active check-in and confirm the questions, schedule, and team assignments are correct. Run a test check-in to verify the flow works end to end.

3. Review converted workflows. Open the workflow builder and inspect each auto-converted rule. Fix any logic that did not convert cleanly. Test each workflow with a dry run.

4. Update API integrations. Generate new v3 API keys. Update your integration code to use v3 endpoints and payload structures. Test each integration.

5. Test webhook endpoints. If you have registered webhook endpoints, trigger sample events and verify your handlers process v3 payloads correctly. Update parsing logic as needed.

6. Connect coding agents (optional). If your team uses coding agents, set up agent connections in the new agents section. This is a v3-only feature — there is nothing to migrate, just configure.

7. Explore new features. Set up smart summaries, try the new dashboard widgets, and explore agent reporting. These are additive — they do not disrupt existing workflows.

After migration

• Confirm all team members received their next scheduled check-in
• Verify notification routing works as expected
• Check that analytics dashboards show historical data correctly
• Remove deprecated v2 API keys after confirming v3 integrations work

Common issues and solutions

Check-in schedule shifted after migration. Timezone handling improved in v3. If your check-in fires at a different time, open the schedule settings and verify the timezone is set correctly for each team member.

Webhook endpoint stopped receiving events. The payload structure changed. Check your endpoint logs for parsing errors and update your handler to match the v3 payload format documented in the webhook reference.

Custom workflow rule logic changed. Complex v2 rules with nested conditions may not convert perfectly. Open the workflow in the visual builder, trace the logic, and adjust conditions or actions as needed.

Missing dashboard widgets. The v3 dashboard is customizable. If your preferred views are not visible, use the widget selector to add them back. Your data is still there — the layout just needs configuration.

If you run into issues not covered here, reach out to the Dailybot support team. Most migration questions are resolved within a business day.