Migrate a Bitbucket Cloud Personal Access Token

Snyk recommends using the Bitbucket Cloud App integration for smoother integration.
This topic describes how to migrate your existing Bitbucket Cloud Personal Access Token (PAT) integration —displayed in Snyk as Bitbucket Cloud (Legacy)—to the Bitbucket Cloud App integration.

Deciding which Bitbucket Cloud integration to use

In general, the recommended way of integrating to Bitbucket Cloud is the new app integration. However, the new integration doesn't fit all cases. This section should give you an idea of which Bitbucket Cloud integration best fits for you.

Main capabilities unlocked by the new app integration

  • It allows using Snyk with Bitbucket’s allowlisting IP addresses premium tier feature.
  • It helps handle rate limiting issues for companies who spread their repos across multiple workspaces in Bitbucket Cloud.
  • The new integration supports the first party interface in Bitbucket Cloud (Snyk's Security tab) out-of-the-box, meaning you wouldn't be required to install and maintain the first-party extension app in order to consume Snyk's security insights from Bitbucket Cloud.

Limitations of the new app integration

  • In the new app integration, every Snyk Org can connect only to one workspace in Bitbucket Cloud. If you rather like to import projects from various different workspaces in Bitbucket into the same single Org in Snyk, you should use the PAT integration.
  • The new app integration does not yet support Snyk Multi Tenant EU, Snyk Multi Tenant AUS and Snyk Single Tenant cloud deployments.
  • For customers who are part of the custom branch closed beta, the new app integration's first party interface in Bitbucket Cloud does not allow importing projects from a non-default branches. It is still possible though to import a non-default branch - you'd just need to do it from within import modal.

Are there any plans to End-of-Life the Personal Access Token (PAT) integration?

No - the Personal Access Token Bitbucket Cloud integration is fully supported and there aren’t any plans to stop supporting it.
However, there is the 1st-party-interface extension app - an app that serves as an extension layer to the PAT integration that allows developers to consume Snyk’s findings from within the Bitbucket interface. This extension app was developed and supported by an external contractor company. As this functionality is now an integral part of the new app integration, the extension app has now moved to no-support mode, meaning that customers who use the PAT integration alongside the first-party extension app would need to migrate to the new app integration in order to get support for the first party interface functionality.

Migration instructions

Things you should know before migrating

In order to migrate to the new app integration, you would need to remove all the previously imported projects from Snyk, delete the legacy PAT integration and its projects, set up the new app integration and reimport your projects to Snyk from the new integration.
Before going through the migration process, it's important to note that the following project-level information would not presist:
  • Historic project related data, including trend numbers of fixing vulnerabilities
  • Project related metadata (ignores/tags)

Migration process

The migration process includes:
  1. 1.
    Deleting the existing projects that are connected to the Bitbucket Cloud PAT (Legacy) integration in Snyk.
  2. 3.
    Removing the first-party extension for the Legacy integration in Bitbucket (optional)
  3. 4.
    Connecting the Bitbucket Cloud App and importing projects.

1. Delete existing projects

Delete all the existing projects in Snyk that were previously imported from the Legacy integration. To use the bulk delete action for your projects, go to
(Organization settings) > Usage and scroll to the Projects section.
Delete existing projects from the Snyk Bitbucket Cloud PAT (Legacy) integration

2. Disconnect the Legacy integration

To disconnect the Bitbucket Cloud (Legacy) integration, go to the settings page of Bitbucket Cloud (Legacy) integration, scroll to the relevant section and click Disconnect.
Disconnect the Bitbucket Cloud PAT (Legacy) integration

3. Remove the Snyk tab for the Legacy integration in Bitbucket Cloud (optional)

The Bitbucket Cloud (Legacy) has an optional first-party interface app for Bitbucket Cloud.
This app can potentially be installed on your Bitbucket Cloud workspace to enrich the legacy integration with a first-party interface (a "Snyk" tab).
If you used this app, before setting up the Snyk Bitbucket Cloud App, remove the Legacy interface app in Bitbucket Cloud before continuing to the next step: this functionality is supported out-of-the-box in the Snyk App integration. Go to your Workspace settings page in > Manage installed apps, expand the Snyk Security for Bitbucket Cloud app, and click Remove.
Remove the first-party Snyk Legacy interface app in

4. Set up the Bitbucket Cloud App integration

See the Bitbucket Cloud App integration topic for more detailed information.

Migration demo

Watch this Snyk Bitbucket Cloud App migration demo to see how it's done!

Marco Morales, a Partner Solutions Architect at Snyk, talks about the Snyk Bitbucket Cloud App and goes through the process to migrate an existing Legacy integration to the Snyk Bitbucket Cloud App - in under 5 minutes!
Go to timestamp 2:34 to jump right into the demo:
How to migrate to the new Snyk Bitbucket Cloud App integration
© 2023 Snyk Limited | All product and company names and logos are trademarks of their respective owners.