Effects of Converting an Account and Conversion Steps

3. Select the **More options** menu and then select **Leave organization**. If the user account is the sole owner of any organization or company, assign another user the owner role and then remove yourself from the organization or company. - You must have a separate Docker ID ready to assign as the owner of the organization during conversion. If you want to convert your user account into an organization account and you don't have any other user accounts, you need to create a new user account to assign it as the owner of the new organization. With the owner role assigned, this user account has full administrative access to configure and manage the organization. You can assign more users the owner role after the conversion. ## Effects of converting an account into an organization Consider the following effects of converting your account: - This process removes the email address for the account, and organization owners will receive notification emails instead. You'll be able to reuse the removed email address for another account after converting. - The current subscription will cancel and your new subscription will start. - Repository namespaces and names won't change, but converting your account removes any repository collaborators. Once you convert the account, you'll need to add those users as team members. - Existing automated builds will appear as if they were set up by the first owner added to the organization. See [Convert an account into an organization](#convert-an-account-into-an-organization) for steps on adding the first owner. - The user account that you add as the first owner will have full administrative access to configure and manage the organization. - To transfer a user's personal access tokens (PATs) to your converted organization, you must designate the user as an organization owner. This will ensure any PATs associated with the user's account are transferred to the organization owner. > [!TIP] > > To avoid potentially disrupting service of personal access tokens when converting an account or changing ownership, it is recommended to use [organization access tokens](/manuals/security/for-admins/access-tokens.md). Organization access tokens are associated with an organization, not a single user account. ## Convert an account into an organization 1. Ensure you have removed your user account from any company or teams or organizations. Also make sure that you have a new Docker ID before you convert an account. See the [Prerequisites](#prerequisites) section for details. 2. Sign in to [Docker Home](https://app.docker.com/login). 3. In Docker Home, select your avatar in the top-right corner to open the drop-down. 4. Select **Account settings**. 5. Select **Convert**. 6. Review the warning displayed about converting a user account. This action cannot be undone and has considerable implications for your assets and the account. 7. Enter a **Username of new owner** to set an organization owner. This is the user account that will manage the organization, and the only way to access the organization settings after conversion. You cannot use the same Docker ID as the account you are trying to convert. 8. Select **Confirm**. The new owner receives a notification email. Use that owner account to sign in and manage the new organization.

This section outlines the effects of converting a Docker Hub user account to an organization, including email address changes, subscription cancellations and restarts, removal of repository collaborators, and the assignment of full administrative access to the first owner. It recommends using organization access tokens instead of personal access tokens to avoid service disruption. The section then provides step-by-step instructions on how to convert the account via Docker Home, including ensuring prerequisites are met, reviewing the warning, entering the username of the new owner, and confirming the conversion.