Can I Filter Work Items that already exist in the Target?

[bldcm]

We have many migrations in the 10s of thousands of work items and a few in the 100s of thousands of work items. If a failure occurs it seems I have to start all over again.

Has anyone tried setting the ORDER of the query to the system ID so that if it fails on say work item 10,000 the config file can be updated to select those with IDs 10,001 or higher. Sorting with the system ID going from lower to higher would essentially guarantee not work items are skipped.

Has anyone tried this?

[MrHinsh]

The FilterWorkItemsThatAlreadyExistInTarget setting on TfsWorkItemMigrationProcessor serves this purpose. When enabled it will:

1. Load all work items from source
2. Load all work items matching the same query from target
3. Strip work item revisions from the run that already exist.

Without this enabled it will iterate through and check every work item. With it enabled it will just check the "rev" value matches...