Migration by import from RTC 4.x to 6.0.4 instead of upgrading (2 paasses)?
Is it a sound strategy to install a brand new instance of RTC (CLM) 6.0.4 with brand new DBs, then migrate data, via imports, from 4.x projects, to avoid a 2-steps upgrade ?
Accepted answer
During the upgrade, metadata (data structure) needs to be changed as well. The data that you export from a 4.0.x instance is not compatible with newer versions, so the proposed import part will not succeed.
Comments
Thx Don,
- What if we only import WI and a chosen snapshot of the versioned code?
- To me even just import the WI's :
- Import the process template for each project area? Are there meta data that would fail this import?
- Import the user base, don't remember if there is a current process for this, or we have to recreate it manually.
The only time I'm aware of IBM recommending the use of export/import is to "copy" a project area from one repository to another existing repository. The likelihood of at least some of your users wanting access to the data that is not brought over by export/import is sufficiently high that it is unlikely that IBM would ever recommend this as a way to shortcut a double upgrade.
Thx Geoffrey,
Comments
Liora Milbaum
Dec 25 '17, 7:06 a.m.A upgrade wrapper which executes the 2-steps upgrade might be useful.