Migrating your account from EU to US region

Last updated: November 2, 2026

Migrating from the EU region to the US region is not a simple region switch — it involves setting up a new US account and transferring your configuration over. This article outlines what that process looks like and what to expect.

What the migration involves

On our end, we can help you scope and plan the cutover. On your side, the main work involves reconnecting everything tied to your current EU account, including:

  • SSO configuration

  • Version control system (VCS) integrations

  • Cloud integrations (e.g., AWS, Azure, GCP roles)

  • Worker pools

  • Contexts and secrets

  • API keys

  • Webhooks and any automations pointing at the EU account

State will also need to be migrated. Note that run history from the EU account will not carry over to the new US account.

Pros and cons

Pros

Cons

US data residency

Significant effort, especially for resources not managed as code

Lower latency if your team and infrastructure are primarily US-based

Run history remains in the EU account

Tips for a smoother migration

  • Use Infrastructure as Code (IaC): Managing your resources as code significantly reduces the manual effort involved in recreating configuration in the new account.

  • Run both accounts in parallel: You can keep the EU account active while you set up and validate the US account, allowing for a controlled cutover.

  • Plan ahead: Reach out to our team before starting so we can assist with scoping and planning the migration.