Microsoft Teams Wiki Replacement: What to Do After Retirement

TL;DR. Microsoft retired Teams Wiki and closed the OneNote export in February 2024. If your team did not export before then, recover the .mht files and images from SharePoint → Site contents → Teams Wiki Data. Decide what deserves to survive, then pick a destination — Teams-native if it must live in Teams, standalone if the documentation matters more than the tab.

Every so often a vendor retires a feature and discovers that "retire" is a word with feelings attached. The Microsoft Teams wiki is the current example. It was never the best wiki anyone had used. It was the one that was already there, in the tab, next to the conversation — and being already there is most of what a wiki needs to be, which is why its removal landed harder than the feature's quality suggested it would.

So: you need a Microsoft Teams wiki replacement, and you probably need it for content you did not realise you had. This post covers what actually happened, how to get your pages out, what each option is genuinely good at, and the part where we tell you when we are the wrong answer.

What actually happened, in order

The retirement ran in stages rather than as one switch, which is why different people in the same company have different memories of it.

Stage	What changed
2023	New wikis were blocked; existing standard-channel wikis could still be edited and exported to OneNote
Early October 2023	Channel Wiki tabs stopped being supported, but the Wiki app and OneNote export remained temporarily available
February 2024	Wiki tabs, the Wiki app, and the OneNote export became inaccessible; GCC, GCCH, and DoD followed in April 2024

The retirement did not automatically move every wiki into OneNote. The export only created a OneNote copy for teams that ran it before the final stage. For everyone else, Microsoft's remaining recovery route is the channel's SharePoint site: the Teams Wiki Data folder contains an .mht file and images to download.

The practical read is simple. If nobody can point to a OneNote copy, recover the SharePoint files now. A file you have downloaded is a backup. A retired tab that used to show it is a memory.

Microsoft's answer changed with the timeline

During the retirement window, OneNote was Microsoft's migration target for standard-channel notes. The official retirement page still documents how that export mapped each wiki tab to a OneNote section and each wiki page to a OneNote page. The same page's final timeline entry matters more now: from February 2024, the Wiki tab, Wiki app, and export are no longer accessible.

SharePoint is now the recovery route. It holds the underlying .mht file and images under Teams Wiki Data. That is not a modern SharePoint page and it is not a ready-made replacement. It is the copy you recover before rebuilding the content somewhere else.

Once recovered, the shape question returns. OneNote is a good notebook. SharePoint pages are a reasonable publishing surface. A wiki is a tree of pages with search scoped to that tree, permissions that follow it, and a history a reviewer can read. If your old wiki was meeting notes, a OneNote copy may be enough. If it was runbooks, onboarding, and the answers new joiners need in week one, you are going to feel the missing tree.

Recover the content before you choose anything

The most common mistake is picking a destination before securing the source. The OneNote export deadline has already passed; recovery now starts in SharePoint.

1. Check whether the old export already ran. Open the channel's Notes tab. If the wiki appears as OneNote sections and pages, verify the content and back up the notebook.
2. Recover an unexported standard-channel wiki. Open the channel's SharePoint site, select Site contents, open Teams Wiki Data, then open the channel folder. Download the .mht file and its images.
3. Audit private channels separately. Microsoft never provided the OneNote migration experience for them. Check the private channel's own SharePoint site for Teams Wiki Data; involve your Microsoft 365 administrator if the files are not visible.
4. Keep the raw recovery copy. Convert a duplicate, not the only .mht file you have. Migration tools have a charming habit of revealing their interpretation of "preserve formatting" after the source has been tidied away.

Then do the part everyone skips: decide what deserves to survive. A long-running wiki usually contains meeting notes nobody has reopened since the meeting. Moving those costs real hours and buys nothing. The migration is the one moment when deleting is cheap, and the moment passes.

What to actually look for in a replacement

Four questions, in the order that matters:

• Does it need to live inside Teams? If the honest answer is yes — your team does not open other tabs, and adoption is the whole risk — that constraint narrows the field to Teams-native apps and you should weight it above everything else.
• Is the content notes or documentation? Notes want a notebook. Documentation wants a page tree, scoped search, and version history.
• Can you get the content out again? You are in this post because a vendor retired a feature. Ask the next one for its export before you ask for its feature list.
• How fast is it? A wiki people wait for is a wiki people stop opening. The two things every wiki gets wrong are the same two things — waiting and clicking around — and they compound into the same outcome, which is a team that asks a coworker instead.

The options, honestly

Option	Best when	The catch
OneNote	The old export already ran, or the wiki was mostly notes	No automatic export now; no wiki-style page tree
SharePoint pages	You will rebuild polished handbook content inside existing governance	The recovered .mht is source material, not a finished page
Teams-native wikis (Perfect Wiki, Sprocket Orbit)	Living inside Teams is non-negotiable	You are buying the tab as much as the wiki
Standalone wikis (Confluence, Notion, Raccoon Page)	Documentation is the point	One more tab; .mht or OneNote conversion is manual

There is no wrong column here, only a wrong match. The team that buys a standalone wiki because it reviewed better, then discovers nobody opens it because it is not in Teams, has made an expensive mistake that no feature list predicted.

Where we fit, and where we do not

Raccoon Page is a standalone wiki. Sub-second loads. Keyboard-first — a command palette, slash commands, and the mouse doing nothing in particular. Spaces, labels, version history with one-click revert, and search that returns the answer rather than a list of places the answer might be.

Now the part that matters more for your decision.

We do not import from Microsoft Teams or OneNote. There is no direct Teams or OneNote importer. Coming to Raccoon Page from a retired Teams wiki is manual work: recover the .mht files from SharePoint, then convert the pages worth keeping to Markdown or .docx before importing them individually. The Word import path reads .docx after conversion; it does not read .mht, Teams, or OneNote data. We would rather write that sentence than sell you a migration we cannot perform.

And if living inside Teams is the requirement, we are the wrong answer. Not a soft wrong — an actual wrong. Perfect Wiki and Sprocket Orbit install from the Teams Store and live in the tab, and if your team's entire working surface is Teams, that constraint should beat every other consideration on the list. A three-person team that already has OneNote and a working habit does not need to buy anything either. Our Free tier is three users, one space, 50 pages, no card — which is the honest recommendation for a small team, and it is also us telling you not to spend money.

Where we are the right answer: the documentation outlived the tool, the team is technical, and finding the page has become the daily problem. That is the same shape as leaving Confluence and the same shape as the SharePoint alternatives conversation — different vendor, identical symptom.

On the way out, whatever you pick: check the export first. Ours is per-space zip in Obsidian-compatible Markdown, attachments included, on every plan — you can read about getting your data back out before you put any in, which is the correct order to read those two pages in. Lord Circuitrix once issued a one-line infrastructure decree — "Provision a Postgres container in case someone builds something" — two quarters before anyone needed it, and nobody asked why. Foresight is cheaper than a migration. Microsoft's users just found that out the expensive way.

Things people actually ask

What replaced the Microsoft Teams wiki? Microsoft recommended OneNote during the retirement, but it did not automatically move every wiki. The OneNote export ended when the Wiki tab and app became inaccessible in February 2024. Content that was not exported must now be recovered as .mht files and images from the channel's SharePoint site.

Can I still access my old Teams wiki content? Not through the retired Wiki tab. Microsoft says to open the channel's SharePoint site, select Site contents, open Teams Wiki Data and the channel folder, then download the .mht file and its images. If your team completed the old export before retirement, check the channel's Notes tab for the OneNote copy.

How do I export a Teams wiki to OneNote? You cannot start that export now. Microsoft removed access to the Wiki tab, Wiki app, and OneNote export in February 2024 for commercial tenants and April 2024 for GCC, GCCH, and DoD. Recover unexported content from SharePoint instead; only teams that ran Export to Notes before retirement already have the OneNote copy.

What happens to wikis in private channels? Microsoft never provided the OneNote migration experience for private-channel wikis. Check the private channel's own SharePoint site for Teams Wiki Data and recover the available .mht files and images. The conversion into a new wiki is manual; involve your Microsoft 365 administrator if the files are not visible.

Is OneNote a good wiki replacement? It is a good notebook. It handles freeform notes, handwriting, and clipping well, and it is already licensed. It is weaker at the things a wiki does: a real page hierarchy, search scoped to one body of knowledge, page-level permissions, and a change history a reviewer can read. If your wiki was mostly meeting notes, OneNote is fine. If it was runbooks and onboarding, it will feel thin.

Do I have to move to a Microsoft tool? No. The recovered .mht files and images are source material you can rebuild in OneNote, SharePoint, a Teams-native third-party wiki, or a standalone wiki. Choose Teams-native when adoption depends on the tab; choose standalone when documentation structure and retrieval matter more. Our import hub lists the formats we read, and Teams is not among them.

Does Raccoon Page import from Microsoft Teams or OneNote? No. There is no direct Teams or OneNote importer. Recover the .mht files from SharePoint, then convert the pages you want to keep to Markdown or .docx before importing them individually. The Word import path reads .docx after conversion; it does not read .mht, Teams, or OneNote data. The recovery and conversion are manual.

How long should a Teams wiki migration take? There is no reliable one-click estimate now that the export has closed. Time depends on how many channel folders you must recover, how cleanly the .mht files convert, and how much content you discard. Inventory and recover first, prune second, then estimate the rebuild from the pages that remain.

---

The Teams wiki was not a great wiki. It was a present wiki, and presence beat quality for about six years. Whatever you replace it with, the test is the same one it passed and the same one it eventually failed: will your team open it on a Tuesday, and will it answer before they give up and ask someone. Recover first, prune hard, then pick. And check the new one's export button before you need it — the last tool did not come with a warning either.