Switching Git providers or Slack workspaces without breaking Axolo

Use this guide before switching Git providers, reinstalling Axolo, or reconnecting a Slack workspace.

A migration can affect repository access, GitLab group access, Slack channels, user mapping, and billing visibility.

Common migration cases

This guide applies if you are:

• moving from GitLab to GitHub,
• moving from GitHub to GitLab,
• installing Axolo on a different Slack workspace,
• reinstalling Axolo after using the wrong workspace,
• changing GitHub organizations or GitLab groups,
• trying to preserve a paid plan after a migration.

Before you migrate

Before changing anything, collect:

1. Current Slack workspace name.
2. New Slack workspace name, if changing.
3. Current Git provider: GitHub or GitLab.
4. New Git provider, if changing.
5. GitHub organization or GitLab group name.
6. Billing email.
7. Whether you want to keep historical Axolo data.

If you are unsure, contact support before deleting an integration.

If you installed Axolo on the wrong Slack workspace

Read the existing guide first:

I've installed Axolo on the wrong Slack Workspace

If you have not connected GitHub or GitLab yet, the fix is usually simpler.

If GitHub or GitLab is already connected, contact support before deleting data.

If you migrate from GitLab to GitHub

When moving from GitLab to GitHub, Axolo needs access to the right GitHub organization and repositories.

Checklist:

1. Install or approve the Axolo GitHub App for the right organization.
2. If you selected specific repositories, add the repositories from Settings → Integrations → Update GitHub app.
3. Confirm the Slack workspace is the right one.
4. Onboard or refresh users if GitHub emails differ from GitLab emails.
5. Confirm the repositories that should create PR channels are active in Axolo.
6. Contact support if your paid plan does not appear correctly after migration.

Related guide:

Add a new repository to Axolo from GitHub

If you migrate from GitHub to GitLab

For GitLab Cloud, Axolo installation is less granular than GitHub: you select the GitLab group to integrate with Axolo.

Checklist:

1. Confirm who owns the GitLab group.
2. Select the GitLab group you want to integrate with Axolo.
3. Confirm Axolo saved your organization members and project information.
4. Onboard or refresh users if GitLab emails differ from Slack emails.
5. Confirm the projects that should create MR channels are active in Axolo.

For self-hosted GitLab, you also need to create the Axolo application in your GitLab instance and configure the required scopes.

Read:

GitLab troubleshooting hub: webhooks, access tokens, CI/CD, and MR notifications

Reinstall vs delete data

Do not delete your Axolo data unless you are sure you want a full reset.

Deleting data may remove connected integration data and make it harder to preserve history.

If your goal is to fix a wrong workspace, switch providers, or preserve billing, contact support first.

Read:

How to delete all my data on Axolo

Billing after migration

After a migration, your subscription may not immediately appear on the new integration.

If your paid plan appears as free, do not create a new paid subscription before contacting support.

Send us:

• Company name,
• old Git provider and organization/group,
• new Git provider and organization/group,
• Slack workspace,
• billing email.

Related guide:

Manage your Axolo subscription, invoices, trial, downgrade, and cancellation

What to send support

For any migration issue, send:

• what you are trying to do,
• old Slack workspace and new Slack workspace, if relevant,
• old Git provider and new Git provider, if relevant,
• GitHub organization or GitLab group,
• billing email, if the issue is subscription-related,
• whether you need to preserve history,
• screenshots or links showing the current error.

We can then tell you whether to reconnect, reinstall, refresh, or manually migrate settings.

Updated on: 11/05/2026