Move your team from Dust to Cassidy.
Each person gets a short interview, then a personalized step-by-step guide showing exactly where their saved work, prompts, and projects land in Cassidy — and the few things that need a manual step, walked through. You send one invite; nobody becomes the help desk, and nothing in Dust is changed or cancelled. Want to see where you’re paying for both first? Run the free audit.
Both platforms surface agents inside the tools employees already use rather than requiring a separate portal login. Cassidy deploys via Chrome/Edge browser extension, Gmail add-in, Outlook add-in, Microsoft Word/Excel add-ins, Slack, Microsoft Teams, Google Chat, embeddable browser widget, and public API. Dust surfaces agents in its native web app, a native Slack integration (DMs and channels), a browser extension for Chrome/Firefox/Chromium, email forwarding, and programmatically via API plus Zapier/Make/n8n/Power Automate. To migrate from Cassidy to Dust: install the Dust browser extension as a replacement for the Cassidy extension, reconfigure Slack by adding the Dust Slackbot to the same channels where Cassidy was used, and redirect API consumers to Dust's API endpoint with new API keys. For Microsoft 365 surfaces (Word, Excel, Outlook, Teams), Dust does not offer native Office add-ins; teams relying on those will need the browser extension or Dust API as a substitute.
- Warning: Cassidy has native Microsoft 365 add-ins (Word, Excel, Outlook, Teams); Dust has no Office add-in. Teams with heavy Microsoft Office workflows lose in-document access and must use the browser extension or API workarounds.
- Warning: Dust's Slackbot for programmatic (bot-triggered) messages consumes API credits on top of seat cost; Cassidy's Slack deployment is included in the plan. Budget for API credit usage if migrating Slack automation.
- Warning: Google Chat is a supported Cassidy deployment channel; Dust does not list a native Google Chat integration. Check your organization's primary communication tool before switching.
Both platforms let non-technical users create AI agents that execute multi-step tasks using company context. In Cassidy, open the Agent Builder, define agent instructions, attach knowledge sources, configure integrations (CRM, Slack, etc.), and publish; on Business plan you can have unlimited agents. In Dust, open the agent builder, write natural-language instructions, pick a model (Claude, GPT-4, Gemini, etc.), attach data sources (Spaces or Company Data), and assign tools. To migrate Cassidy agents to Dust: export or document each agent's instructions and connected integrations, recreate the system prompt in Dust's instruction field, attach equivalent Dust data connections, then map each Cassidy integration action to a Dust tool or MCP server. Reverse migration follows the same documentation-then-rebuild path.
- Warning: Cassidy Starter plan caps agents at 5; Dust Pro has no documented hard cap but requires a paid seat per user. Budget for seat cost differences when moving large teams.
- Warning: Cassidy agents can be triggered by events, schedules, or API calls; Dust agents are invoked on-demand via conversation or API. Event-driven / scheduled triggers from Cassidy must be re-implemented using Dust's API plus an external scheduler (Zapier, n8n, cron).
- Warning: Dust supports agent delegation via 'Run Agent' tool (one agent calling another); Cassidy's equivalent is chained workflows rather than agent-to-agent delegation. The architecture pattern differs.
Both products ingest company documents and data so agents answer with accurate, company-specific context via RAG. In Cassidy, connect sources via Settings > Knowledge Base: Google Drive, SharePoint, Confluence, Notion, OneDrive, Box, and Dropbox are all supported; Starter plan indexes up to 100,000 pages with 24-hour sync. In Dust, admins add connections under Workspace > Connections: Notion, Google Drive, Confluence, GitHub, SharePoint, OneDrive, Zendesk, Gong, Snowflake, BigQuery, and more are supported with near-real-time sync. To migrate from Cassidy to Dust: connect the same source systems in Dust's Connections panel, grant Dust the same folder/page-level permissions, then assign the resulting data to a Dust Space and attach it to the relevant agents. Reverse migration (Dust to Cassidy) follows the same reconnect-then-attach steps.
- Warning: Cassidy Starter plan syncs on a 24-hour cycle; Dust connections typically update within minutes. Teams relying on near-real-time freshness must be on Cassidy Business plan or switch to Dust.
- Warning: Dust stores ingested data with granular admin-controlled permissions; if source folders are not explicitly whitelisted by a Dust admin, agents will silently lack access to that content.
- Warning: Cassidy supports Dropbox and Box as first-class connectors; Dust lists Dropbox only in beta imports and does not list Box. Confirm connector availability before migration if those are primary sources.
Both platforms connect agents to external business apps so they can read and write data beyond the knowledge base. In Cassidy, integrations are added from the Integrations library (100+ tools covering CRM, communication, project management, HR, and finance); each integration is attached to agents or workflows to grant read/write access to that system. In Dust, agents use 'tools' — native action modules for Notion, Slack, GitHub, Confluence, HubSpot, Salesforce, Gmail, Google Calendar, Outlook, and Zendesk — plus web search/browse and custom MCP servers. To migrate Cassidy integrations to Dust: identify which Cassidy integrations your agents actively write to (not just read from the knowledge base), check whether a native Dust tool covers the same platform, and configure it in the agent builder. For platforms not covered natively, set up a custom MCP server or use Dust's Zapier/Make/n8n connector as a bridge.
- Warning: Cassidy covers 100+ integrations including HR and finance tools (Workday, SAP SuccessFactors, NetSuite, Xero); Dust's native action tools are focused on knowledge-work apps and do not list dedicated HR/ERP connectors. Teams relying on those categories will need MCP or automation middleware on Dust.
- Warning: Dust's MCP (Model Context Protocol) server support enables custom integrations but requires developer setup; Cassidy's no-code integration catalog requires no coding.
- Warning: Some Cassidy integrations (e.g. LinkedIn, Gong, ZoomInfo, Apollo) have no direct Dust native tool equivalent. Verify coverage for each integration before committing to migration.
Cassidy's visual no-code workflow builder handles multi-step, cross-system automations with conditional branching; Dust's developer API and automation-platform connectors (Zapier, Make, n8n, Power Automate) serve the same orchestration role for teams comfortable with those tools. To migrate Cassidy workflows to Dust: document each workflow's trigger, steps, branching logic, and downstream systems; rebuild the trigger in Zapier/n8n/Power Automate pointing to Dust's API (POST a message to the relevant Dust agent); map each step's cross-system write action to either a Dust native tool or a subsequent automation step in the orchestration layer. Dust API authenticates via Bearer token API keys created in workspace settings. Reverse migration (Dust API automations to Cassidy workflows) involves rebuilding the logic in Cassidy's no-code builder and replacing Dust API calls with Cassidy's event triggers.
- Warning: Cassidy provides a no-code visual workflow builder included in the subscription; replacing it with Dust API + Zapier/n8n adds a dependency on an external automation platform and its associated costs and maintenance.
- Warning: Cassidy Business plan supports custom event triggers and advanced workflow actions; Dust's event-driven automation requires an external scheduler or webhook provider — there is no native scheduled or event trigger built into Dust.
- Warning: Dust programmatic API usage is metered separately via credits (billed by token consumption at published rates); Cassidy workflow runs are not token-billed. High-volume automation workflows may incur unexpectedly large credit charges on Dust.
- Warning: Dust Pro workspaces are capped at $50 per active user per cycle with a $1,000 total cycle cap on programmatic credit spending; enterprise teams must negotiate pay-as-you-go to exceed this.