Fields in target not migrated?

[Musket519]

I made a post about this earlier but Im remaking it with some new information. I have work items that have already been migrated but the tool didnt grab all of the fields despite them being mapped in the config file. Specifically this is what the tool will do on one of these work items:

It finds 4 revisions but doesnt add any custom fields at all.

Then I go into and manually change a field (for example, setting the effort field to 1) and then run the tool again with no changes made to the config at all. This is what it does:

It now finds 7 revisions and the custom fields are populated. I dont have the ability to manually change a field in each of the thousands of work items I need to move. Im not sure whats causing this. Any help?

[MrHinsh]

The tool iterates through all of the fields on the source and copies them to the identical field on the target. It does not miss fields that exist or are editable.

If that field does not exist at the time of the migration, then rerunning will not populate it, as all of the revisions have already been done, and the migration is based on revisions and not migrations.

You can either:

1. Delete the migrated work items and start again with all of the custom fields existing on both sides, or mapped with a fieldmap
2. Run the WorkItemPostProcessingContext that will create a new revision on the target for all fields.

Both these options will bring across the fields that you missed from the target process or the config prior to the initial migration run.