Transfer a team chat tool by first identifying what is actually moving: a person's access to a new device, workspace data to another platform, or legal and administrative control to a new owner. These are different operations with different evidence. A successful sign-in does not prove that history, applications, billing, retention, recovery, and ownership were transferred.
Decide the transfer type and scope
For a new device, record the workspace, user identity, supported app, multifactor method, device-management requirements, notifications, downloads, and any offline data. For a new platform, inventory public and private channels, direct messages, members, guests, files, reactions, canvases, workflows, applications, webhooks, retention rules, external organizations, and legal obligations. For a new owner, identify the current primary owner, proposed successor, billing contact, domain or identity administrator, recovery contacts, and the date the former owner loses access.
Slack's permissions reference shows why an inventory matters: roles can differ across member management, applications, exports, billing, deletion, and ownership. Record effective powers, not just role names. Do not copy passwords or multifactor seeds into the handoff.
Set up a new device safely
Use the vendor's supported client and the organization's normal sign-in path. Verify the workspace name and domain before entering credentials. Enroll the device if policy requires it, restore accessibility preferences, set notification boundaries, and test an ordinary message, file, call, search, and sign-out. Confirm that restricted channels remain restricted and that the user cannot perform owner or administrator actions merely because the old device could.
Keep the old device available until acceptance, but remove local downloads and end sessions after the new device passes. A remote-session review is important when the old device was lost or transferred. Do not weaken authentication to make the move easier. If recovery depends on a departed person's phone or mailbox, stop and use the documented account-recovery route.
Migrate to another platform with a pilot
Read the source and destination export and import rules before promising completeness. Slack's workspace import guidance documents plan-dependent data coverage, preparation that can take days to months, and unsupported import into Enterprise organizations. Preserve the original export package; changing its contents can cause problems.
Pilot a small representative set containing a public channel, permitted private content, a guest, an attachment, a thread, a reaction, and a deactivated user. Map identities deliberately so messages are not assigned to the wrong person. Compare counts, timestamps, thread order, filenames, access, and searchability. Treat applications, bots, workflows, calls, shared channels, retention, and permission models as separate migration work unless vendor evidence shows otherwise.
Choose a cutover time, freeze avoidable changes, export again if supported, import the delta, and announce which platform becomes authoritative. Keep a reconciliation log for omissions and exceptions. Do not leave two writable systems operating indefinitely without a declared system of record.
Transfer ownership with evidence
Slack's ownership-transfer instructions state that only the Primary Owner can transfer, the recipient must already be a member, and the transfer is immediate. The departing owner should complete the transfer before deactivation. Support-assisted transfer may require evidence and is not guaranteed.
Before the action, verify the successor's identity, membership, role readiness, multifactor access, billing responsibility, and recovery route. Document who authorized the change and define a pause point immediately before transfer. Afterward, have the successor read back ownership, billing, member-management, export, application, and recovery controls. Then reduce or remove the former owner's access according to policy.
Verify acceptance and close the handoff
Test representative allowed and denied actions. For device moves, confirm messages, search, calls, notifications, files, and sign-out. For platform moves, compare a signed-off sample and retain the source archive under appropriate access. For ownership changes, verify the new primary owner and independent recovery without exposing secrets.
Record scope, exclusions, evidence, errors, owner, rollback or recovery path, and acceptance date. The transfer is complete only when the intended people can work, private information remains restricted, the new owner can recover control, and the organization knows which system and records are authoritative.
Sources
- Permissions by role in Slack — Slack Help Center
- Import data from one Slack workspace to another — Slack Help Center
- Transfer ownership of a workspace or org — Slack Help Center