Is it possible to migrate from Agile to Scrum based project about azure-devops-migration-tools HOT 10 CLOSED

Yes you can.

I do however recommend that you change the process in place rather than over the air. In TFS you can manipulate the process and massage it into the Scrum process.

https://nkdagility.com/upgrading-to-visual-studio-scrum-3-0-process-template-in-tfs-2013/

from azure-devops-migration-tools.

Kind of... Check: https://nkdagility.com/do-you-know-how-to-upgrade-a-process-template-but-still-keep-your-data-intact/

If you use option 7 then you can use the Bulk Update option in the tool to massage the data after...

#Rough Outline#

1. Create a hybrid Scrum template with all of the fields from the equivalent Agile items including your custom fields
2. Rename User Story to Product Backlog Item
3. Rename Issue to Impediment
4. Overwrite all of the Work Items with your hybrid template
5. Update the Process and Group configuration files
6. Now use the VstsMigrator field mapping system to move data from your Agile/Custom fields to wherever you want
7. Upload the vanilla Scrum Template
8. DONE

from azure-devops-migration-tools.

MrHinsh,

Are your comments above up to date?

Am I correct in thinking that with the latest version of the VSTSSyncMigrator tool we can use the WorkItemTypeDefinition and the FieldMaps - FieldValueMapConfig sections of the json configuration file to achieve the workitem migration and process template migration in flight?

I'm currently planning on migrating a project from TFS2017.4 Agile Template (vanilla) to VSTS Scrum Template and will be testing that process this week.

I'll post my findings and configuration file here later in the week if I'm successful so that others can benefit etc..

P.S. I've already completed a number of migrations for other projects (minus the template swap) with great success. Thanks to your efforts my boss calls me his TFS Ninja :).

from azure-devops-migration-tools.

already completed a

If possible please post your configuration file

from azure-devops-migration-tools.

If yiu are currently in TFS you should do an in-place change from Agile to Scrum. https://nkdagility.com/upgrading-your-process-template-from-msf-for-agile-4-to-visual-studio-scrum-2-x/

If you are in Azure DevOps you will need to change Project and do a live migration. That's super hard and you should hire an AzDev MVP to help you!

from azure-devops-migration-tools.

If yiu are currently in TFS you should do an in-place change from Agile to Scrum. https://nkdagility.com/upgrading-your-process-template-from-msf-for-agile-4-to-visual-studio-scrum-2-x/

If you are in Azure DevOps you will need to change Project and do a live migration. That's super hard and you should hire an AzDev MVP to help you!

I am doing a Migration From TFS 2017 to AzureDevops.
If I do "WorkItemTypeDefinition": {
"User story": "Product backlog item" that should work right?

Once Migrated we got to do field mappings.

All the rest of the WIT names are same like epic, Feature, task and bug.

Thanks for your reply

from azure-devops-migration-tools.

@prashanthbv12 Please open a new issue if you still have this problem.

from azure-devops-migration-tools.

2. Rename User Story to Product Backlog Item

Can you elaborate a bit more on how this is done exactly? Is this using the FieldValueMap?

from azure-devops-migration-tools.

It depends in the question. You can use witadmin.exe in TFS & Azure DevOps Server, but in Azure DevOps Services there is no way to rename a work item.

from azure-devops-migration-tools.

I didn't see the WorkItemTypeDefinition mapping element previously. I am going to give that a try. BTW ... thanks for the quick response on your website chat feature an making your tool available!

from azure-devops-migration-tools.