TIBCO Scribe® Insight doesn't have a method for moving Integrations from one collaboration to another. However this can be accomplished without having to recreate an integration by following the steps below. This article pertains only to moving integrations and does not cover other items within the collaboration, such as Monitors or Publishers.

Be sure to verify if anything referencing a folder path such as a File Integration, pre/post jobs need to be updated after moving the integration. This article assumes the same folder structure is used when moving integrations from one collaboration folder to another.

1. Backup the ScribeInternal Database
2. Make a copy of the collaborations folder
3. Create the new collaborations via the console
4. Create folder(s) with the same structure in the new collaboration (can probably just move folders/files to new collaboration folder)
5. In SQL Server Management Studio query the Collaborations table to get the New Collaboration ID's

   SELECT [COLLABORATIONID],[NAME] FROM [SCRIBEINTERNAL].[SCRIBE].[COLLABORATIONS] Order by Name

6. Determine which Integrations will be changed to the new collaboration (need the ListenerId)

   SELECT c.[COLLABORATIONID]
        ,c.[NAME]
        ,l.[LISTENERID]
        ,l.[EVENTTYPE]
        ,l.[NAME]
        ,l.[JOBSPECNAME]
   FROM [SCRIBEINTERNAL].[SCRIBE].[COLLABORATIONS] c
   INNER JOIN [SCRIBEINTERNAL].[SCRIBE].[LISTENERS] l ON c.[COLLABORATIONID] = l.[COLLABORATIONID]
   Order by c.[COLLABORATIONID],l.[NAME]

7. Update/Change the CollaborationId for the appropriate integrations that will be in the new collaboration (update 1 new collaboration at a time)

Update [SCRIBEINTERNAL].[SCRIBE].[LISTENERS] Set [COLLABORATIONID]=14 -- new collaboration id
  Where [COLLABORATIONID] = 12 -- old collaborationid
  And LISTENERID IN (27,35,37)  -- list of integrations to change

8. Verify integrations are working as expected
 

This article describes the steps necessary to move an integration to a different collaboration