Slack to Slashwork Migration

Point this agent at your Slack-integrated codebase and your Slack workspace export, and ask it to plan your migration to Slashwork.

What it does

A Slack migration has two lanes, and this agent works both:

1. Data lane — channels, users, and message history move via Slashwork's native Slack importer (driven from your standard Slack workspace export).
2. Code lane — bots, incoming webhooks, and Events API consumers are mapped, planned, and re-scaffolded against Slashwork's GraphQL API.

The workflow:

1. Map your Slack integration surface (SDK calls, webhooks, event subscriptions, Block Kit usage) and tier each finding as mechanical, rework, or redesign.
2. Plan a phased migration: provision → history import → integration translation → parallel running → cutover.
3. Import message history from a Slack export using the native importer.
4. Scaffold the Slashwork GraphQL calls (users → teams → groups → memberships → webhooks) plus translated integration code.
5. Sandbox — execute the scaffold against a Slashwork test company and report PASS/PARTIAL/FAIL validation evidence.

Prerequisites

• SLASHWORK_API_TOKEN — Application bearer token for a Slashwork test company
• SLASHWORK_GRAPHQL_URL — your company's endpoint, for example https://yourcompany.slashwork.com/api/graphql
• SLACK_BOT_TOKEN — optional; enables read-only enumeration of the source workspace for mapping and parallel-run diffing