Hi Sam,

when I used the API, I was not able to just use the handle or complex object from one server on another server.
You can just use the same data for things like Strings or Int, because this is just a value.

For complex items e.g. users, timelines, iterations and the like I had to find the related object on the other server and use the handle to the remote object in the write. This is similar to CSV import, where RTC has to match iterations by ID's (or names).

An example: Owner of a work item. Get the ID or name or whatever is the mapping from the source data. Find the user in the target system e.g. by looking up its ID and set the value found in the remote object.

For work items, you also have to care for the links and have to run a second pass to recreate the work item links (and CLM links). So you have to create some method to be able to
- Identify which work item maps to which target work item (numbers might be different)
- Recreate the original link on the new work item
- potentially delete the old link on the original work item, e.g. to RRC or other CLM links.
- You have to download (and later upload attachments).

Because it is that hard (I am not even talking about recreation of the history), and you have to do this for every metadata object, a project move is very hard to implement.