Slack Workspace Import (migrate your Slack into Team Chat)
Status: In-development (gated behind slack-import unreleased feature). Reveal via Settings -> Lab -> Slack Workspace Import, or launch with AMC_SHOW_SLACK_IMPORT=1.
On this page
What it is
Status: In-development (gated behind slack-import unreleased feature). Reveal via Settings -> Lab -> Slack Workspace Import, or launch with AMC_SHOW_SLACK_IMPORT=1.
A guided 6-step wizard that imports an entire Slack workspace into Team Chat: channels, messages, threads, reactions, pins, files, and members. It maps Slack users to existing Omniscio accounts by email. Every imported message shows who really wrote it in Slack: a matched member appears as themselves, and someone who has not joined appears under their Slack name. Either way the message carries a small Imported tag, so it is never mistaken for a message posted in Team Chat. All import writes go through a Cloud Function batch relay (admin SDK); the desktop never writes import data directly to Firestore.
This is distinct from the Slack integration, which triages live Slack messages from the inbox. The import wizard is a one-time migration tool that moves historical Slack data into Team Chat permanently.
Where to find it
Reveal it from Settings → Lab → Slack Workspace Import, then use it from Team Chat's import entry.
How it behaves
How to use it
- Open Team Chat and look for the import entry point (visible only when the
slack-importfeature flag is on). - Welcome step -- confirms your workspace and identity; an "Add Token Now" shortcut navigates to Slack OAuth settings if you haven't connected yet. You must tick the box confirming you have authority to bring this data into Omniscio before Begin turns on; the tick is recorded.
- Discover -- Omniscio fetches your Slack workspace's channels and members.
- Select Channels -- toggle which channels to import (all selected by default).
- Map Users -- shows which Slack users were matched to existing Omniscio accounts by email (the match is made inside the app, not by loading your team list into the screen), and lets you pick a teammate by hand for anyone left over. Matched people's messages appear under their own name; anyone unmatched appears under their Slack name, never yours.
- Import Progress -- live progress updates via push events; cancel is available (with confirmation).
- Report -- summary of what was imported: channels, messages, threads, reactions, pins, files, members, skips, and errors. Members counts each matched person placed in the imported channels once (you are not counted). A Slack direct message with no messages in the last 12 months is skipped and listed under skipped items, so it does not become an empty DM.
Direct messages. An imported Slack DM is named after the other people in it, never after you. People who have not joined the workspace yet are not added to the DM's members (an import can never grant access), so the DM keeps the Slack names in its title.
What's built vs what's left
Built (renderer + IPC + schemas):
- Complete 6-step wizard UI (
SlackImportWizard.tsx+ step components) - IPC channels:
SLACK_IMPORT_DISCOVER,SLACK_IMPORT_START,SLACK_IMPORT_CANCEL,SLACK_IMPORT_PROGRESS(push) - Zod schemas for discover response, user mapping, import request, progress, and report
- Cloud Function batch relay schema (
slackImportBatchSchema) - Double-gating (feature flag on both the entry point and the wizard itself)
- Fresh state on every open (no stale data from a previous attempt)
- Cancel with confirmation dialog
Not yet deployed / remaining:
- Cloud Function batch relay (authored, needs deployment)
- Testing with real Slack workspace data at scale
- Matching beyond exact email (unmatched people appear under their Slack name unless you pick a teammate by hand)
Scope and limits
- Desktop only -- the wizard is a renderer-side feature inside Team Chat.
- One-time migration -- not a continuous sync; run it once to move your history.
- No undo -- a cancelled import keeps whatever was already written; start fresh to retry. Retry (or reopening the wizard) works right after a cancel, with no restart.
- Reactions arrive as emoji -- each Slack reaction becomes its emoji, skin tone included; a workspace's own custom emoji shows as a Team Chat custom-emoji chip. Reactions from people who were not matched to an Omniscio account are left out rather than credited to you, and so is any reaction, pin or file that names a message this import did not create: the run carries on and counts each one as a skip instead of stopping the channel.
- Emoji in messages arrive as emoji -- Slack emoji codes in messages and channel topics (like
:white_check_mark:or a thumbs up with a skin tone) become the real emoji. A workspace's own custom emoji keeps its:name:text, and words joined by underscores are no longer turned into italics. Messages imported before Nov 6, 2026 keep their old text until you import again. - Files and images -- recent files (last 60 days) upload through a server-side upload function that hands the desktop short-lived upload links into your own attachment folder, for workspace admins only. The same function serves the Discord import. Older files are left out on purpose, and file types Team Chat does not accept anywhere (for example CSV and audio) are listed as skipped in the report.
- Cancel stops the run, never the wizard -- cancelling ends the import at its next checkpoint, and that cancellation belongs only to the run it stopped. Workspace discovery is a read, so it keeps working straight after a cancel.
- Admin SDK boundary -- all writes are server-side via the Cloud Function relay.
Related
- team-chat.md -- the Team Chat feature this imports into
- slack-integration.md -- the live Slack triage integration (separate feature)
- Contract: team-chat-slack-import-contract.md
Last verified 2026-11-06