When you digest the guidance you quickly realize that the analysis of existing data, especially history, is an important link in the chain of a successful migration. Migrating history introduces complexity and more importantly time … if it took your organization 20 years to accumulate the history in terms of version control and work item artefacts, why should we expect the TFS Integration Platform to migrate everything in a 15min coffee break session?
- With Version Control data we can select a snapshot of state (history) to migrate. See I have just moved my VC content, now I want to sync from a specific snapshot … now what? or the new TFS Integration Platform – Configuration document that will ship as part of the product in the next drop.
- Options possible with VC today:
- Complete history migration (not recommended)
- Partial history migration
- Snapshot migration (the latest and greatest only)
- With Work Item data we do not have support for the snapshot feature as yet.
- Options possible with WIT today:
- Complete history migration, which includes the state changes.
- What we are asking in this post ...
- Should we support partial or snapshot migration for WIT as well?
Snapshots and selective history allows us to cherry pick what we feel is important and allows us to reduce the migration time of potentially lengthy migrations.
Therefore snapshots seem to be the way to go … or not?
Do you feel we need the feature supported for both WIT and VC, or is VC sufficient? Please add your candid feedback as a comment.