Skip to content
Baseworks KB

Slack to Discord Migration — Potential Future Workflow

Created 2026-07-07
Status preliminary
Tags infrastructurecommunicationsworkflowplatformsdiscordslackplan

Preliminary plan. Originated as a vault capture (2026-05-21) and moved here on 2026-07-07 because it is a real, but time-consuming, future workflow rather than an on-the-go note. Not yet scoped or scheduled — this note holds the decision and the open questions so it is ready to pick up when the time is right.

The decision

Section titled “The decision”

Consider moving the team’s communication and automation workflows from Slack to Discord. This is a strategic infrastructure decision that affects how the team coordinates day to day, where automation events surface, and how future agent workflows are wired in. Patrick’s note (2026-07-07): the migration itself is expected to be quite time-consuming, so it belongs in the plans queue as a deliberate future project, not an ad-hoc task.

Why it is on the radar

Section titled “Why it is on the radar”
  • Discord is already part of the infrastructure direction. The Claude Code Channels — Discord Integration plan already routes agent events and two-way chat through Discord. Consolidating team communication onto the same platform would reduce the number of surfaces to maintain.
  • Single platform for coordination + automation. Backup failures, inbox changes, build errors, and Claude Code sessions could live alongside the team’s own conversation, rather than split across Slack and Discord.

Prior analysis already on file

Section titled “Prior analysis already on file”

Two existing notes cover much of the groundwork, so this is not a blank start:

Start from those two when scoping, rather than re-inventorying from scratch.

Open questions to resolve before scoping

Section titled “Open questions to resolve before scoping”
  • What actually runs in Slack today (channels, integrations, n8n hooks, history worth preserving) and what would need to move versus be rebuilt? (Partly answered in Future-Messaging-Architecture — confirm it is still current.)
  • History/export: is Slack conversation history worth migrating, or is a clean start acceptable?
  • Cost and access model differences (Slack workspace vs. Discord server roles/permissions).
  • Sequencing against the Discord channels plan: does the agent-integration work land first, or the team-communication move?
  • Effort estimate and a rough phase breakdown (this is the “time-consuming” part Patrick flagged).

Next step

Section titled “Next step”

When this is picked up: inventory the current Slack usage, then decide migrate-vs-rebuild per item, and produce a phased plan. Until then it stays in the preliminary queue.

Section titled “Related”