How do I move accounts between organizations in AWS Organizations?
Last updated: 2019-04-23
I plan to migrate member accounts from one organization to another organization. What should I consider before starting the migration process?
When planning your migration, keep the following in mind:
- You have the permissions you need to move both the master and member accounts in the organization.
- You have a plan to address any charges that are incurred while the accounts are migrating.
- You have backed up any reports or billing history that you need to keep.
- You have a plan to update the tax information for any accounts that are changing organizations.
- You fully understand the technical process of migrating accounts.
Account access considerations
You must have root or IAM access to both the member and master accounts. For more information on adding these permissions, see Authentication and Access Control for AWS Organizations.
You might need to add more information to a member account before you can move it. For example, you might need to add a new payment method to the member account, or update the contact information for the account. When you remove the account from the organization, you are prompted to add this information. For more information, see Removing a Member Account from Your Organization.
Before migrating, decide what set of features you want for your organization. By default, organizations support consolidated billing features. To access additional features such as service control policies (SCPs), enable all features.
When a member account leaves an organization, all charges incurred by the account are charged directly to the standalone account. Even if the account move only takes a minute to process, it is likely that some charges will be incurred by the member account.
Be sure that you have a plan to address these charges. For example, you might add a credit card to the member account to cover the charges. Then, plan an internal process to reimburse the linked account for using its own payment method during the migration. For instructions, see Managing Your AWS Payment Methods.
If you need help updating the payment method for your account, contact AWS Support.
When it is added to the new organization, charges will again be billed to the master account.
If you currently benefit from a volume discount, you might temporarily pay the normal rate for that service. This is because you have changed billing entities, and your new consolidated billing family might not have reached the higher usage tier necessary to activate the volume discount. Be sure to plan for this temporary change in pricing.
Billing history and billing reports for all accounts stay with the master account in an organization. Before you move the account to a new organization, download any billing or report history for any member accounts that you want to keep. This might include Cost and Usage Reports, Detailed Billing Reports, or reports generated by Cost Explorer.
You might need to update the tax settings on member accounts after you move them.
To view and edit the tax registration numbers for all member accounts in the organization, you must sign in as the master account.
Planning the migration process
- If you have only a few accounts to migrate, you can use the AWS Organizations console.
- If you are migrating many accounts, you might use the AWS Organizations API or AWS Command Line Interface (AWS CLI) to move the accounts instead.
In either case, plan how you will do the following with each member account:
- Remove the member account from the old organization.
- Send an invite from the new organization.
- Accept the invite to the new organization from the member account.
If you want the master account of the old organization to also join the new organization, do the following:
- Remove the member accounts from the organization using the preceding process.
- Delete the old organization.
- Repeat the preceding process to invite the old master account to the new organization as a member account.