--- title: "Convert policies and migrate data" slug: "convert-policies-and-migrate-data-3" tags: ["Product Usage", "DLP 11.11.x", "DLPE 11.11.x", "DLPExtn 11.11.x", "DLPNM 11.11.x", "DLPNP 11.11.x"] updated: 2026-09-01T07:30:00Z published: 2026-09-01T07:30:00Z canonical: "docs.trellix.com/convert-policies-and-migrate-data-3" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Convert policies and migrate data Upgrading to Trellix DLP 10.0 or later from versions earlier than 9.4.100 requires migrating or converting incidents, operational events, or policies. ePO - On-prem server tasks are used for the conversion/migration. **This task describes upgrading from Trellix DLP Endpoint 9.3.x.** Upgrade the Trellix DLP Endpoint extension to version 9.3.600 (9.3 Patch 6) or later, then install the Trellix DLP 9.4.100 or later extension in ePO - On-prem. The policy conversion task only converts rules that are enabled and applied to the database. To verify the status of rules you want to convert, review your Trellix DLP Endpoint 9.3 policy before conversion. 1. In ePO - On-prem, select **Menu** → **Automation** → **Server Tasks**. 2. Select **DLP Policy Conversion**, then click **Actions** → **Run**. The **Server Task Log** page opens, where you verify that the task is running. The converted policy is compatible with version 9.4.100 and later policies. > [!NOTE] > Note > > The task fails if it has run previously. If you make changes to the Trellix DLP 9.3 policy and want to rerun the conversion, edit the server task by deselecting the option **Do not run policy conversion if rule set '[9.3] Policy Conversion Rule Set' exists** on the **Actions** page. The previous rule set is deleted and replaced. 3. Return to the **Server Tasks** page, select **DLP incident migration from 9.3.x to 9.4.1 and above**, then click **Actions** → **Edit**. **DLP operational events Migration from 9.3.x to 9.4.1 and above** is performed in the same way. 4. Select **Schedule status** → **Enabled**, then click **Next** twice. > [!NOTE] > Note > > The migration is pre-programmed, so you can skip the **Actions** page. 5. Select a schedule type and occurrence. > [!TIP] > Tip > > Schedule the migration tasks for weekends or other non-work hours due to the load they place on the processor. 1. Set the start date and end date to define a time period, and schedule the task for every hour. 2. Schedule repeating the task according to the size of incident database you are migrating. Incidents are migrated in chunks of 200,000. 6. Click **Next** to review the settings, then click **Save**.