--- title: Transfer records to remediation efforts in the Security Exposure Management Workspace description: You can transfer records from existing remediation efforts into new remediation efforts in the Vulnerability Manager Workspace. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/security-management/sem-transfer-VI-to-RE.html release: australia topic_type: task last_updated: "2026-03-12" reading_time_minutes: 3 breadcrumb: [Use Remediation Effort records, Use, Unified Security Exposure Management, Security Operations] --- # Transfer records to remediation efforts in the Security Exposure Management Workspace You can transfer records from existing remediation efforts into new remediation efforts in the Vulnerability Manager Workspace. ## Before you begin If confronted by a zero-day threat or a very critical vulnerability that you want to resolve quickly, you might want to consolidate any active records that you already have for this vulnerability into one remediation effort. However, each record can only be in one effort, and records can overlap among watch topics. So, to gather them all, you must transfer these records from multiple existing efforts into one remediation effort. Say, for example, you created a remediation effort that has one, high-priority vulnerability in it. Because this vulnerability is widespread and potentially impacts the other areas in your environment, you might have records that are associated with this vulnerability already in existing remediation efforts. To combine these records so they are all in one remediation effort, you can transfer any records from existing remediation efforts into a new remediation effort. **Note:** You cannot transfer records from recurring remediation efforts into new remediation efforts. For more information, see [Create a recurring remediation effort in the Vulnerability Manager Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-manager-workspace/vr-ws-create-recurringRE-steal-VI.md). Role required: - sn\_vul.vulnerability\_analyst, or sn\_vul.vulnerability\_admin for host vulnerable items \(VITs\) - sn\_vul.app\_sec\_manager for application vulnerable items \(AVITs\) - sn\_vul\_container.vulnerability\_analyst or sn\_vul\_container.vulnerability\_admin for container vulnerable items \(CVITs\) - sn\_vulc.admin for configuration test results \(CTRs\) ## Procedure 1. Navigate to **All** > **Security Exposure Management Workspace**. 2. Select the watch topics icon. 3. On the Watch Topics page, select a watch topic that you want to create a recurring remediation effort for. 4. Select **Create Remediation Effort**. The Create Remediation Effort modal is displayed. 5. In step one, Effort details, fill in the required fields. In the **Short description** field enter text that describes the recurring remediation effort that helps you locate it and track it from the effort list. In the **Description** field, enter more text about the context of the effort that helps you locate it easily from the list of remediation efforts. For example, `Active Log4J Vulnerabilities`. 1. In the **Name** field enter a name for your new remediation effort. By default the watch topic name is displayed. 2. In the **Description** field, enter text that will help you locate this remediation effort easily from the list of remediation efforts. 6. Select **Next**. Task generation details are displayed. 7. In step 2, Task generation, choose one method from the list to bundle the records in the remediation tasks that you generate from this remediation effort after it is created. - By Assignment group - By Assignment group and finding - By Assignment group and vulnerability - None \(No remediation tasks are created\). Use this method if you want to add records manually to a remediation task for this effort. See [Create a remediation task on-demand from Remediation Effort in the Vulnerability Manager Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-manager-workspace/vr-ws-create-rt-frm-re.md). 8. To automatically refresh the duplicate findings, you must select the **Automatically refresh duplicate vulnerable items for the created remediation tasks** option. 9. Select **Next**. 10. In step 3, Transfer, verify how many records will be added to the remediation effort and see how many records are available for transfer from other active remediation efforts. 11. To transfer records from other efforts, from the list, select the check boxes for the records you want. Select the **Transfer matching records from other active remediation efforts** check box and then select the check boxes for the records that you want to transfer from other active remediation efforts. 12. Select **Create Remediation Effort**. After a few moments, the new remediation effort is displayed. Depending on the number of records, it may take some time. A message indicates that the record is populating. The new remediation effort is created with any records that are available from the watch topic used to create it, in addition to any records that you selected for transfer from existing efforts. If you select records to transfer from an existing effort, and the existing effort transfers all of its records into your new effort, the remediation effort you moved the records from is closed. **Note:** If there are neither any records available from the watch topic, nor any records selected for transfer, the **Create Remediation Effort** button is deactivated. For more information on how the Remediation Tasks associated with the Remediation Efforts are impacted by records transfer, see [Transferring records or record carry over](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-manager-workspace/vr-ws-re-lifecycle.md). **Parent Topic:**[Use Remediation Effort records](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/sem-ws-remed-eff-rcd.md)