Tools and providers
How to retire a corporate communications channel without losing its records
How to close or migrate a corporate communications channel while keeping its records: exit plans, retention schedules, exports, membership and cost baselines.
What to take away
- Pick the end state before you announce anythingdeletion, a read-only archive, or migration to a successor channel.
- Write a channel exit plan naming the record owner, the retention period and the retrieval route.
- Export posts, threads, files and membership lists into a store your records team controls.
- Test one export before deleting the source, and log the decision and the approver.
- Cost the exit against a baseline so the saving can be defended later.
Decide the end state first
A corporate communications channel closes for one of three reasons: the project finished, the platform is being consolidated, or a lawyer needs the content preserved. Each reason points to a different end state, and that choice drives every later task.
| End state | What happens to the content | Common trigger |
|---|---|---|
| Deletion | Items removed once the retention period closes | Finished project, no audit interest |
| Read-only archive | Posting stops, search and export continue | Compliance, HR or dispute hold |
| Migration | Content and membership move to a successor | Platform consolidation |
Pick one and write it down. A channel that is half closed, still visible but unmonitored, is the worst outcome for records.
The channel decommissioning checklist
- Name a record owner and a deputy, with contact details in the exit plan.
- Confirm the retention period with legal, and with your information governance lead if the channel holds personal data.
- Inventory every record typeposts, threads, direct messages, files, pinned items, membership lists, bots and webhooks.
- Test one export and read it back before you delete anything.
- Tell members when posting stops and where the successor channel lives.
- Log the decision, the date, the approver and the deletion certificate.
Migrating an internal comms channel in five steps
- Freeze the channel, set a read-only banner and publish the closing date.
- Map source channels to targets one to one, because merging unrelated topics destroys context.
- Export posts, threads and files with the platform's own tools, such as Microsoft Purview eDiscovery for Microsoft 365 or Slack corporate export.
- Rebuild membership from the directory, and re-check guest accounts against your duties under the Data Protection Act 2018.
- Post a short note in the successor channel, pin it, and archive the old one with a pointer to the new home.
Records retention for comms channels
Retention follows the record, not the tool. A pinned policy announcement, a signed contract in a file tab and a direct message agreeing a price are three different records with three different lives.
| Record type | Where it should live next | Retention driver |
|---|---|---|
| Announcements and approvals | Records store with version history | Statutory filing support |
| Contracts and attachments | Document management with access controls | Contract and tax rules |
| Membership and access logs | Identity or HR system | Access audits |
| Decision threads and direct messages | Exported case file | Disputes and investigations |
Public authorities carry an extra duty. Records must stay retrievable so that requests can be answered, which is why the Freedom of Information Act 2000 sits behind the section 46 records management code.
Example: closing a project channel after an acquisition
Suppose a UK engineering firm buys a smaller rival and merges both Teams tenants. The acquired team's channel holds eighteen months of pricing threads, two signed supplier contracts and a membership list with three external contractors.
The exit plan freezes the channel, exports threads and files to the acquirer's records library, moves contracts into the contract register, and removes the contractors once their access is no longer needed.
Because the buyer files accounts every year, those exports also need to support later disclosures, which fall under the accounts and reports provisions of the Companies Act 2006.
Costing the exit against a baseline
Closure costs money before it saves any. Licence seats, export tooling, staff hours and the records store all carry a price, and moving the same content into a paid archive changes the cost line rather than the total.
If you want to claim the move paid off, write the counterfactual first so the saving is measured against something real.
If the destination platform is still open, the comparison of Teams and Slack records examines dated channel records, membership boundaries and untested areas before any trial.
A young company closing its first workspace needs the same discipline at a smaller scale, and the lean corporate communications plan sets out the Companies House facts and a five-step template.
Common questions
How long should we keep exported channel records?
Your retention schedule decides. Accounting records carry their own statutory minimum periods, and personal data should not be kept longer than the purpose requires.
What happens to direct messages when a channel closes?
Treat them as records when they carry decisions. Export the relevant threads into a case file and delete the rest under the platform's retention policy.
Who signs off a channel closure?
The record owner drafts the exit plan, legal or information governance confirms retention, and a named director approves. Keep that approval beside the export.
Can we hide the channel instead of closing it?
Hiding leaves content searchable but unmonitored and outside a retention decision. Archive it properly or delete it on schedule, then record which you chose.
