Migrate to a new connector version
Why are some connectors marked v2?
We’ve learned a lot since we started building connectors! One key advancement was the creation of the Baton framework for connector development, which ConductorOne launched in December 2022.
Since then, we’ve rolled out updated versions of some connectors that were written pre-Baton in order to modernize the connectors’ architecture, improve their performance, and enable new capabilities. (See the table below for an overview of new capabilities in v2 connectors.)
What happens to the v1 connector when a v2 is launched?
We want anyone setting up a connector for the first time to use the latest and greatest version, so when a v2 version is launched, we mark the original (v1) connector with a v2 available label on your Connectors page. This is intended primarily to lessen the chances that someone will set up a v1 connector by accident when a shiny new v2 version is available.
Are v1 connectors still safe to use?
Absolutely. We continue to support both versions of a connector so long as they’re in use.
If we decide in the future to retire a v1 connector entirely, we’ll be in touch with anyone still using that connector well in advance of its retirement, and will provide support and guidance for migrating to the new version.
Migrate from a v1 to a v2 connector
The basic process for migration is as follows (see the special note below about migrating IdP connectors):
Leave the v1 connector running as-is
Set up the v2 connector (it’s safe to add a second connector from the same app, and even to set it as a directory)
Configure and test the v2 connector as needed
When you’re confident the v2 connector is working as expected, remove the v1 connector
Depending on the complexity of the connected software and how you’ve set it up in ConductorOne, this process might be quite simple, or a bit more complex. Our Customer Success team is always ready to talk through the process with you and provide advice and support.
Thinking of migrating an IdP connector? If you’re ready to migrate to a v2 version of your identity provider (IdP) connector, make sure to talk with Customer Success before you proceed. Due to how IdP apps pull in child apps these connector migrations can have some special complexities, and we can help make sure the migration goes smoothly.
Version comparison
The table below outlines the differences between the v1 and v2 connectors, highlighting the key improvements in each newer version.
| v1 connector docs | v2 connector docs | Key capability changes and improvements in v2 |
|---|---|---|
| AWS v1 | AWS v2 | Syncs IAM roles and IAM groups Provisions IAM groups |
| Azure Active Directory | Microsoft Entra ID | Syncs enterprise applications and licenses |
| Cloudflare v1 | Cloudflare v2 | Modernized backend architecture (no capability changes) |
| Confluence v1 | Confluence v2 | Syncs spaces and space permissions Provisions groups and space permissions |
| Coupa v1 | Coupa v2 | Provisions groups, roles, and licenses |
| Datadog v1 | Datadog v2 | Syncs teams Provisions roles and teams |
| GitHub v1 | GitHub v2 | Provisions repositories and orgs |
| Google Workspace v1 | Google Workspace v2 | Modernized backend architecture (no capability changes) |
| Okta v1 | Okta v2 | Syncs custom org roles |
| OneLogin v1 | OneLogin v2 | Syncs groups |
| Salesforce v1 | Salesforce v2 | Syncs profiles and applications Provisions groups, roles, permission sets, and profiles |
| Snowflake v1 | Snowflake v2 | Syncs databases Provisions roles |
| Zendesk v1 | Zendesk v2 | Syncs roles Provisions organizations, groups, and roles |