Recommendations for multiple migration runs?

Question

Could anyone provide any best practices about multiple migration runs? Moving from TFS 2017.3.1 to Azure DevOps Service. Dealing with a fair number of work items (32k). Of course, TSTU throttling is making the run take a long time, so I was thinking of pushing what I could up front, then a second pass to pick up the new work items since the first big push. So...enabling UpdateSourceReflectedId would set the ReflectedWorkItemId on the source items that have already been migrated. But what happens if someone changes a work item that has already been pushed? Would the history delta get picked up? How is that typically resolved...I was thinking maybe a Querybit like: ReflectedWorkItemId <> '' and ChangedDate > (last run time), but is that necessary? Those already exist on target...would ReplayRevisions pick up only the missing changes? TIA...

Answer 1

I usually do the following for large runs:

• Open work items edited in last 90 days
• Closed work items edited in last 90 days
• open out to more days in chunks

The important thing to note is that links are created only when both ends of the link exist.

After a long run you can then rerun "edited in last month" to bring any changes a cross.

Changes to avoid in the Source:

• changing work item type
• moving work item between team project

We handle these, but loosly.