"we no longer support the v1 config schema"

[YuriVanZieks]

Hi !
I have been trying to learn how to use the tool but am stuck at the beginning of my tests, with this error whenever I do the command to execute :

!!ACTION REQUIRED!! we no longer support the v1 config schema...

I have the recommandation to use the following command by the cmd : devopsmigration.exe upgrade -c myconfig.json

All it does is create a configuration-update.json file, which I tried using, but same issue ...

I haven't seen this issue reported anywhere else, any ideas ?

[10:57:44 INF] [16.2.11] Start Time: 08/11/2025 10:57:44
[10:57:44 INF] [16.2.11] Running with settings: {"ConfigFile": "c:\\temp\\configuration.json", "DisableTelemetry": false, "DebugTrace": false, "skipVersionCheck": false, "$type": "ExecuteMigrationCommandSettings"}
[10:57:44 INF] [16.2.11] OSVersion: Microsoft Windows NT 6.2.9200.0
[10:57:44 INF] [16.2.11] Version (Assembly): 16.2.11
[10:57:44 INF] [16.2.11] Logpath: C:\Users\REISST\AppData\Local\Microsoft\WinGet\Packages\nkdAgility.AzureDevOpsMigrationTools_Microsoft.Winget.Source_8wekyb3d8bbwe\logs\20250811105736
[10:57:50 INF] [16.2.11] Verion Info:
[10:57:50 INF] [16.2.11]      Running: 16.2.11.0
[10:57:50 INF] [16.2.11]      Installed: 16.2.11
[10:57:50 INF] [16.2.11]      Available: 16.2.11

[10:57:50 INF] [16.2.11] Azure DevOps Migration Tools [Object Model]
[10:57:50 INF] [16.2.11] unknown
[10:57:50 INF] [16.2.11] naked Agility with Martin Hinshelwood
[10:57:50 INF] [16.2.11] ===============================================================================
[10:57:50 FTL] [16.2.11] Config is Invalid

!!ACTION REQUIRED!! we no longer support the v1 config schema...

You are using a deprecated version of the configuration, please update to the latest version.
You can use devopsmigration.exe upgrade -c myconfig.json to atempt to update it.This is best effort and may not bring across all of your property values as it will only create and map valid ones with
the same name.
We have made lots of architectural changes, refactors, and renames. Not all of them are mapped...


Exiting...
[10:57:50 INF] [16.2.11] Command ExecuteMigrationCommand completed in 00:00:05.9341528

[MrHinsh]

You would need to provide your config for us to have any hope of understanding what might be the issue.

[YuriVanZieks]

configuration.json
Is this the file needed ?

Thanks a lot

Steven

[MrHinsh]

The config you provided works on my machine!

[YuriVanZieks]

Thanks for trying, then I suppose there is an issue somwhere else, any thoughts on what that would be ?

(still tried it once again, using the file I uploaded to you ... same result)

[YuriVanZieks]

There seems to be an error with that version.

The .exe file does not work when launched manually, and the winget command does not work either, saying no package could be found. Might not have been approved yet, tho

Exception non gérée : System.IO.FileLoadException: Impossible de charger le fichier ou l'assembly 'file:///C:\Users\REISST\Downloads\MigrationTools-16.3.0-Preview.1\MigrationTools.Clients.TfsObjectModel.dll' ou une de ses dépendances. L'opération n'est pas prise en charge. (Exception de HRESULT : 0x80131515) ---> System.NotSupportedException: Tentative de chargement d'un assembly à partir d'un emplacement réseau qui aurait entraîné l'utilisation de l'assembly en mode Bac à sable (sandbox) dans les versions antérieures du .NET Framework. Cette version du .NET Framework n'activant pas la stratégie CAS par défaut, ce chargement peut être dangereux. Si ce chargement n'est pas destiné à utiliser l'assembly en mode Bac à sable (sandbox), activez le commutateur loadFromRemoteSources. Pour plus d'informations, consultez http://go.microsoft.com/fwlink/?LinkId=155569.
   --- Fin de la trace de la pile d'exception interne ---
   à System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   à System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
   à System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
   à System.Reflection.Assembly.LoadFrom(String assemblyFile)
   à VstsSyncMigrator.ConsoleApp.Program.<Main>d__0.MoveNext() dans D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.ConsoleFull\Program.cs:ligne 25
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
   à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   à System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   à VstsSyncMigrator.ConsoleApp.Program.<Main>(String[] args)

[MrHinsh]

You need to unblock the file before you can unpack it.

Tip: You may need to 'unlock' the downloaded archive. Right-click → Properties → Unblock before extracting.

https://devopsmigration.io/download/

[YuriVanZieks]

Of course, my bad, forgot that part.
It seems to work :) I still have an access token issue but that's another problem that I have to dive in now, but the initial problem is solved on my end.

Do you think it was all due to the version causing problems ? Still, thanks a lot for the help !

[MrHinsh]

No, I think I just had some bad detection logic and it was running home to the "v1" issue... I replaced all that logic.