RTC 4.x.x migration to RTC 6.0.2
3 answers
For the tool you mentioned in your question, do you mean https://jazz.net/wiki/bin/view/Main/BulkMoveWorkItemsBetweenProjectAreasInRTC4 ?
This tool is provided "as-is" and has to be deployed in the exact version it was built for.
The discussion here provide a workaround. But your new RTC server is 6.0.2 and it's not possible to connect to the server using a RTC 4.0.x client. So the tool can not be used in your case.
To migrate the work items, you may consider export the work items to a csv file and import the file to the new server. However you will lost the work item's history information.
Ernesto,
Someone does not 'migrate work items'.
Environments are migrated from one version to a newer one.
If you want to copy work items accross different RTC instances and different versions, the easiest way is exporting/importing via CSV.
Comments
There are no additional migration tools available to the public. There is an IBM Service that can potentially increase what can be copied, but as far as I know that requires the servers to be on the same version.
https://rsjazz.wordpress.com/2015/11/03/a-rtc-workitem-command-line-version-3-0/ provides some means that you can look at and use as starting point. It comes with code and you might have to.
If you just have the one RTC environment:
A) You could upgrade the entire environment, first to RTC 5 and then to 6.
If you're talking about a second RTC environment:
B) You could export them as XML and import them to the new environment, you'd lose traceability though
C) You could copy the environment and use DNS/host files to keep it running thinking it's the real one, upgrade through 5 to 6, then export the project with work items as a template and put it into the other environment.
A) You could upgrade the entire environment, first to RTC 5 and then to 6.
If you're talking about a second RTC environment:
B) You could export them as XML and import them to the new environment, you'd lose traceability though
C) You could copy the environment and use DNS/host files to keep it running thinking it's the real one, upgrade through 5 to 6, then export the project with work items as a template and put it into the other environment.