Slack to Microsoft Teams Migration Planning Prompt

You are a senior IT architect who has led Slack-to-Teams migrations in enterprises with thousands of users, hundreds of channels, dozens of integrations, and significant change management.

I will provide:
- Slack workspace inventory (members, channels, apps, integrations)
- Target Teams tenant configuration
- Identity provider on both sides
- Compliance regime
- Timeline constraints
- Anticipated user resistance level

Your job:

1. **Pre-flight inventory of Slack**:
   - Users + their email + SSO mapping
   - Channels (public / private / DMs / MPIMs / Connect / archived)
   - Apps + tokens + their function (per-app criticality)
   - Webhooks + endpoints + secret storage
   - Workflow Builder workflows
   - Custom emoji + canvases
   - Retention policies + eDiscovery holds
   - Slack Connect partnerships

2. **Teams-side decisions before migration**:
   - Tenant region + data residency
   - Naming conventions for Teams (vs Slack workspaces)
   - Channel topology (per-team / per-product / per-region)
   - Private vs Standard vs Shared channel choices
   - App governance policy in Teams

3. **Identity reconciliation**:
   - Both sides typically connect to the same SSO; map Slack email → Entra UPN
   - Detect mismatches early; document expected exceptions (contractors, service accounts)
   - For accounts without M365 license — decide: license or block

4. **Channel mapping** — many-to-many:
   - One Slack channel → one Teams channel (simplest)
   - Multiple related Slack channels → one Teams channel with multiple tabs
   - Slack DMs → personal chats (default; nothing to migrate)
   - Slack Connect → Teams Shared Channels with same partners (requires partner cooperation)

5. **Integration re-wiring** — for each Slack app, identify Teams equivalent:
   - PagerDuty Slack app → PagerDuty Teams app (both exist; permissions differ)
   - GitHub Slack app → GitHub Teams app (or Power Automate flow)
   - Datadog → Datadog Teams integration
   - Custom bots → port to Bot Framework or evaluate retirement
   - Webhooks (Slack incoming webhooks) → Teams Workflows webhooks
   - Workflow Builder → Power Automate flows

   Plan per-integration risk + effort + owner.

6. **History migration** — options:
   - **No history migration** — clean slate; lowest risk; Slack archive kept for reference
   - **Export-only** — Slack export to a SharePoint library for search; not "live" in Teams
   - **Third-party tool** (Microsoft / Quest / others) — imports messages as Teams chat messages; quality varies; expensive; some compliance limitations

   Recommend "no history migration" with retained Slack archive read-only for 1 year, then dispose per retention policy.

7. **User communication & change management**:
   - T-90d: announce decision, reasons, timeline; FAQ
   - T-60d: tooling decisions (which Teams app for which Slack feature)
   - T-30d: pilot team migrated; lessons published
   - T-14d: "your team migrates next week" message + training session
   - T-0: cutover day; old Slack read-only
   - T+30d: post-cutover survey + adjustments
   - T+90d: full Slack deprecation; archive secured

8. **Phased rollout** — by team:
   - Pilot: one tech team (IT or eng), 2-week soak
   - Wave 1: tech departments
   - Wave 2: customer-facing teams (more friction; need integrations stable)
   - Wave 3: rest of company
   - Adjust pace based on retention metrics

9. **What you'll lose moving to Teams** — be honest:
   - Slack's threading is denser
   - Workflow Builder is simpler than Power Automate
   - Slack search is fast
   - Slack Connect has more mature controls
   - Custom emoji culture (Teams allows but UX is different)

10. **What you'll gain**:
   - M365 integration (Loop, Planner, SharePoint, Power BI tabs natively)
   - Teams Phone integration
   - Better Adaptive Card UX for approvals
   - Native Conditional Access
   - Premium meeting features (transcripts, copilots)

11. **Post-migration validation**:
   - All integrations functional
   - Search works for relevant content
   - Compliance + retention applied
   - User adoption metrics (DAU, message volume per team)
   - Survey results

Output as: (a) inventory questionnaire, (b) channel mapping rules, (c) integration migration matrix, (d) history migration recommendation with reasoning, (e) phased rollout schedule, (f) change management comms calendar, (g) honest tradeoffs ("what you'll lose"), (h) post-migration validation checklist.

Bias toward: pilot before wave, integrations stable before broad rollout, retain Slack archive, set realistic expectations.