Skip to content

Clarify v1-to-v2 connector migration impact on IDs #183

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mindymo merged 3 commits into from
Apr 7, 2026
Merged

Clarify v1-to-v2 connector migration impact on IDs #183

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c5547ad
Clarify v1-to-v2 connector migration impact on IDs
Apr 3, 2026
1aa8c0b
Apply suggestions from code review
OneWhoNests Apr 7, 2026
fe3bbea
Merge branch 'main' into docs/ce-591-migration-docs-update
mindymo Apr 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion baton/migration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,10 @@

## 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>
Expand All @@ -38,7 +42,7 @@
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>

Expand Down Expand Up @@ -68,7 +72,7 @@
| [Coupa v1](/baton/v1/coupa) | [Coupa v2](/baton/coupa) | Provisions groups, roles, and licenses |
| [Datadog v1](/baton/v1/datadog) | [Datadog v2](/baton/datadog) | Syncs teams Provisions roles and teams |
| [Docusign v1](/baton/v1/docusign) | [Docusign v2](/baton/docusign) | Provisions accounts |
| [GitHub v1](/baton/v1/github) | [GitHub v2](/baton/github) | Provisions repositories and orgs |

Check warning on line 75 in baton/migration.mdx

View check run for this annotation

Mintlify / Mintlify Validation (conductorone) - vale-spellcheck

baton/migration.mdx#L75 

Did you really mean 'orgs'?
| [GitLab v1](/baton/v1/gitlab) | [GitLab v2](/baton/gitlab) | Provisions accounts, projects, and groups |
| [Google Cloud Platform](/baton/v1/google-cloud-platform) | [Google Cloud Platform with Google Workspace](/baton/google-cloud-platform) | Syncs groups, Workforce Identity pools and pool providers, secrets Provisions groups, Workforce Identity pools |
| [Google Workspace v1](/baton/v1/google-workspace) | [Google Workspace v2](/baton/google-workspace) | Modernized backend architecture (no capability changes) |
Expand Down