title | titleSuffix | description | ms.custom | ms.subservice | ms.assetid | ms.author | author | ms.topic | ms.reviewer | monikerRange | ms.date |
---|---|---|---|---|---|---|---|---|---|---|---|
Migrate wiki extension pages in Azure DevOps |
Azure DevOps |
Migrate wiki pages created using the Marketplace extension to the Azure DevOps Wiki. |
wiki, devdivchpfy22 |
azure-devops-wiki |
535245F2-6227-410C-B91D-559FA509D81B |
chcomley |
chcomley |
conceptual |
gopinach |
<= azure-devops |
03/27/2025 |
[!INCLUDE version-lt-eq-azure-devops]
Learn how to migrate pages created using the Wiki Marketplace extension to your team project wiki. You can save any wiki pages created using the Wiki Marketplace extension to a Git repo in your team project.
Note
The Wiki Marketplace extension is deprecated. Uninstall it after you migrate your pages.
[!INCLUDE wiki-prerequisites]
- Clone the vsts-wikiTools repository and compile the MigrateToVSTSWiki tool.
- Create, and then clone your Azure DevOps wiki.
- Move and commit all Markdown pages to your Azure DevOps wiki.
- Run the wiki migration tool, MigrateToVSTSWiki.exe
- When the wiki migration tool is complete, push the changes to the default main branch,
wikiMain
, of the Azure DevOps wiki repository.
-
Clone the vsts-wikiTools repository and compile the MigrateToVSTSWiki tool.
-
To generate the migration tool EXE, compile the project under the path
Tools/MigrateToVSTSWiki
. -
From a web browser, open your Azure DevOps team project and create your first wiki page.
-
To clone your wiki, get the URL. For more information, see Clone your wiki and edit wiki pages offline.
Name this clone location asLocationA
for this procedure. -
Clone your wiki repo using your IDE or the git clone command.
-
Clone the wiki extension repo. The wiki is mapped to a folder given to you during the wiki creation. You can confirm by going to the manage wiki option in the existing wiki, as shown in the following example. Your existing wiki pages are saved under the folder labeled
Root
.For example, you cloned the previously mentioned
sampleWiki
in the locationC:\wiki\sampleWiki*. The wiki pages are saved in the path *C:\wiki\sampleWiki\ _extensionWiki
Name this location as
LocationB
for this procedure. -
Create an empty folder in any path on your local machine, and name it
LocationC
for this procedure.In summary, the following locations are represented as follows:
- Location A = Azure DevOps Wiki repo
- Location B = Wiki extension repo
- Location C = Empty folder to run migration tool in
-
Open a command prompt as an administrator and run
MigrateToVSTSWiki.exe
. This tool copies the files from your existing wiki to the destination directory you provide. During copying, the tool converts the pages to be compliant with the Azure DevOps wiki.MigrateToVSTSWiki.exe /source:LocationB /destination:LocationC
For example:
E:\wiki\sampleWiki\_extensionWiki
is the folder in which the existing wiki files are presentE:\Temp\Wiki\New
is the empty folder into which the migrated files are to be copied.
-
Remove all the files from
LocationA
(if any) apart from the Git related files, such as.gitignore
, and so on. -
Copy all the files from
LocationC
and paste them intoLocationA
. -
Run
git add .
to stage all the newly added files inLocationA
for the commit. -
Run
git commit -m <commit message>
to commit the locally staged files. -
Run
git push origin wikiMain -f
to push the changes to the default branch of the Azure DevOps wiki.
After you migrate your wiki extension files to the Azure DevOps wiki, you're ready to uninstall the Wiki extension.
[!div class="nextstepaction"] Uninstall the Wiki extension
- Wiki page title naming conventions
- Clone and update wiki pages offline
- Source code for the wiki tools
- Git quickstart
This project adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact opencode@microsoft.com with any questions or comments.