> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/aws-onboarding/moving-to-a-new-payer-account.md).

# Moving to a New AWS Payer Account or Organization

If you are an existing Archera customer moving to a new AWS organization or management (payer) account, connect the new payer to Archera before moving your existing AWS accounts. Then coordinate the move of your accounts and any Archera Guaranteed Reserved Instance (GRI) subaccounts so that your commitments and the usage they cover arrive in the new organization together.

## 1. Onboard the new payer account to Archera

As soon as you have access to the new AWS organization and its payer account, add it as a **new top-level AWS integration in your existing Archera organization**, in advance of moving your other accounts.

1. Open **Settings → Integrations** in Archera and add a new AWS integration.
2. Sign in to the new AWS management (payer) account and complete the guided onboarding flow. The recommended connection method is CloudFormation.
3. Verify the installation to confirm that Archera can access the new payer account.

Keep the existing payer integration in place during the migration. For connection details, see the [Archera QuickStart Guide for AWS](https://docs.archera.ai/help-center/user-guide/quickstart-aws.md).

## 2. Invite your existing accounts to the new AWS organization

When you are ready to finish the migration, send AWS Organizations invitations from the new organization to:

* Your existing AWS accounts that are moving, including accounts with usage or commitments.
* Any **Archera GRI subaccounts that contain commitments** for your organization.

Include the GRI subaccounts in your migration plan even if they do not run workloads. They hold commitments that cover usage in your other accounts. For AWS prerequisites and invitation instructions, see [Migrating an account to another organization](https://docs.aws.amazon.com/organizations/latest/userguide/orgs_account_migration.html).

## 3. Coordinate the migration time with Archera support

**If you have GRI subaccounts, contact** [**Archera support**](mailto:support@archera.ai) **before moving your accounts.** Let the team know when you plan to migrate and which accounts are moving. Include the new payer account ID, the GRI subaccount IDs, and your planned migration date, time, and time zone.

Archera support will coordinate the GRI subaccounts joining the new organization alongside your accounts with usage. Agree on the timing with support before proceeding.

Minimizing the gap between these moves is important: while your usage accounts and the GRI subaccounts are in different organizations, the commitments cannot provide shared coverage for that usage. Coordinating the move minimizes the risk of a lapse in coverage.

## 4. Complete the coordinated move

At the agreed migration time, have your existing accounts accept the invitations and join the new AWS organization. Archera support will coordinate the GRI subaccounts joining with as little time between the moves as possible.

Once your usage accounts and all accounts holding their commitments have joined, your migration to the new organization is complete. The commitments remain in the accounts that hold them and move with those accounts to the new organization. With commitment discount sharing enabled, they can continue covering eligible usage there.

Confirm that Archera can see the migrated accounts and commitments under the new integration. If you have GRI subaccounts, confirm completion with Archera support.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.archera.ai/help-center/aws-onboarding/moving-to-a-new-payer-account.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
