Omniscio

Import from Slack — bring a Slack workspace into Team Chat

Open Team Chat, open the sidebar's more menu, and choose Import from Slack. A six-step wizard finds the Slack workspace you already connected, lets you pick channels, shows how Slack people map to your team, and copies everything into the Team Chat workspace you are in. Nothing is written until you start the import, you can cancel at any point, and re-running is how you repair a run that was interrupted.

On this page

What it is

Slack Workspace Import is part of Team Chat, not a separate app, so it turns on wherever Team Chat is on — there is no second switch to find. It imports:

  • channels, with their names, topics, purposes and members
  • messages, including threaded replies, kept as threads
  • reactions, pins and channel membership
  • files shared in the last 60 days, as normal Team Chat attachments

Where to find it

Team Chat → the more menu at the top of the sidebar → Import from Slack. If Team Chat is on, the action is there; every member of a workspace sees Team Chat exactly as before, and the import itself is available to workspace admins and owners only, because it writes a lot of history at once.

The six steps

  1. Welcome — confirms the connected Slack workspace and you as the importer. A required consent checkbox keeps Begin disabled until you confirm you have the right to bring that data in.
  2. Discover — reads the Slack channel and member lists and matches people to your team by email.
  3. Select Channels — every channel is selected by default; switch off the ones you do not want.
  4. Map Users — shows the email match and lets you map anyone by hand from your team's roster. An admin can also invite the unmatched people by email in one go.
  5. Import Progress — live progress, with Cancel import.
  6. Report — counts of channels, messages, threads, reactions, pins, files and members, with problems listed first and the things left out on purpose listed separately.

What happens to people who are not on your team

A Slack member matched by email, or mapped by hand, appears in Team Chat as themselves. Everyone else keeps the name they had in Slack, with an Imported tag beside it, and no profile link. Their messages are stored under the importer's account because nobody else can own them yet, which is also what makes them erasable later by their Slack identity.

Cancelling and starting again

Cancelling keeps whatever was already written — there is no undo — and the wizard confirms before it stops. Running the import again is the repair path: imported documents have stable ids, so a re-run fills in what is missing and never resurrects a message you deleted or undoes an edit you made. Large workspaces can take a few minutes.

Security

Every write goes through one server-side relay, so the desktop app carries no direct database path for import data. The relay re-checks that you are an admin of the workspace you are importing into, refuses any direct-message path, refuses a batch that would rewrite a channel it did not create, and bounds every imported value it stores. Files are uploaded only into your own folder inside that workspace and only with a link minted for that exact channel and file.

Verified on the live service

The import was proven end to end on 20 November 2026, 10:44 PM against the live cloud service, not a simulation. One batch carrying a channel, three messages, a threaded reply and a reaction was sent with a signed-in test account into a throwaway test workspace. The service answered 200 and reported all six rows written with nothing dropped: the channel came back private and named, all three messages came back stamped as imported, the reply kept its thread parent, the reaction kept its emoji, and the per-row import ledger recorded every one. The test workspace, its channel, the test account and the import's quota and audit rows were then deleted in the same run and re-read to confirm they were gone.

The same check is repeatable with prove-slack-import-relay.mjs, which seeds its own workspace, drives the batch, reads it back and tears everything down.

Last verified 2026-11-20