Migrate from Slack to monday Work Management

The Slack workspace name and settings map to a monday.com workspace. Workspace-level settings (default channels, notification preferences, permission defaults) do not transfer because monday.com applies these at the board and item level. We create the monday.com workspace with the same name during migration setup and document the workspace settings for manual reconfiguration.

Slack public channels map 1:1 to monday.com boards. The channel name becomes the board name; the channel description and purpose (stored in channel topic) become the board description. We preserve the channel creation timestamp and the Slack channel ID as a custom monday.com column for reference. Public channel membership maps to board member access (Admin, Member, or Guest) in monday.com.

Private Slack channels also map to monday.com boards, but require Business+ export tier on the source. We flag any private channels that cannot be extracted (Pro tier workspaces) as a scoping gap before migration begins. The private designation maps to a monday.com board with restricted member access; the private channel membership list becomes the monday.com board member list.

Messages in a Slack channel map to item updates within a monday.com board. We parse each message for assignee and due-date signals (e.g., @person, /due date, task-style language) and surface those as monday.com items with assignees and Due Date columns. Messages without task signals become general updates on an informational item named after the channel. Thread parent messages are preserved; thread replies are merged chronologically as subsequent updates on the same item. This is a lossy translation: thread branching does not map to sub-items.

DMs require Business+ export tier or API-based im:read scope access. We extract DMs that contain task-like language (assignee mention plus due date, or explicit task commitments) and surface them as items in a dedicated 'Slack DM Tasks' board for manual triage. Pure conversational DMs with no task signals are documented in a CSV inventory for the customer's admin to review and discard or create items from manually. This is a pair-specific gotcha: Slack DMs do not cleanly map to any monday.com object without human-reviewed triage.

Slack workspace users map to monday.com workspace members. We extract display name, email (Business+), timezone, and custom status from Slack and provision matching monday.com users. Deleted Slack users retain their display name in message attribution; these are mapped to a 'Slack Deactivated User' placeholder in monday.com rather than a real user. User Groups (subteams) map to monday.com Teams with the same member list preserved.

Slack exports file metadata and URLs, not file blobs. We preserve the file URL, filename, file type, uploaded-by user, and upload timestamp. Files are re-uploaded to monday.com via the monday.com API if they are still accessible (not 404'd due to workspace storage quota). Files returning 404 are flagged in the inventory with the original URL so the customer can attempt manual retrieval. The file upload strategy depends on destination storage quota being pre-provisioned, which we confirm during scoping.

Pinned messages in Slack are preserved as a custom monday.com 'Pinned' toggle column. We add this column to the relevant board during migration setup. The pinned message content and pinning user are recorded. Note that re-pinning functionality does not exist in monday.com in the same way; we use the toggle column as a static record of what was pinned, not a live re-pinnable feature.

Slack custom emoji (workspace emoji reactions) do not map to any monday.com object. monday.com supports native emoji in item updates and column values, but does not have a workspace-level custom emoji library. We document the full custom emoji inventory with image URLs in a CSV for the customer's admin to review; custom emoji cannot be re-uploaded to monday.com in bulk.

Slack reactions (emoji responses) on messages are preserved as monday.com item reactions. We extract the reacting user's ID and the emoji name, then apply the reaction to the corresponding item update in monday.com. Note that monday.com item reactions are a less prominent UI element than Slack message reactions; they appear on item updates but do not surface in board views by default.

Installed Slack apps, OAuth tokens, incoming webhooks, outgoing webhooks, and slash command configurations do not migrate. We document the full app inventory during discovery (app name, OAuth scopes used, connected channels, business-critical rating) and deliver it as a written inventory for the customer's admin to reinstall and re-authorize in monday.com. The monday.com Slack integration specifically can be reconnected post-migration for two-way notifications.

Slack Workflow Builder automations (multi-step forms, alerts, slash-command triggers) are not exported via the admin export tool or API. We deliver a written inventory of every active Slack Workflow with its trigger, steps, and output action for the customer's admin to rebuild as monday.com automations post-migration. monday.com's automation builder supports 200+ templates but requires manual recreation; there is no automated workflow import from Slack.