diff --git a/baton/migration.mdx b/baton/migration.mdx
index 2b982e5..7fb6769 100644
--- a/baton/migration.mdx
+++ b/baton/migration.mdx
@@ -24,6 +24,10 @@ If we decide in the future to retire a v1 connector entirely, we’ll be in touc
 
 ## Migrate from a v1 to a v2 connector
 
+<Warning>
+**Important: Migrating from a v1 to a v2 connector replaces internal identifiers.** When you set up a v2 connector — whether in a new app or the same app as the v1 connector — ConductorOne generates new app user IDs and entitlement IDs. Any existing tasks, access reviews, access review templates, or access profiles that reference the old v1 app’s users or entitlements will no longer resolve to the correct resources. Plan accordingly and review your tasks and access profiles after completing the migration.
+</Warning>
+
 The basic process for migration is as follows (see the special note below about migrating IdP connectors):
 
 <Steps>
@@ -38,7 +42,7 @@ The basic process for migration is as follows (see the special note below about
     Configure and test the v2 connector as needed.
     </Step>
     <Step>
-    When you’re confident the v2 connector is working as expected, remove the v1 connector and its associated app.
+    When you’re confident the v2 connector is working as expected, remove the v1 connector and its associated app. Then update any access reviews, access review templates and access profiles that referenced the old app’s users or entitlements to point to the corresponding resources in the new v2 app.
     </Step>
 </Steps>