--- title: "How repeated manual migrations are handled" slug: "how-repeated-manual-migrations-are-handled" tags: ["Migration", "ENS 10.7.x"] updated: 2026-10-07T18:04:46Z published: 2026-10-07T18:04:46Z canonical: "docs.trellix.com/how-repeated-manual-migrations-are-handled" --- > ## 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. # How repeated manual migrations are handled Manual migration has no effect on objects migrated during a previous migration session. For example, if you migrate some policies for a product module, then migrate the same policies again: - The new policies are created in the **Policy Catalog**. If the target policy name already exists, the Migration Assistant appends a digit to the newer policy name (for example, My Policy, My Policy-1, My Policy-2). - The previously migrated policies still appear in the **Policy Catalog**. - If you migrate McAfee Host IPS **Firewall** policies again, you need to migrate the **Host IPS Catalog** again. (The Migration Assistant shows the date and time when the Catalog was last migrated, if applicable.) > [!NOTE] > Tip > > **Best practice:** Migrate the **Host IPS Catalog** immediately before the McAfee Host IPS **Firewall** policies to ensure that they remain synchronized. Manual migration does not retain assignments for migrated objects. You must assign the migrated objects manually. You also must manually delete the objects created during the previous migration session that you no longer want. If you have assigned objects that you created during a previous manual migration session, these assignments are not affected if you migrate the same objects again.