---
sourceDocument: Australia Security Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/security-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Security Management

ft:clusterId :

    - security

bundleId :

    - security

workflow :

    - Technology


---

# Copy a Splunk ES profile

# Copy Splunk Enterprise Security profiles from one instance to another using
export/import functionality {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

You can export and import Splunk Enterprise Security profiles settings from one
ServiceNow AI Platform instance to a different ServiceNow AI Platform
instance.

## Before you begin

The settings you can export and import include profile name, correlation rules,
mappings, filters, aggregation criteria, field translations, fetched sample data,
scheduling, and configuration tile source information.

Role required: sn_si.ingestion_profile_admin  
Note:  
Users with the sn_si.admin role can perform all operations available to a profile admin, as the sn_si.admin role inherits the required permissions by default.

## About this task

This functionality allows the security administrator to copy profiles that have been
tested and verified on one ServiceNow AI Platform instance, for example on
non-production, to another ServiceNow AI Platform instance, for example production,
without the need to redo all configuration settings. The settings that are exported
and imported include profile name, correlation rules, mappings, filters, aggregation
criteria, field translations, fetched sample data, scheduling, and configuration
tile source information.  
Note:  
When you export a manual event forwarding profile type, the attachment data used for the sample field mapping is copied, however, the attachment file itself is not exported.

## Procedure

1. Navigate to AllSplunk ES IntegrationSplunk ES Event Profiles.
2. Select a profile that you want to export to another ServiceNow AI Platform instance.  
   You can select multiple profiles for export.
3. From the Actions menu, select Export.
4. Once the export complete message appears, select Download.  
   The exported payload.xml file is downloaded on your computer. The file contains the profile name, correlation rules, mappings, filters, aggregation criteria, field translations, fetched sample data, scheduling, and
   configuration tile source information. When you select and download multiple profiles, they appear in the same payload.xml file.

   You can now proceed to import the profile in another ServiceNow AI Platform instance.
5. Navigate to Splunk ES IntegrationSplunk ES Event Profiles.
6. Select Import.
7. Select Choose file and select the xml file on your computer.
8. Select Upload.
9. Select Close and Reload Profiles.  
   You have successfully imported the profile from another ServiceNow AI Platform instance.

   Verify that the exported Source (Splunk API account and Splunk server URL) and MID Server configuration settings are valid and available in imported ServiceNow AI Platform instance. Update your Splunk Enterprise Security configuration if required.
10. **Optional:** Verify the MID Server settings after your import a profile.
11. **Optional:** Navigate to Security OperationsIntegration Configurations.
12. **Optional:** Select the Splunk Enterprise Security configuration tile, and select Update.
13. **Optional:** Review and update the Source and MID Server details as required.

*[\>]: and then