--- title: "Migrate policies automatically" slug: "migrate-policies-automatically-4" tags: ["Product Usage", "ENS 10.7.x", "ENS 26.x"] updated: 2026-09-13T18:52:33Z published: 2026-09-13T18:52:33Z canonical: "docs.trellix.com/migrate-policies-automatically-4" --- > ## 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. # Migrate policies automatically Custom policies created in Host Intrusion Prevention can be migrated automatically or manually using the Endpoint Migration Assistant. Currently, the custom policies created for Host Intrusion Prevention: IPS can be migrated automatically and manually. You must apply the policy to an entire system tree or a single group in the system tree before you migrate your policies in the automatic mode. Make sure that **Endpoint Migration Assistant** extension is installed in the ePO - On-prem. 1. Log on to ePO - On-prem server as an administrator. 2. Select **Menu** → **Policy** → **Endpoint Migration Assistant**. 3. Select the migration mode as automatic. 4. For manual migration, select objects to migrate as **Policies**. 5. For automatic migration, select the system to be migrated, click **Next**. You can select the entire System Tree or a single group in the system tree. 6. Click **Next** to generate a preview of the new Endpoint Security policies. A progress bar appears and lets you know how many policies are being included in the preview. 7. Review the new policies. 1. Under **New Categories** in the left pane, select a category, then preview the new policies for that category in the right pane. 2. (Optional) For every new policy that is created under Endpoint Security, click **Rename and Edit Notes** to rename the policy or edit the policy notes, if needed. 8. Click **Save** to run a server task to complete the migration. The Migration Assistant runs a server task in the background to migrate your policies. You can check its status in the Server Task Log. You must wait for the server task to complete before starting another migration session.