Retirement of Teams Wiki - everything you need to know

By Robert Dyjas on  • Edit this post

The article gathers everything about retirement of wiki functionality in Teams. Timeline, details, proactive actions.

In January 2023 Microsoft announced the retirement of wiki functionality in Teams. This article talks about everything you need to know to be prepared for it, when the time comes


Below are the more important information from the article:

  • Wiki migration tool is available in public preview
  • OneNote is the tool to replace wiki in channels
  • Loop is the new platform for meeting notes
  • There's a script available to estimate the impact of this change
  • Microsoft has plenty of learning materials about OneNote

If you want to know the details, keep reading. If you stop here, thanks for your short visit!


Wiki will be retired from Teams. We know that based on Microsoft's announcement published in the beginning of January:

Microsoft's announcement MC496248

If you want to check the announcement here is the link (requires admin account to access) Message Center entry MC496248. You can also read it on unofficial M365 Changelog (no account required).

When will wiki be retired from Teams?

The Message Center announcement doesn't specify any date when wiki will be completely removed. It only says what is going to happen with the next release of Teams wiki.

The changes announced already are:

  • Users will have an option to export their wiki content to OneNote notebooks in Teams standard channel (I write about private channels below)
  • Users will be able to continue to access and edit existing wikis but will not be able to create new wikis in Teams channels
  • Notes tabs powered by OneNote will be added by default when users create new channels

The changes are already available in public preview. The initial announcement mentioned mid-February as a start date. However, the rollout started closer to the end of March. There is no mention of the end date. If you have the EA (Early Access) indicator next to your profile picture (see below) you should see the new interface now.

Early Access indicator in Teams

The dates mentioned above apply to these two changes:

  • Users have an option to export their wiki content to OneNote notebooks in Teams standard channel
  • Users are able to continue to access and edit existing wikis but are not be able to create new wikis in Teams channels

There's one change with no specific date. The announcement mentions that soon Notes tabs powered by OneNote will be added by default when users create new channels.

What will change with Wiki tab?

At the first stage, the Teams application will suggest adding OneNote tab:

Top bar suggesting OneNote tab

The empty Wiki tab will not be locked yet. We will still be able to make some edits.

When we go to the page with existing content, we will see a different bar:

Top bar proposing to migrate to OneNote

That experience is now (as of April 2023) generally available.


The bars will be visible to users with rights to add or remove tab in a channel. For others, there will be no bar.

How will the migration process look like?

The yellow warning bar will be added to the top of wiki tab:

Warning bar at the top of wiki tab

The bar says:

Wiki tabs will go away in June 2023, you can export your content to a new Notes tab that will be created for this channel

Once we click the Get details button we'll be redirected to the next screen giving more information:

Details screen

The pop-up says:

What to expect when you export:

  • Each wiki page will be saved in as a separate page (in OneNote) in the Notes tab
  • Some changes to formatting such as font style and spacing may occur
  • We'll keep a read-only version of your content in the Wiki app for reference
  • In Notes, you can take notes and organize content for this channel

After using Export to Notes button we'll see the progress screen:

Progress screen

And then the confirmation screen:

Confirmation screen

After confirming with Finish we'll be redirected to the Notes tab. The tab is the default name for a OneNote tab in the channel.

Notes tab with migrated pages

The context pop-up says that each page from wiki was saved as a separate page in the section. The section name comes from the channel name. For details see To which section is the wiki migrated?.

Next pop-up will suggest to delete the Wiki tab:

Pop-up suggesting deletion of Wiki tab


If we click Wiki tab after the migration, it will show the read-only snapshot of the wiki at the moment of migration. The tab will not reflect any changes made afterwards.

To which section is the wiki migrated?

Migration of wiki creates a section named after the channel. The pages contain the wiki name and page title separated by underscore. For example, Getting started from Wiki in test2 channel will land under test2 section in Notes. The page will be named Wiki_Getting started:

Structure of migrated wiki pages in Notes


For some reason, pages under General channel with only one wiki will not have Wiki_ added to the page name in Notes:

No prefix for General channel wiki

How are multiple wikis migrated?

Our channel can have multiple wiki tabs. All wikis will be migrated to the same section in Notes. They will have different prefixes added to page name. With this, we'll distinguish them easily:

Different prefixes for different wiki tabs

What are the known issues with migration?

There is no official list of known issues. However, based on my experience we might see one of the cases described below. The remediation is to migrate the broken content manually.

Pages title not appearing correctly

It happened to me once that page titles didn't populate correctly. At the page list all were shown as Untitled Page while the title on the page itself was correct:

All pages shown as untitled

Broken pages

I saw the issue happening once when the title had a slash character /. When I tried to open the page in OneNote it displayed the error message:

Error message indicating sync error

Waiting multiple days didn't fix the issue. However, I was not able to reproduce it later. The page I migrated later had no issue:

Page with slashes migrated correctly

Duplicated pages

From time to time, when we close the last modal with the top-right X button, we might be able to run the migration once again:

Closing the model prematurely

As a result, we'll see the duplicated pages in Notes:

Duplicated pages in Notes

Incorrect section linked

When the channel has the brackets, Notes tab might lead to incorrect section in the notebook. I didn't find any pattern how it works.

In some cases, the first section in the notebook was linked. In others, the random section.

Will private channel wiki be retired?

Yes, wiki tab will be retired from private channels, too. There is an important difference in terms of the migration. According to Export a wiki to a OneNote notebook:

Private channel wikis will also be deprecated. Unlike with standard channels, there will be no migration experience for private channels, so users will need to copy-paste the content into OneNote manually.

Will meeting notes be retired?

Although meeting notes are based on the wiki functionality, the announcement doesn't cover it at all.

If we dig more, we can find something about the meeting notes in the roadmap entry 101509. The entry initially said:

Every Teams meeting now comes with a collaborative OneNote canvas. Create notes from the Teams calendar or during a meeting. You can easily recall your notes and manage your tasks directly from OneNote.

That was a little bit unclear but now it's saying more (emphasis mine):

Collaborative notes allow meeting attendees to co-create and collaborate on their meeting agenda, notes, and action items. Since Collaborative notes are a Loop component, it is always in sync regardless of how many places they live in. Assigned Tasks in Collaborative notes automatically sync with ToDo & Planner.

If you want to read more about the Microsoft Loop, here are some useful resources:

What's the difference between wiki and OneNote?

OneNote can be considered wiki on steroids. Wiki was always meant to be a simple text editor. The main things that are making wiki less usable than OneNote are:

  • Cannot be used outside of Teams
  • Limited formatting options
  • No full-text search
  • No recycle bin
  • No offline use
  • Poorly designed version history

If you want to read more, I recommend the following articles: Don't use Teams wiki – Vesa Nopanen and What's wrong with Microsoft Teams built-in wiki? Five built-in wiki limitations that you should know.

What's the experience for Teams 2.0?

As new Teams client doesn't support Wiki app it's not suitable for Wiki migration. In fact, new client doesn't show Wiki tab at all:

Difference between standard and new client

The new experience is far from ideal - it should at least indicate there is a Wiki app available.

Upcoming OneNote improvements

On the other hand, OneNote got a nice refresh in 2022. There are more improvements coming, such as new navigation options, dictating notes.

If you want to be up-to-date, here's the OneNote section of the M365 roadmap.

Can I export list of wiki users in an organization?

Now when we know what to expect, let's think how many users will be affected by this change. Are our users using wiki at all? How to check this?

Tony Redmond has written an excellent guide describing How to Find Teams Channels With a Wiki Tab.

For meeting notes, the only discovery way I can think of is via eDiscovery. Knowing that meeting notes are kept under OneDrive > Microsoft Teams Data > Wiki, we'd need to find the people with such folder existing. But that only covers people, who created the notes, not talking about the ones reading them.

Can I remove wiki tab programatically?

Removing wiki tab is possible using Microsoft Graph. Andres Bohren has written a guide showing this: How to remove Microsoft Teams wiki tab with Microsoft Graph.


Although the article is in German, browser's built-in translation works just fine. If you want, you can also go directly to the translated article.

How can I prepare for Teams wiki retirement?

The wiki retirement in inevitable. How to better prepare for it? I think the most important part is about education - promote OneNote across the organization as it'll be our new friend in the upcoming days.

Microsoft has some good resources you can use to get people familiar with OneNote: OneNote help & learning and OneNote video training.

Next part is discovery - find out who uses wiki and prepare a targeted communication about migrating to OneNote. Check the section Can we export list of wiki users in an organization to find out how to do that.

Last, but not least - stay in the loop. Get back to this post frequently for updates. Keep checking the Message Center and M365 Roadmap. Make sure you don't miss important updates.

You can also bookmark this support article Export a wiki to a OneNote notebook. It seems to have a lot of useful information (including timeline). Such information is not mentioned anywhere else.


There's a lot of things uncovered for the Teams wiki retirement. However, there are things we can already do to be prepared.

Once we're prepared, we only can hope that Microsoft provides a nice transition experience for the discovery, migration and decommission of the wiki.

Bye, bye, wiki! You'll be missed (but only by some of us) 😉