This article provides a description of the Advanced IM Export data management policy. The system provides multiple options to export data from the platform. Export policies are recommended when large volumes of data have to be exported from the system on an ongoing basis. For more information on the available export options and their comparison, see Export.

The export policies are executed by the Storage Management Service on the Media Repository/Application Servers.

An export data management policy creates a copy of the selected conversations and places the data in a configurable storage/export location. It consists of a (previously created) storage/export target, and a set of filters to choose which conversations should be exported. Policies with the export action do not modify or impact the original conversations in any way. The exported data is not accessible in any way from the system.

Creating an Advanced IM Export policy

To create an export data management policy, follow the steps below:

Step 1 - Create a Storage target for the export policy

Step 2 - Follow the generic policy creation steps described on the following page: Data management policies

Step 3 - Select Advanced IM Export as the action

Step 4 - Select the Destination Storage Target you created from the list. Only SMTP Storage Target is supported!

Step 5 - Configure policy-specific settings as follows:

Name	Description
Decrypt Encrypted Conversations	If conversation-related files are encrypted, the system can automatically decrypt the files before exporting. Original files remain encrypted.
Export Attachments in IM Conversations	Export file attachments with instant message conversations.
Export Conversations Based on	Users: Participant-based export will produce data for each configured user or participant (depending on configuration) which will result to data duplication. Channels/Chats: Conversation-based export will produce data only once for exported conversations avoiding duplications. The chat/channel based export option should not be used with the Export API based integrations. Due to limitations in the Microsoft Export API, the export process might not be able to identify all relevant data for the export and messages will be missing from the export. The chat/channel based export was primarily designed and implemented for DLP / Webhook based integrations.

Step 6 - Configure Custom Schedule if you want o run the export in a specified time

Step 7 - Configure Filtering Criteria to specify which conversations should be exported by this policy