Couple of issues generated during the migration for quite many projects in our organization.

[dafidov]

Hello.
I'm a part of the team where are day to day activity is migrating projects from different parts of our organization to new structure on Azure DevOps.
We are migrating data from TFS on Prem to Azure DevOps and also we are migrating different projects from Different organizations already existing on Azure DevOps to new consolidated structure.
During those migrations we have occurred several times similar issues which I will list below and would like to ask you if there is any solution or if any new development will happened in near new version of the tool to support to sort them out.
As we are in that process and we assume it will take several months in future it is crucial for us to have them sorted out as the amount of projects and sizes of them is huge.

1.a. Dates revision issue: 'Dates must be increasing with each revision'; 1st attempt full history migration failed; but 2nd try query was shortened to created after 01.01.2022, migration was successful;
b. Dates revision issue: 'System.Web.Services.Protocols.SoapException: VS402625: Dates must be increasing with each revision'
2. Test Plan issue 'Microsoft.TeamFoundation.TeamFoundationServiceUnavailableException: TF400324: Azure DevOps services are not available from server': 53 valid Test Plans at source, bulk migration failed; individual migration 50 Test Plans was successful, but some Test Suits and Test Cases were not linked; some test suit all Test Cases were migrated separately and successfully;
3. Some revisions are missing, when a work item is moved from one project to another;
4. Latest revisions missing when an area path existing in the past has been deleted and a workitem was moved from one project to another;
5. Empty record produced by nkdagilty during migration, without even Title, if a workitem type has been changed in the past;
6. During migration in some cases we occurred: Removed Areapath: Workitem type change:

Thank you in advance for taking a look on them and advising how this issues can be sorted out and when and if there are any plans to improve the tool to eliminate this issues in future version.

[MrHinsh]

What version are you using?

1. This was resolved in the latest version of the code. If it's still happening, we need to debug to understand the order and what we can do to fix it. We added a rewrite for the history when dates have duplicates that adjusts any duplicates by 1 until there are no duplicates. If you switch the logs to Debug you will see both the pre-rewrite and post-rewrite dates listed.
2. Where are you running the tool? We recommend running as close to the target (an Azure VM) as possible. Does re-running resolve this?
3. What do you have SkipRevisionWithInvalidIterationPath and SkipRevisionWithInvalidAreaPath set to?
4. See 3
5. I have seen this occasionally and have an open bug [Bug] Sometimes the tool creates Empty workitems - no title, and set to new... no fields mapped #1961
6. If you have old work item types that no longer exist then they should be mapped to existing ones (we probably need a validator for that)

These are a lot of very specific issues that may need to be debugged on you environment in Visual Studio to resolve. I'm starting a migration of 80k work items across 50 projects Monday so will likely hit most of these ;) myself and can debug.

[MrHinsh]

Note, we do have a validator for 6 and it was added 71 days ago.

Which version are you using?

[dafidov]

Hello. for migrating test cases I use 13.1.0 for migrating other work items 15.0.0. Based on your feedback I will re run migration using the latest version of the tool with fixes to verify if there will be better result. Will keep you posted.

[dafidov]

Migration tool is run on local machine not on Azure VM so maybe that will sort out additional issues will check it too.

[dafidov]

Hello @MrHinsh we have re run the migration with version v15.0.5, still haveing the issue with "'System.Web.Services.Protocols.SoapException: VS402625:"

It was run with SkipRevisionWithInvalidIterationPath and SkipRevisionWithInvalidAreaPath flag set as False.
We can test it with flags set to true but then we could loos some historical revisions.

The same parameter SkipRevisionWithInvalidIterationPath and SkipRevisionWithInvalidAreaPath flag set as False was when we occurred that some revisions was skipped.

Have you occurred same behaviors like we when you was running your last migration?
Any possible solutions?
Thank you in advance for your feedback!

[MrHinsh]

#2067

[MrHinsh]

I'm integrating a PR into Preview.

You would need to uninstall the prod version an try the preview after it has been approved...

[dafidov]

Looks like there is somethig wrong with System.RevisedDate (Revised Date) | "9999-01-01T00:00:00.0000000Z"

This specific one was ADO to ADO but if I remember properly originally first items was migrated from Jira to ADO and the malformed data format could come from that original migration.

[MrHinsh]

@dafidov Im working with the Azure DevOps team to isolate this.

Please share account name, identity under which the tool is running and approx. date time in UTC. They can try to look up any matches in their telemetry using that. I can see from the logs the time, but not the date.

martin[at/]nkdagility[dot//]com

[dafidov]

Please share account name, identity under which the tool is running and approx. date time in UTC. They can try to look up any matches in their telemetry using that. I can see from the logs the time, but not the date.

Hello.
Email sent with all details.