diff --git a/data/reusables/enterprise-migration-tool/about-the-migrator-role.md b/data/reusables/enterprise-migration-tool/about-the-migrator-role.md
index 7301a127b168..96b203361391 100644
--- a/data/reusables/enterprise-migration-tool/about-the-migrator-role.md
+++ b/data/reusables/enterprise-migration-tool/about-the-migrator-role.md
@@ -2,6 +2,9 @@ To remove the need for organization owners to complete migrations, {% data varia
 
 You can grant the migrator role to an individual user or a team. We strongly recommend that you assign the migrator role to a team. Then, you can further customize who can run a migration by adjusting team membership. For more information about changing team membership, see "[AUTOTITLE](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)" or "[AUTOTITLE](/organizations/organizing-members-into-teams/removing-organization-members-from-a-team)."
 
+> [!WARNING]
+> When you grant the migrator role in an organization to a user or team, you are granting them the ability to import or export any repository in that organization.
+
 To grant the migrator role, see "[Granting the migrator role](#granting-the-migrator-role)."
 
 After you grant the migrator role, make sure the migrator uses a {% data variables.product.pat_generic %} that meets all the requirements for running migrations.