Copying Source Control data into a new Project Area

David, this usually requires the servers to be 'compatible' which menas the same version for a huge bunch of them.

Thanks for useful reply. But I currently have problem when I try to create Rep workspace for the components I wish to transfer.
I have eclipse client v602 connected to jazz_server_old (v602) and jazz_server_new(v606). All on same network and use same Active Dir
I duplicated stream from  jts_old and am trying to create a rep_workspace with "Use another repository" option. i.e. duplicate stream and its components are on "jts_old" and instructions in your link say I want repo workspace to be on "jts_new".
I get Error invoking remote service at https://jts_old:9443/ccm/
javax.net.ssl.SSLHandshakeException : Received fatal alert: handshake failure

Any help would be gratefully received.

I don't know if this is relevant to my problem described above but when I tried to use Eclipse client v606 (as opposed to v602) I also got a handshake failure when I was trying to connect to the v602 server "jts_old".

But once I had switched to using the older v602 client I was able to connect to both "jts_old"(v602) and "jts_new"(v606).
That's why I was a bit disappointed about the handshake failure when I was trying to create the repository workspace.

Yeah, you will always need to make sure that the RTC client you are using is older than the oldest sever in this scenario. The n-1 compatibility rule means that the RTC client can be at an older version than the server, but not the other way around.