It's all about the answers!

Ask a question

Is there any recommended approach for migrating data from RQM standalone to CLM?


María Silvana González (50710) | asked Oct 07 '14, 1:12 p.m.
A project has been using an old version of RQM standalone, and storing the Defect work items in the RQM project area.
Now they face the need to migrate to CLM latest version and to use RQM integrated with RTC, but they want to keep the existing defects.
Is there any recommended approach for migrating data from RQM standalone to CLM?  In this case, the defects previously stored in RQM should be moved to RTC.

Thanks a lot in advance!
Silvana

Accepted answer


permanent link
Arun K Sriramaiah (3.2k12261) | answered Oct 08 '14, 8:16 a.m.

Hi Maria,

Please use the Interactive upgrade guide for upgrdation steps.( to latest version 5.0.1 link is attached below)

http://www-01.ibm.com/support/knowledgecenter/SSCP65_5.0.1/com.ibm.jazz.install.doc/topics/roadmap_clm_upgrade.html?lang=en

Regards,

Arun.

María Silvana González selected this answer as the correct answer

Comments
María Silvana González commented Oct 08 '14, 8:20 a.m.

Thank you very much!

One other answer



permanent link
N Z (3622026) | answered Oct 07 '14, 5:19 p.m.
Yes, there is recommended approach, but you haven't mentioned what version you are on, and what version you are going to.

This will dictate how the upgrade and migration is performed. 

Look up the documentation on the version you want to go to, there'll be an interactive upgrade guide which will give you specific instructions on what you need to do. If you are going from a very old version to a new version, it may have to be done in multiple steps.

Comments
María Silvana González commented Oct 08 '14, 8:08 a.m.

Hello!
Our stakeholder confirmed that both project areas, source and target, are now on version 4.0.6.
Could you please guide me on where to find the documentation so I can give them the information?
Thanks a lot in advance!
Silvana


Ara Masrof commented Oct 08 '14, 9:55 a.m.
JAZZ DEVELOPER

For clarification

If you were originally running RQM 2.x in a stand-alone environment and chose to manage your defects within RQM (i.e. never set up an external defect provider) then these defects will stay managed by RQM throughout the upgrade process. There is no migration path that will migrate internally managed RQM defects to RTC. After you have upgraded to 3.x/4.x/5.x you can use RTC to manage 'new' defects, but the ones from 2.x will still be managed locally by RQM 


Ara

Your answer


Register or to post your answer.