Private equity and portfolios
Slack and Teams workspaces from acquisitions: merge, archive or export?
By SourceX Editorial · Updated
Short answer
Slack and Teams workspaces from acquisitions have three exits: merge active channels into the platform's workspace, archive the old workspace read-only, or export its full history and close it. Most groups combine them: export everything first, merge what people still use, and check ownership, plan limits and retention settings before any channel moves.
Key takeaways
- Merging moves the conversations people still use; exporting preserves the history a merge can leave behind.
- Check workspace ownership, plan, retention settings and legal holds before choosing an option.
- Public channels, private channels, direct messages and shared channels are separate scopes with separate permissions.
- Exported chat archives can hold credentials and customer details, so restrict access and scan them before any reuse.
What are the options for an acquired company's chat workspace?#
An acquired company's Slack or Teams workspace can be merged into the platform's own workspace, archived where it is, or exported in full and closed. Each choice keeps a different part of the history, and each is easier to change before people start moving channels.
Pressure usually comes from two sides. Employees want one place to talk from the first week, and finance wants to stop paying for a second workspace. Neither goal requires a rushed decision about history, provided a full export is taken before anything else happens.
The decision also has an owner problem. In many smaller companies the workspace was created by a founder or an early engineer whose account still holds the top admin role, and that person may be leaving as part of the deal. Transfer that role to a company-controlled account before anything else.
What each option keeps#
Merging keeps only the channels that are moved, archiving keeps everything for as long as the plan and retention settings allow, and exporting keeps whatever the export reaches. Specifics depend on the migration tool, the plans on both sides and the settings in place, so confirm them with a test run on a single channel.
Retention settings deserve special attention. If the acquired workspace was set to delete messages or files after a period, older history may already be gone, and neither a merge nor an export will bring it back.
| Option | Threads and replies | Files | Older channel history | Private channels and DMs | Main risk |
|---|---|---|---|---|---|
| Merge into platform workspace | Kept for channels moved | Kept if the tool carries them | Kept only for channels moved | Often left behind or handled separately | Assuming the move carried everything |
| Archive in place, read-only | Kept | Kept | Kept while plan and retention allow | Kept, with access to control | Ongoing cost and retention quietly deleting content |
| Export, then close | Kept in the export | Kept if downloaded with it | Kept as far back as the export reaches | Only if plan and approvals allow | Losing whatever the export did not cover |
| Shared channels during transition | Visible to both organizations | Shared | Not moved | Not affected | Treating a temporary bridge as the plan |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Export permissions to check first#
Export permissions should be confirmed before the integration plan is announced, because they decide which conversations can be preserved at all. Workspace exports differ by plan: public channels, private channels and direct messages are often treated as separate scopes, and some require a higher plan or an approved request. Check the vendor's current documentation for your plan.
Write down each answer and who confirmed it. That record becomes part of the archive's provenance if the history is ever reused.
- Ownership: who holds the primary owner or global admin role, and whether that person is staying.
- Plan level: which conversation types the current plan can export, and whether a temporary upgrade is needed.
- Retention: message and file retention settings, and what they have already removed.
- Legal holds: litigation or regulatory holds that require preservation in place.
- Policies and notices: what the acquired company told employees about monitoring, retention and access to messages.
- Shared channels: which channels include customers, vendors or contractors from other organizations.
- Integrations: bots and connected apps that posted records into channels, such as ticket or deploy alerts.
Teams tenants and mixed environments#
Teams tenant migrations are harder to treat as a single move, because Teams conversations, chats, files and meeting content are not all stored in the same place within Microsoft 365. A tenant-to-tenant project has to account for each, and migration tools vary in which parts they carry and whether original authors and timestamps survive.
Mixed environments, where the platform runs Slack and the add-on runs Teams or the reverse, rarely justify converting history between products. The usual approach is to move people onto the platform's tool for new work, export the old history in its native form, and keep it searchable for the people who need it.
Which option fits which situation?#
The right option follows from how much the add-on's people still rely on their channels and how much the history is worth keeping. Use these rules as a starting point, then adjust for legal holds and customer commitments.
Whatever the choice, set a point at which it is reviewed. An archived workspace left on autopilot keeps billing, keeps its retention rules running and keeps former employees' accounts active unless someone deprovisions them. A review once integration settles shows whether the archive is still used and whether the export alone is enough.
| Situation | Lean toward |
|---|---|
| Small add-on, channels mostly social or short-lived | Export, then close |
| Project or engineering channels still in daily use | Merge those channels; export everything first |
| Legal hold or open disputes | Archive in place under the hold, and export as well |
| Different chat products on each side | Move people for new work; export old history natively |
| Many shared channels with customers | Keep a transitional shared channel; agree history handling with each customer |
Illustrative: a software platform folds in two add-ons#
Illustrative: a fictional vertical software platform on Slack acquires a scheduling software vendor, also on Slack, and a reporting tool vendor on Teams. The scheduling vendor's engineering channels hold years of deploy alerts, bug triage threads and links to its Git repository. The reporting vendor's tenant is used mainly for chat and meetings.
The platform's CTO exports both workspaces before any move, confirms that retention settings had not removed older content, and checks what each add-on's employee handbook said about access to messages. Active engineering channels are merged into the platform workspace. The Teams tenant is exported and closed. Both archives are stored read-only with a named owner.
When the group later considers whether chat history could support AI work, only the scheduling vendor's public engineering channels are put forward for review. Direct messages and private channels stay out of that scope by default.
Before reusing a chat archive#
Chat archives are among the most sensitive records a company holds, so reuse needs more than a successful export. Exports can contain passwords, API keys and access tokens pasted into channels, alongside customer names and personal details. Secret scanning is not limited to code: TruffleHog, an open-source scanner, says it scans sources including chats, wikis and logs, and because its verification feature attempts live logins, it should be run with operational care.
SourceX treats chat as a scoped record family. In the Rights and Preparation steps of the SourceX five-step transaction, scope usually starts with public work channels, questions about employee notice and consent are reviewed with counsel, and names, personal details and confidential content are stripped out before the supplier approves anything for delivery.
Frequently asked questions
Will merged channels keep original authors and timestamps?
That depends on the migration tool and its settings. Some carry original authors and dates; others post imported messages under a bot account or with changed timestamps. Run a test merge on one channel, compare it with the original, and keep the full export as the reference copy.
Can we delete the old workspace once the export is done?
Only after the export has been checked for completeness, any legal holds are addressed and retention obligations are understood. Record what was exported, what was not, and who approved closure. Deleting the workspace removes the last copy of anything the export missed.
Do employees need to be told about an export?
It is usually good practice, and the acquired company's own policies may require it. What employees were told about access to messages, and the laws where they work, shape what can be done later. Employee notice is assessed with counsel, especially before any reuse beyond integration.
What about shared channels with customers?
Messages in shared channels were written by people in two organizations, so neither side should treat the other side's messages as its own records. Keep shared channel history in the archive for continuity, and leave customer-written messages out of any reuse unless the customer agrees.
Can an acquired company's chat history be licensed?
Sometimes, when channels record work rather than private conversation and the rights, notices and privacy review support it. Direct messages are generally excluded. Each entity's history is assessed on its own, and identifying and confidential content is stripped out before any sharing.
Sources
- TruffleHog, an AGPL-3.0 open-source secret scanner from Truffle Security, says it classifies over 800 secret types. For each secret it can classify, it can log in to confirm whether the secret is live, and it scans sources including Git, chats, wikis, logs, object stores and filesystems. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.