> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/platform-administration/snyk-broker/universal-broker/upgrade-an-organization-integration-from-classic-broker-to-universal-broker.md).

# Upgrade an Organization integration from Classic Broker to Universal Broker

How to upgrade an Organization integration from Classic Broker to the Universal Broker

{% hint style="info" %}
Before running a Broker client, Universal Broker operators declare their desired deployment model to specify which Broker connections to support. This changes the Classic Broker approach from `organization > integrations > broker connections` to `broker connections > integration/organization`.

You do not need to re-import repositories. The migration acts as a token rotation, and Snyk preserves your existing targets and data if your connection settings remain unchanged.
{% endhint %}

## Migrate a single Organization

To upgrade existing Classic Broker integrations to Universal Broker for one Organization at a time:

1. Create the Universal Broker connection you want to use. For details, see [Basic steps to install and configure Universal Broker](/platform-administration/snyk-broker/universal-broker/basic-steps-to-install-and-configure-universal-broker.md).
2. Run the Universal Broker client. For details, see [Running your Universal Broker client](/platform-administration/snyk-broker/universal-broker/running-your-universal-broker-client.md).
3. Use a test Organization to test the Universal Broker connection. Run `snyk-broker-config workflows connections integrate` and enter the test Organization ID, using the same credentials as were used for the Classic Broker connection. The objective is to have the same access as the Classic Broker.
4. When you are ready, run `snyk-broker-config workflows connections migrate`.
   1. Select the deployment and connection you want to upgrade to.
   2. Enter the Organization ID for the connection you want to upgrade to the Universal Broker.
   3. Confirm your choice.\
      When the command completes, the connection to the Organization has been upgraded.
5. Repeat the procedure for all the relevant connections integrated with each Organization.
6. When you have migrated all of the integrations to the Universal Broker client, delete or remove the Classic Broker container.

If you run into issues, you can roll back to the Classic Broker client as long as you have not terminated the Classic Broker client. To roll back:

1. Disconnect the Universal Broker connection that you migrated to previously.
2. If any other Classic Broker Organization is left with the same Broker token, after you disconnect the Universal Broker token, use the API endpoint Clone an integration (with settings and credentials) to copy the integration settings from another Organization and reuse the previously used Classic Broker token through the API.
3. If there are no Classic Broker Organizations left with the old Broker token, then after you disconnect the Universal Broker connection, set up a new Classic Brokered connection. Copy the Broker token from the new Brokered connection as a parameter and restart the Broker container.

## Migrate multiple Organizations

The bulk migration workflow allows you to migrate multiple Organizations at the same time. To do this:

1. Create a test connection and integrate it. See steps 1-3 from [Migrating a single Organization](#migrating-a-single-organization).
2. Run `snyk-broker-config workflows bulk-migration list` to see a list of all the Organizations that can be migrated.
3. Run `snyk-broker-config workflows bulk-migration apply` to migrate all the Organizations listed in the previous step. Select the deployment and connection you want to upgrade to and confirm your choice.

This command is asynchronous, which means migration happens in the background. If you are migrating several Organizations, the migration process can take some time to complete.

You can run `snyk-broker-config workflows connections get` to list the connections and confirm they have been migrated.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.snyk.io/platform-administration/snyk-broker/universal-broker/upgrade-an-organization-integration-from-classic-broker-to-universal-broker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.