# Move a small team from Slack to chat already in its suite

> Pilot routine team conversations in Google Chat, or in Teams if it is already licensed. Keep Slack when partner channels, automations or historical context are essential.

- Outcome: Run routine internal conversations and linked meeting handoffs without a duplicate chat subscription.
- Replaces: Slack (task_specific)
- Uses: Google Workspace — Baseline: Google Chat for routine discussion and Docs for durable decisions, in the Workspace account the team keeps.
- Extra monthly cost: $0 — Conditional on already having the required accounts, eligible features and sufficient capacity; no upgrade is assumed. If the test requires added storage, seats or a plan change, enter that incremental cost before treating this as a saving.
- Difficulty: moderate; skill: basic; setup: Allow one focused pilot session, then a normal work cycle to test the result; this is an editorial planning estimate.
- Evidence: editorial; illustrative example: false; last reviewed 2026-10-16
- Canonical: https://onelesstool.com/workflows/slack-to-included-chat

## Good fit for
- A small internal team whose important work is already in Google Workspace
- Teams with a limited set of active conversations and few Slack-specific integrations

## Not a fit for
- Organisations dependent on Slack Connect partner channels
- Teams whose bots, workflows or searchable history are business-critical
- A migration that cannot meet required retention, permissions or external-access policies

## Before
Team messages, channels and operational handoffs live in Slack.

## After
Move a bounded set of conversations to existing suite chat, while recording decisions in linked documents and retaining necessary Slack history.

## Steps

### 1. Inventory the real dependencies

List active channels, owners, external participants, integrations and links used in daily work. Separate conversation from durable decisions. Check [Slack pricing](https://slack.com/pricing) and your contract for the effect of a downgrade on access and retained history.

### 2. Choose one already-licensed destination

This baseline uses Google Chat. Confirm it is enabled for every pilot user and check external-user settings with the administrator. If the team instead retains Microsoft 365, Teams is an alternative only when the actual purchased licence includes it; Microsoft offers plans without Teams. Do not purchase a second suite merely to follow this workflow.

### 3. Create a small conversation map

Create only the spaces needed for the pilot and record each space’s owner and purpose. Put decisions, procedures and file links in a shared document. Do not assume a Slack export imports into the destination with identities, threads, permissions or timestamps preserved.

### 4. Rebuild one real handoff

Choose a recurring internal handoff and perform it in the new space. Test notification expectations, file access and a meeting link with the people who will use them. Test any indispensable integration separately; do not substitute a chatbot summary for an operational automation.

### 5. Run a bounded pilot

Choose a normal work cycle and clearly state where new messages belong. Record missed notifications, inaccessible files and confused participants. Keep Slack available for the historical records and external relationships you have not migrated. Avoid two permanent, competing places for the same discussion.

### 6. Cut over only the supported use

Agree on the default destination, publish the space map and preserve required records with an owner. Cancel or reduce paid Slack only after every paid dependency has a working home. If one partner channel or critical bot remains, calculate the retained Slack bill rather than counting a full cancellation.

## Prompts

### Draft a conversation migration map
Turn an inventory into a testable proposal; an assistant is optional, not a required dependency.

```text
Using this channel inventory {{channels}} and these team constraints {{constraints}}, propose a destination-space map, owner and test for each conversation. Flag external members, bots, retention needs and unresolved permissions. Do not claim exports can be imported or that an integration exists. Return questions for the administrator before suggesting cancellation.
```

## Limitations
- The pilot covers routine internal conversations and linked meeting handoffs, not an automatic migration of the entire workspace.
- This workflow does not promise Slack history, app, bot or external-channel parity.
- Google Chat and Teams policies depend on the organisation and actual licence.
- Reduced subscription cost may be outweighed by duplicated conversations and lost context.

## Verification checklist (run before cancelling)
- [ ] Every pilot user can open the agreed chat spaces and linked documents.
- [ ] Notifications and meeting handoffs work on the devices the team uses.
- [ ] External relationships and required records have an explicitly approved retained home.
- [ ] Each essential bot or workflow has been tested, retained or deliberately retired.
- [ ] The team has completed a normal work cycle without an unresolved critical handoff failure.
- [ ] The remaining Slack bill and any new suite seats are included in the calculation.

## Savings methodology
Monthly saving = the bill you can actually stop paying, minus replacement upgrades, storage and seats, minus any retained subscription cost. Use your invoice and current vendor pricing pages; count a cancelled subscription once. Track migration and ongoing manual work separately. Cancellation is justified only when every paid use you need has passed the pilot.

## Sources
- Google Workspace: Chat: https://workspace.google.com/products/chat/ (accessed 2026-10-16)
- Slack pricing: https://slack.com/pricing (accessed 2026-10-16)
- Microsoft 365 business plans: https://www.microsoft.com/en-us/microsoft-365/business/microsoft-365-plans-and-pricing (accessed 2026-10-16)
- Google Drive sharing: https://support.google.com/drive/answer/2494822?hl=en (accessed 2026-10-16)