Need ability to move items from one project to another or merge 2 or more projects into one

Hi Moses,
Great question. Let me try to unpack it to help us determine best options.
1. Does Jama allow moving certain items out of a project to another? If so, how?
 2. Maybe even merge 2 or more project items into one? If so, how?
It sounds like you are currently creating a new project and items from scratch or duplicating an existing project and deleting what isn't needed.

1. There isn't a specific method to move items out of a project into another. In terms of best strategies to accomplish this, I think it depends on the data you need to move. A) If it's items, relationships, and perhaps even related items, I would suggest the Reuse function, because you can specify what information you want transferred to the other project. As long as you do not check the "Sync Item" box, you will be creating a separate discrete item in the destination of your choice (just choose manual Destination). You can then delete the original item from the source project. This is preferred because you can "move" items, folders, or components this way. We recently recorded a Q&A session about Reuse that may be helpful.
However, if it's a matter of picking and choosing what items you want to move, you're probably better off building a filter to view all the items you want to move, then exporting them to Excel. Then import them into the Destination project. The upside is that you can move only what you want rather than whole containers, but the negative is none of the relationships will be moved over—you'd have to manually build them or use the Import Relationship Plugin.

2. I'm not quite sure what you are trying to accomplish by merging 2 project items into one project. If it's a matter of consolidation items from two different projects into one, then I'd recommend A or B above, as the source of the items doesn't really matter.

If neither of those will work for you in these scenarios, we can change this post to an Idea so that it's considered a feature request. If this is the case, it would be good if you could provide insight why the proposed A or B methods above won't help you accomplish what you need. Thanks!

OK, I understand. Your primary concern with this is needing to maintain the version history, so reusing items without syncing or project duplication followed by item deletion won't work for you. And you're right about the technical side of it—as it stands it would require a bit of work to make this function possible (especially considering the versions). I've changed this post to an Idea so our Product team can consider it as a feature. I know that we're working on some new ways to work with items, so this feedback is good to have. Thanks!

"move" is something that we are actively investigating. The complexity in dealing with item ID's, integration setup, item type setup (especially across projects), tags, attachments, versioning, sync, baselines, reviews, permissions, etc. is something we have to be very thorough with. 

Would you expect to be able to move an item and then revert to an old version of an item? If you revert to an older version, would the expectation be that it goes back to the old location within Jama? 

Would you expect that the exact item type would need to be in both projects? 

This is exactly the scenario I was just asked about by our director.  I'm glad to have found this stream.  This conversation is a year old, has there been any further updates or conversations about moving items from one project to another?