Multi-cell migration checklist

dbt Labs is in the process of migrating dbt Cloud to a new cell-based architecture. This architecture will be the foundation of dbt Cloud for years to come, and will bring improved scalability, reliability, and security to all customers and users of dbt Cloud.

There is some preparation required to ensure a successful migration.

Migrations are being scheduled on a per-account basis. If you haven't received any communication (either with a banner or by email) about a migration date, you don't need to take any action at this time. dbt Labs will share migration date information with you, with appropriate advance notice, before we complete any migration steps in the dbt Cloud backend.

This document outlines the steps that you must take to prevent service disruptions before your environment is migrated over to the cell-based architecture. This will impact areas such as login, IP restrictions, and API access.

Pre-migration checklist

Prior to your migration date, your dbt Cloud account admin will need to make some changes to your account.

If your account is scheduled for migration, you will see a banner indicating your migration date when you log in. If you don't see a banner, you don't need to take any action.

1. IP addresses — dbt Cloud will be using new IPs to access your warehouse after the migration. Make sure to allow inbound traffic from these IPs in your firewall and include it in any database grants. All six of the IPs below should be added to allowlists.
   • Old IPs: 52.45.144.63, 54.81.134.249, 52.22.161.231
   • New IPs: 52.3.77.232, 3.214.191.130, 34.233.79.135
2. IDE sessions — Any uncommitted changes in the IDE might be lost during the migration process. dbt Labs strongly encourages you to commit all changes in the IDE before your scheduled migration time.
3. User invitations — Any pending user invitations will be invalidated during the migration. You can resend the invitations once the migration is complete.
4. Git integrations — For customers on a dbt Cloud Enterprise plan, native integrations with GitLab and Azure DevOps will need to be manually updated. dbt Labs will not be migrating any accounts using these integrations at this time. If you're using one of these integrations and your account is scheduled for migration, please contact support and we will delay your migration.
5. SSO integrations — Integrations with SSO identity providers (IdPs) will need to be manually updated. dbt Labs will not be migrating any accounts using SSO at this time. If you're using one of these integrations and your account is scheduled for migration, please contact support and we will delay your migration.

Post-migration

After migration, if you completed all the Pre-migration checklist items, your dbt Cloud resources and jobs will continue to work as they did before.

You have the option to log in to dbt Cloud at a different URL:

• If you were previously logging in at cloud.getdbt.com, you should instead plan to login at us1.dbt.com. The original URL will still work, but you’ll have to click through to be redirected upon login.
• You may also log in directly with your account’s unique access URL.

Login with GitHub

Users who previously used the "Login with GitHub" functionality will no longer be able to use this method to login to dbt Cloud after migration. To continue accessing your account, you can use your existing email and password.