Hi and welcome to Bitbucket → GitHub Migration Dashboard!

This dashboard helps you verify that you have migrated all necessary repositories from Bitbucket to GitHub. It also enables the DevEx team to track migrated or deprecated repositories to ensure proper backups.

More information you can find on our Confluence page.

Quick Start

1. When you first open the link, authenticate by clicking the Login button at the top right. Follow the standard PostNord login flow.
2. After logging in, select the Bitbucket Workspace where your repositories are located. Click “Save and Continue” to load and display the repositories and matches for the selected workspace.

Ok, I see the table. What should I do here?

Our scripts automatically matched Bitbucket and GitHub repositories by comparing multiple parameters. While most matches have high confidence, we ask you to confirm that the repositories marked as Migrated are correctly matched. For other repositories, please help with mapping or identify deprecated repositories.

How can I do this?

Repositories are grouped by project by default. To simplify your work, filter repositories by Jira Projects you manage and use bulk actions as needed.

In some cases, update repository status individually by clicking the button in the Action column.

Our goal is to have no PENDING or NOT MATCHED statuses remaining for your repositories.

Please update only repositories that belong to your team.

Updating Matching Status

Click the button to update a repository's matching status. You can select one of these statuses: PENDING, CONFIRMED, REJECTED or DEPRECATED. You may also manually map a GitHub repository, which sets the status to MANUAL automatically.

Bulk Actions

Update statuses for multiple repositories by selecting checkboxes and clicking the Bulk Actions button above the table.

Available bulk actions depend on the selected repositories' statuses:

• If selected repositories have only Migrated or Possibly migration status, you can bulk update them to CONFIRMED.
• For Not Migrated repositories, you can bulk update them to DEPRECATED.

Statuses

Migration Status

This column indicates if the repository is considered migrated. It has four possible values:

• Migrated - matching criteria are strong, and the repository is considered migrated.
• Possibly - matching criteria are not strong enough to confirm the GitHub repository is the exact migrated repository from Bitbucket.
• Not Migrated - no matching found or matching criteria are weak.
• Deprecated - the repository is deprecated and not intended for migration.

Match Status

This column indicates the current matching status between Bitbucket and GitHub repositories:

• PENDING - awaiting user confirmation or rejection.
• CONFIRMED - the matching is correct.
• REJECTED - the matching is incorrect and must be ignored.
• MANUAL - matching specified by the user.
• DEPRECATED - migration or backup is unnecessary for this repository.

Match Type

Specifies key criteria used for matching the repository and determining its migration status:

• DOUBLE-HASH - Bitbucket and matched GitHub repositories have similar SHA of the first and closest-to-GitHub repository creation date commits, indicating preserved commit history from creation through migration.
• HASH - Bitbucket and matched GitHub repositories have similar SHA of the first commit. This is a weak criterion alone, as it may indicate a fork with different commit history, but combined with NAME it suggests a high probability of correct matching.
• NAME - Bitbucket repository name closely matches (over 80% similarity) the GitHub repository name. See difflib for details. You can view name similarity by enabling the “Name Similarity” column.