Moving Your Organization to Another Region

StackJack can move your entire organization — every ticket, connector, credential, automation, and usage record — from one StackJack region to another. Today that means moving from the US region to the EU region. When the move finishes, the independently verified target becomes your organization's authoritative home, and StackJack emails the owner the new addresses. One day after the move is verified, StackJack removes the old copy and checks that it is gone. Two small records stay on purpose: the directory entry and the migration evidence row.

There is no Region item in the sidebar. When your organization can move, the Dashboard shows a Move to another region card. Select See the details to open the Region page, or open it directly at /settings/region. If the card is absent or the Region page says a move is unavailable, one of the platform or organization readiness requirements has not been met yet; contact support rather than trying to start the move from another region.

If the Region page shows Page not found, moves are temporarily unavailable. If you already confirmed a move, or you are not sure of its state, contact support.

Who can start a move

The primary owner and co-owners can start a region migration. When the feature is enabled, Members and Administrators can see the page, but its destination choices and Start migration button are disabled and the page tells them to ask an owner.

Selecting a destination runs the readiness checks but does not start a move. The Start migration button becomes available only after every check passes.

What happens, step by step

1. An Owner selects the destination on the Region page (/settings/region). StackJack immediately checks that the source and destination are configured, the organization is homed here, no other move or data deletion is open, every run transcript deletion has finished, and an owner email is available. Every check must pass before Start migration is enabled. Selecting the destination does not move anything.
2. The Owner starts the request: select Start migration, type the organization's name exactly, and confirm. Nothing moves yet — this only sends a confirmation email.
3. The Owner gets a confirmation email with a single-use link. The email states the exact time the link expires (72 hours after the request). If you ignore the email, nothing happens — the request simply expires and your data stays where it is.
4. Clicking the link confirms the move. From this point your organization is read-only: everyone can still sign in and look at everything, but connector credential changes, subscription changes and new checkouts are refused with a message that says the move is in progress, AI tools connected through the old address stop answering, and scheduled automations don't run. Automations that were already running are allowed to finish.
5. StackJack copies everything to the new region and verifies the copy. Most moves complete within the same day. You can watch live progress on the Region page at /settings/region, and everyone sees a banner on the dashboard.
6. StackJack creates new regional sign-ins and attempts setup messages for active members. One active member — the highest-ranked one, an Owner ahead of an Administrator ahead of a Member — is made the new organization's administrator, and their credential message must be sent successfully before the migration can continue. Nobody has to open or accept it. Delivery failure for another member is recorded for support but does not strand the entire organization. StackJack's separate setup-guide message is queued and retried, but delivery can still fail. Sign-in accounts are created fresh in the new region — they are not transferred (see below).
7. StackJack clears the old copy one day after the move is verified. The irreversible scrub of the old region starts automatically once the new copy has passed every verification check and has waited one day; our team can also start it sooner. Every check runs again immediately before anything is deleted, and a check that fails stops the scrub. StackJack then checks that the old copy is gone.
8. The verified target becomes your authoritative home, and StackJack attempts a completion email to the owner address with the new Portal and MCP endpoint URLs. It is sent 30 to 90 minutes after the move is verified — a day before the old copy is cleared — and says the old copy is cleared automatically one day after the move. Email delivery does not determine whether the move is complete. If the message does not arrive, use the target-region addresses shown in the Portal or contact support rather than continuing to use the old endpoint.

Your sign-in starts over in the new region — passkeys included

Each StackJack region runs its own sign-in system. Your account in the new region is created new, it is not your old login moved over:

• StackJack attempts two messages for each active team member: a password-setup message from the sign-in provider and a StackJack message explaining the move. The provider message for the member chosen as the new organization's administrator — the highest-ranked active one — must send successfully or the move stops there; other provider-message failures are recorded, and the StackJack guide is retried before it is marked failed.
• If your organization has no active members at all when the copy is checked, the move stops before anything in the old region is touched: there would be nobody who could sign in to the new one.
• If an expected message is missing, open the target region's Portal, use Forgot password, or contact support. Do not infer that the move failed solely from a missing email.
• Set a new password, and if you use passkeys, register them again — passkeys are bound to the sign-in service that created them and cannot follow you across regions.
• Your old sign-in stops working once the move completes. Use the invitation and Portal address for the new authoritative home.
• The new region's portal has a different address (for the EU region: https://portal-eu.stackjack.io) — bookmark it. The completion message and StackJack setup guide carry it when those messages are delivered.

Team members who were deactivated before the move are carried over as deactivated and do not receive an invitation.

Reconnecting your AI tools after the move

Every AI tool needs its endpoint URL changed. Each region serves MCP from its own address (the EU region uses https://mcp-eu.stackjack.io), and a client left pointing at the old address does not get an error explaining the move — it simply stops finding your organization. Copy the new address from MCP Setup in the destination portal.

Beyond that, what each connection needs depends on how it authenticates, and the two kinds behave differently:

Why signed-in connections cannot simply follow the URL. An access token is bound to the region that issued it, so a token minted in the source region is refused by the destination — the tool's existing token and its background refresh both stop working. Signing in again at the destination mints a token that region accepts. For shared-app connections, your authorization moves with your organization but stays inactive until the app's own registration exists in the destination region, which the first sign-in there creates. If a shared app is refused right after the move, have one person sign in through it and try again. A shared-app authorization that was revoked before the move stays revoked at the destination: signing in again does not restore it, and an owner has to reinstate that person's access deliberately.

The identity side is separate and is covered above, under "Your sign-in starts over in the new region". Reconnecting an AI tool does not replace signing in to the destination portal.

Do not wait indefinitely for email: if the Portal shows completion but the message is missing, use the target endpoint shown there or contact support.

What moves, what's rebuilt, what stays behind

Everything moves: tickets, team members, connector configurations and their stored credentials, MCP clients, automations and agents (including any Anthropic API key you brought), the recorded test files behind your test scenarios, usage history, and archived audit records. Once the move is verified, the old region's copy of your files (ticket files, knowledge files and recorded test files) is deleted, along with the large tool results StackJack stored there for your automation runs.

Two technical records are intentionally retained after the target becomes authoritative:

• a small cross-region directory entry (your organization's owner email and account identifiers) that tells StackJack's sign-up and sign-in systems which region is home — so a teammate who signs in at the old address can be pointed the right way; the move updates that entry to name the target home;
• a technical migration evidence row (timestamps and verification receipts), kept as proof of the attempted move and scrub.

For what "region" means for your data day to day, see Data Residency.

While the move runs

• The portal is read-only for everyone in the organization, Owners and Administrators included: connector credential changes, subscription changes and checkouts are refused until the move completes, and reading still works.
• AI tools connected through the old address stop answering, and agents and scheduled automations are paused. When the move completes, reconnect with the address in the completion email.
• Anything written through the old endpoint during the move would land in the copy that is about to be deleted — which is why writes are refused rather than allowed to disappear.
• Turning someone's access off still works during the move, but a turn-off made after your data was copied does not reach the new region: the move carries the access you had switched off when the copy was taken. So after the move, repeat in the new region any turn-off you made while the move was running — a person's access to a connected app, or an AI client credential you revoked.
• The Owner can cancel at /settings/region up until the copy starts. After that the page offers no cancel. If the move stalls, contact support: our operators can end a parked move from their own console, which leaves your data in the old region untouched.
• If a move fails, the owner address gets one email saying so. Your organization stays in the region it was in, and the Region page says the move did not finish and whether anything was copied. If the same problem stops two moves within a day, a new attempt is paused until support tells you to try again.
• If you sign in to the destination region after a failed move, a banner says that copy is inactive and names the region where your organization is live. Changes made there are not saved. Our team removes that copy before you move again.

Related pages

• Data Residency
• Your MCP Endpoint
• Usage Data Retention
• Team Roles and Permissions