title: Team Foundation Server: Cloning a Collection's Project into a new Collection
body: <p>We are looking to create a new Team Foundation Server Collection for the next version of our application development.  The source from our current version will largely not apply, except for a few DLLs which should more or less remain unchanged.  We wanted to make a new collection but were wondering if we would be able to clone the DLL projects from our existing collection to retain history.  </p>
  
  <p>Is this possible?  We realize this could bring up some "Dual Maintenance" issues if there are any bugfixes needed for the DLLs, but we are not too concerned about that scenario.</p>
  
  <p>So far, I have come up with a few resources.  Some MSDN posts were pointing people towards <a href="http://msdn.microsoft.com/en-us/library/dd936158.aspx" rel="nofollow">Splitting a Team Project Collection</a>.  The issue there, however, is that you can only have one project in each collection.  IT states: </p>
  
  <blockquote>
    <p>A project cannot exist in more than one collection. Until you delete all duplicated projects between the split collections, you will not be able to start the renamed collection.</p>
  </blockquote>
  
  <p>That is not really what we want.  We would like to maintain both projects with history in each collection.</p>
  
  <p>Otherwise, I saw the TFSConfig command.  It contains a /clone option, but I am not quite sure of its usage (additional examples are also hard to come by) and it mentions that it is primarily used for <em>splitting</em> as well.</p>
  
  <p>Are we looking to do something that isnt possible?  Would we need to copy the source and add it as a new project in the new collection and refer to the old collection if we really need history?  Thanks.</p>