--- title: "How repeated automatic migrations are handled" slug: "how-repeated-automatic-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-automatic-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 automatic migrations are handled Running automatic migration after you have already migrated some or all of your settings affects the new objects created during the previous migration session. When you run automatic migration after migrating previously, the Migration Assistant: - Deletes objects created during a previous automatic migration session for the same systems. | First migration | Second migration | Policies in **Policy Catalog** after second migration | | --- | --- | --- | | Single group | Same single group | Only the new policies created in the most recent migration session. (The policies created in the first migration session are replaced.) | | Entire System Tree | | Entire System Tree | Entire System Tree | | Entire System Tree | Single group | For the group — Only the new policies created in the most recent migration session. (The policies created in the first migration session are replaced.) For other systems in the System Tree — Policies created in the first migration session. (The policies created in the first migration session are not changed.) | - Retains objects created during a previous manual migration, but does not retain their assignments. - Assigns the new policies to managed systems. For example, if you have assigned policies that you migrated manually to managed systems, the new policies are assigned instead. These actions also apply to the Common **Options** policies created during previous migrations.