Slack Import Wizard
Status: In-development (gated behind slack-import unreleased feature flag). A guided, multi-step wizard that imports a Slack workspace's channel history into Team Chat. The wizard discovers a connected Slack workspace, lets the user pick channels, reviews the Slack-to-Firebase user auto-match, then runs the import with live progress and a final report.
On this page
What it is
Status: In-development (gated behind slack-import unreleased feature flag).
A guided, multi-step wizard that imports a Slack workspace's channel history into Team Chat. The wizard discovers a connected Slack workspace, lets the user pick channels, reviews the Slack-to-Firebase user auto-match, then runs the import with live progress and a final report.
Where to find it
The wizard is gated behind the unreleased Slack Workspace Import feature — reveal it from Settings → Lab — and it is launched from Team Chat once revealed.
How it behaves
Steps
- Welcome — overview and prerequisites (a connected Slack workspace via Settings). The import reuses the Slack connection you already made in Settings → Channels → Slack (Connect Slack, or the manual setup), including the personal token it saved, so once you are connected it asks for nothing more.
- Discovery — automatic; briefly shows a loading state while the wizard discovers available Slack channels and members. No dedicated step component (rendered inline).
- Channel Selection — lists discovered channels; user picks which ones to import.
- User Mapping — auto-matches Slack members to Omniscio workspace members; user can adjust mappings. A person invited but not yet signed in stays unmatched. Anyone left unmatched ("Keeps original name") is not imported under your name: their messages keep their original Slack name and carry the Imported tag — as every imported message does, matched or not. Invite the people it could not match: a workspace owner or admin importing into the company workspace sees an invite box above the list ("N unmatched members have an email address and can be invited to your workspace") with an Invite all button. It asks first ("Send invites to N people?"), then emails one invite per address, each address once, through the same invite path as Settings → User Management. Afterwards it says who was invited, whose invite email did not go out, how many were not sent yet, and who failed and why; invited people get an Invited label next to their row, and anyone not yet invited stays on offer, so Invite all again retries just them. Inviting does not change the import: an invited person's messages come in under their Slack name, with an Imported tag, until they are matched to an account, and you can still map anyone by hand. An import into a self-serve workspace shows no invite box (those workspaces invite by share code). One import matches up to 50,000 people, the same ceiling member discovery uses; a workspace with more people is stopped before anything is imported, and the message names both the workspace's count and the ceiling.
- Import Progress — live progress bar with per-channel status. Once anything fails, the error count is joined by the newest error in words ("Latest: ..."), so you can see which step went wrong while the import keeps running. If Cancel import itself fails, the button comes back so you can try again; if the cancel request only timed out, it stays on "Cancelling..." because the cancel may still go through.
- Report — summary of imported messages, channels, and any errors. An import with failed rows says so in its heading ("Import finished with 2 errors", with a warning badge instead of the green check). When anything failed, or was skipped for a reason other than being left out on purpose, Copy error report copies the failed rows and skipped items, with the reference, as plain text; when rows failed, a next-step line says to run the import again: imported items keep the same ids, so anything that already came across is not duplicated. Every run also shows a Reference under the heading, the same id the app log records for that import, to quote when asking for help. A file that could not be uploaded is listed by its file name. Skipped items come in two groups: real problems first, in an open list ("2 items skipped" — a failed upload, thread replies that could not be loaded, an unsupported or too-large file), then the items the import leaves out by design in their own closed group, "N left out on purpose (normal)" — channel join/leave and other channel notices, DMs with no messages in the import window, pins that point at messages older than the window, and files older than 60 days. Nothing in that second group needs action. The copied report keeps the same order and headings. The Discord and Obsidian import reports keep their single skipped list.
If an import is still running when you open the wizard, or when a new start is refused because of it, the wizard goes back to that import's live progress with Cancel import available, and moves on to its report when it finishes.
Privacy
Imported Slack messages, member profiles, and channel metadata are stored in Firestore. Imported Slack and Discord messages follow the same plan-based retention as native Team Chat messages, counted from when the import landed: Free workspaces keep them 90 days, Pro 365, Team and Enterprise indefinitely. Their reactions and shared-media rows are removed together with the message. Imported member and channel-member rows are memberships of existing workspace members and stay until the workspace is deleted. Retention applies only while plan enforcement is switched on. Every imported row records which system it came from and the source person's own id (source + sourceUserId, e.g. slack-import / U0G9QF9C6), so an imported person who has no Omniscio account can be erased without a Firebase uid: eraseImportedChatUser in firebase/functions/src/team-chat/erase-user.ts takes { sourceSystem, sourceUserId } and tombstones their imported message bodies and member display names, and deletes their imported reaction, channel-member pointer and shared-media rows, leaving everyone else's alone. Imported rows carry no expiry deadline yet: the import retention window waits on confirmation of the published retention policy.
Related
- Team Chat — the parent feature these imports feed into.
- Discord Import Wizard — the sibling Discord importer.
Last verified 2026-10-17