From c5547ad9e7fe8cc2d1cde24959c6b92f74512640 Mon Sep 17 00:00:00 2001
From: "c1-dev-bot[bot]" <2740113+c1-dev-bot[bot]@users.noreply.github.com>
Date: Fri, 3 Apr 2026 20:17:37 +0000
Subject: [PATCH 1/2] Clarify v1-to-v2 connector migration impact on IDs

Add a warning that migrating from a v1 to a v2 connector generates new
app user IDs and entitlement IDs, which can break existing tasks, access
reviews, and access profiles. Remove the misleading option 4b (moving a
v2 connector into the original v1 app) since it does not preserve IDs
and offers no advantage over using the new app directly.
---
 baton/migration.mdx | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/baton/migration.mdx b/baton/migration.mdx
index 6870dd89..8db9ab00 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, 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,9 +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. You have two choices here:
-	1. Remove the v1 connector and its associated app.
-	2. Remove the v1 connector from the original app and add the v2 connector. Then remove the v2 connector from the testing app and delete the testing app.
+    When you’re confident the v2 connector is working as expected, remove the v1 connector and its associated app. Then update any tasks or access profiles that referenced the old app’s users or entitlements to point to the corresponding resources in the new v2 app.
     </Step>
 </Steps>
 

From 1aa8c0b6f00f8bb5fa4d8c36abdc8d0baf778966 Mon Sep 17 00:00:00 2001
From: Nestor Reyes <108298854+OneWhoNests@users.noreply.github.com>
Date: Tue, 7 Apr 2026 16:15:58 -0400
Subject: [PATCH 2/2] Apply suggestions from code review

2 Suggestions. We want to add Access review templates as well.

Co-authored-by: Nestor Reyes <108298854+OneWhoNests@users.noreply.github.com>
---
 baton/migration.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/baton/migration.mdx b/baton/migration.mdx
index 8db9ab00..5565b66c 100644
--- a/baton/migration.mdx
+++ b/baton/migration.mdx
@@ -25,7 +25,7 @@ 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, 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.
+**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):
@@ -42,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. Then update any tasks or access profiles that referenced the old app’s users or entitlements to point to the corresponding resources in the new v2 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>