What You Actually Own When You Buy a Cloud Account
A cloud account is access to a provider relationship, not a title deed. Here is what genuinely transfers to you, what stays with the provider, and what to verify yourself.
Buying a cloud account is not like buying a server or a domain name. There is no deed, no registry entry, and no moment where a title moves from one name to another. What changes hands is access to a relationship that already exists between a provider and an account holder, together with whatever happens to be sitting inside that account at the moment you take it over.
That distinction sounds academic until something goes wrong. Knowing precisely where the line falls between your control and the provider’s control is the difference between a clean handover and a week of support tickets. This guide walks through what you genuinely hold after a transfer, what never moves, and the short list of things worth verifying yourself on day one.
The account is a relationship, not an asset
Every cloud account exists because a provider agreed to supply services to a named party under a set of terms. The account identifier, the console login and the billing profile are all artefacts of that agreement. When you take over an account, you step into the practical operation of that relationship. You do not automatically become the contracting party in the provider’s records unless the provider has a formal process for changing that, and most do.
The practical consequence is simple. Anything the provider can do under its terms, it can still do after you take over. It can suspend the account for non-payment, close it for abuse, require identity verification, or ask the original account holder to confirm something. Your position improves enormously if you move the account onto your own contact details and your own payment method as quickly as the provider allows.
It helps to think in terms of what a provider can verify. A provider can verify who pays, who answers the registered email, and who passes identity checks. It cannot verify who sits at the keyboard. Every durable improvement to your position therefore involves moving one of those verifiable facts onto you. Everything else is convention.
What transfers with the login
The useful part of a handover is the operational state. In most cases that means the console credentials, the root or owner email address if the seller agrees to release it, any projects or subscriptions already created inside the account, running resources and their data, configured networking, and the account’s accumulated history with the provider. That history matters more than people expect, because quota decisions and fraud scoring often lean on it.
Service limits travel with the account too. An account that has been active for a while and has paid a few invoices often carries higher default allowances than a brand new signup. If that is part of what you are paying for, read how service limits and quotas work before you assume the numbers in a listing are stable, because quotas are set per account per region and can be reviewed at any time.
What does not transfer
Several things stay exactly where they were. The provider’s terms of service do not bend for a new operator. Any identity verification tied to the original holder remains tied to them until the provider accepts new documentation. Support entitlements bought under a named contract may not follow. Promotional pricing granted to a specific organisation is often tied to that organisation rather than to the account number.
Neither does legal responsibility for what the account did before you arrived. If the account has a history of abuse reports, that history sits in the provider’s systems regardless of who holds the password today. This is why reading a listing carefully matters, and why we wrote a separate walkthrough on how to read a cloud account listing rather than burying it here.
The provider’s terms sit above everything
No marketplace, broker or seller can grant you rights that the provider has not granted. Some providers describe account transfers in their documentation and offer a supported path. Others treat the account as personal to the registered holder. The difference is material, and it is worth checking the provider’s current published terms yourself rather than taking anyone’s summary of them.
Where a provider offers an organisation or billing account structure, use it. Moving a project under an organisation you control, or inviting your own identity as an owner and then removing the previous one, gives you a durable position that a shared password never will. Providers with strong organisation models, including Google Cloud and Amazon Web Services, make this reasonably straightforward once you know where the controls live.
Resources, data and the control plane
Think of an account as having two layers. The control plane is the set of permissions, policies, keys and billing settings that decide who may do what. The data plane is the running machines, the stored objects, the databases and the traffic. A handover gives you both, but they need different treatment, and conflating them is how people end up with a locked down console sitting on top of a wide open bucket.
On the control plane, assume nothing is clean. Keys may exist that nobody mentioned. Roles may grant more than their names suggest. On the data plane, assume nothing is yours until you have inspected it. Volumes and buckets inherited from a previous operator may contain someone else’s data, which is a privacy problem as much as a cost problem. Decide early whether you are keeping any of it, and if not, remove it deliberately rather than letting it sit.
Credits are a provider balance, not your property
Credits deserve their own warning. A credit balance is an entry in the provider’s billing system that the provider controls. It expires. It frequently excludes certain services, certain regions, or certain purchase types such as reserved capacity and third party marketplace software. It can be withdrawn if the provider decides the terms under which it was issued were not met.
So treat any credit figure in a listing as a claim to be tested, not a number to be banked. The only figure that counts is the one the provider’s own billing console shows after the account is in your hands. Our guide on verifying cloud credits before and after a transfer covers where each console displays the balance and which fields actually matter.
Where your responsibility starts
The moment you hold working credentials, you own the consequences of what runs under them. That includes the bill. An inherited account can be quietly spending money on resources you have not looked at yet, in regions you did not think to check. It can also be exposed in ways you did not create, through open security groups or long lived keys.
Work through the post handover security checklist in the first day rather than the first month. If the account came with API keys or a root email you do not fully control, the companion piece on securing an inherited account goes deeper on credential hygiene specifically.
Questions worth asking before you buy
A short set of questions separates a usable account from an expensive problem. Who is the registered holder, and will the root email be released to you? Has the account passed identity verification, and in which country? Is there a payment method attached that is not yours, and can it be removed? Are there running resources, and who pays for them during the handover window?
Then ask what you are actually buying for. If you want a specific provider because of pricing shape rather than account history, a direct signup may serve you better. Comparisons such as AWS against Hetzner are useful here, because the right answer sometimes is that you do not need an aged account at all, just a cheaper platform.
A realistic summary
You own the operational control of an account, the resources inside it, and the obligations that come with both. You do not own the provider’s goodwill, the terms, the verification status of someone else, or a credit balance that the provider can change. Everything in the first group is yours to secure immediately. Everything in the second group is a risk to price in rather than a feature to pay extra for.
Buyers who treat an account as a working system to be audited, rather than a product to be unwrapped, almost never get caught out. Pick one provider, learn its console properly, and only then add a second. Depth on one platform beats shallow familiarity with four, because the controls that matter during a handover are always the ones buried two menus deep.
One last framing that tends to stick. An account you bought is worth exactly what you can still do with it after the provider reviews it tomorrow. If the answer to that question depends on someone else’s documents, someone else’s card, or someone else’s mailbox, you do not yet own very much. Spend your first day closing those three gaps and the rest of the question answers itself.