Forum Discussion
Now in public preview: Future of wiki and Notes in Teams
Description
We are announcing that Wiki's will be retired from Teams starting January 2024. We are offering note taking capabilities within Teams channels using the included OneNote notebook provided for each team.
With this release, users have an option to export their wiki content to OneNote notebooks in Teams standard channel. After exporting users can go to the Notes tab to collaborate using OneNote in channels while Wiki is read only after export.
Why are we moving to a new note taking experience?
- This new functionality provides an improved note taking experience over Wiki. Some of the improvements are:
- Easy collaboration across the team
- View all channel notes in a team in one place organized within single notebook
- Rich editing with typing, ink annotations, highlighting, file attachments, etc.
- Easy recall & search for channel notes within OneNote
Plan to enable OneNote Notes in Teams channel and retire Wiki
- Users now have the option to export their Wiki content to OneNote Notebooks or they can continue to read/write their existing Wiki. Post export users can continue to collaborate in Notes tab in channels and have a copy of older Wiki content available for reference. When Wikis are exported each page in Wiki will appear as a page in OneNote Notebook section. Users can’t create new Wikis in new channel experience; for note taking we suggest using OneNote.
- For new channels Notes will be available as default tab soon. For now, user can create Notes tab manually using add a tab option.
We request you to try out the new Wiki export experience and share your feedback.
How to try out the experience
- In Teams, go to whatever channel has the wiki you want to export.
- In the Wiki tab, select Get details > Export to Notes > Finish.
- Go to the Notes tab to access your content.
Read more about the change here - https://support.microsoft.com/en-us/office/export-a-wiki-to-a-onenote-notebook-8cd8ab0c-2314-42b0-a1d0-5c6c4c5e1547?storagetype=stage#bkmk_wikideprecationfaq
Flighting status
Available in public preview
How to enable
This config change is available to everyone.
Supported clients and platforms
|
Windows |
macOS |
iOS |
Android |
Linux |
Chrome |
Firefox |
Safari |
Edge |
|
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
How does this feature impact the existing experience?
Users can continue to access their Wiki as is, no change in existing content until general availability when Wiki content will retire.
Known issues
None
Known limitations
- Post export users may see some formatting change and dark mode is not supported
- Export is only supported from standard channels, from Private channels user need to manually copy & move content.
Enable your Teams client for the public preview
- First, IT admins need to set an update policy that turns on Show preview features. Learn how at https://docs.microsoft.com/MicrosoftTeams/public-preview-doc-updates.
- Users then choose to join the public preview individually. See https://support.microsoft.com/office/get-early-access-to-new-teams-features-a6e387fe-1cad-4f90-ad78-1a311c77b36d for instructions.
Send us your feedback
Got feedback on features in the public preview or other areas of Teams? Let us know straight from Teams via Help > Give feedback. This is on the bottom left of the your client.
Thank you,
Preview Team
Quality & Customer Obsession, Microsoft Teams
76 Replies
Instead of replacing Wiki with OneNote "Notes", it would be a better idea, and make much more sense, to replace Wiki with a modern Loop Workspace.
- This is insanity. What makes this even worse is that, how bad the export to notes script may be, IT ISN'T EVEN AVAILABLE FOR PRIVATE WIKI CHANNELS.
So screw you, teams with private wiki pages, here's hours if not days of painstaking manual copypaste labor to move, reformat and reorder content from a tried-and-true Wiki format to a slow, unwieldy, almost unsearchable, non-automatable nonsensical tool like Notes. Should have had those channels public all along because we can't be bothered to make it so that you can convert between public and private, but welp, can't help you now, buhbye!
This can't be real. It just can't be real.- Bouke, MS doesn't design products. The shoot from the hip and then react from product feedback. It's the most offensive and convoluted way to design a product and once you understand this lack of design IS their design methodology, this it makes a lot of sense why their tools are so clunky, difficult and frustrating.
- You wrote that users could "try out the experience" by exporting Wiki to Notes. So I did that, but now the Wiki is read only and refers to Notes, which I don't want to use because it doesn't provide the list of tasks in the left pane where a use can navigate tasks. How do I unlock Wiki so I can continue to use until we decide what we're using next? Or How do I get a list of tasks in Notes?
- Converting to a Loop workspace would be much better the OneNote.
- I have to agree with most people here that OneNote is in no way a replacement for Wiki. Please keep Wiki alive.
Jan_Steberl the wiki feature as been very positive as it is a simple and powerful way to let users access data in a structured way. I am sure the change would 'improve note taking experience over Wiki', however we didn't select a wiki to try to take better notes. I echo the comments that removing the wiki impacts what our team has built out over the last year with no understandable upside. I hope you will reconsider keeping the WIKI functionality.
Jan_Steberl
This is a horrible idea. It would make way more sense to transition Teams Wikis to Microsoft's new https://loop.microsoft.com/ tool (which is like Notion).
OneNote is not analogous to Wikis in use; unlike OneNote, Wikis are not used to collect notes in real-time, Wikis are used to organize existing, structured information and make it discoverable. While the Teams Wiki has always been a bad implementation, at least it is structured.- It’s terrible that after you removed Wiki from SharePoint, you are now removing it from Teams. Without replacement. In M365, there is no way to store structured content such as knowledge base or wiki pages. OneNote is great for notes, Modern SharePoint pages are great as a welcome page, but both are unusable as a wiki or knowledge base library. The only option is to switch to competitors such as Confluence.
I've submitted the following feedback:
Re: Retiring Wiki in place of Notes.
This is horrendous and nonsensical. The wiki is agile, to the point, and freakin awesome. Notes is an absolute clusterfck and serves an entirely different function than a wiki. If I've wanted to use Notes, I would have been using that - in some cases, I do.
Regardless of how I feel about it, I've just exported a Team Wiki to Notes and all the pages say Untitled Page without the ability to edit the name of the page. So, that was pointless.
That's going to be a FOR THE LOVE OF THE FEW THINGS MICROSOFT HAS GOTTEN RIGHT... HELL NO from me on this topic.
Anthony-123, I had the same issue and noticed a "auto refresh" quick fix. If you click in the title of the page (title above the date) enter a space or delete a space it refreshes with the imported name of the page. Lots of work, but it was helpful in one of my smaller notebooks. Good Luck.
- Is this tool to move Wiki pages to OneNote still in active development? It appears the parsing script fails to recognize Wiki formatting and the best option is to manually rebuild each page individually. Where can we find updates on this parsing tool? I'm going to wait until MS fixes the bug before I lose two weeks of work due to MS's complete incompetence and negligence here. What a productivity tool!
