Not every domain move is a transfer to a new registrar — sometimes you need to move a domain between two accounts at the same registrar, which is a different and usually much simpler process. This ‘account transfer’ or ‘internal transfer’ or ‘push’ is what you use to hand a domain to a client, move it between your own accounts, or receive one from someone else, all without the domain leaving the registrar. This guide explains how account transfers work, how they differ from registrar transfers, and how to do one smoothly.

You will learn what an account transfer (internal push) is and how it differs from a registrar transfer, when you would use one, how the process generally works, what information you need from the other account, why it is usually faster than a registrar transfer, and the common pitfalls to avoid. By the end you will be able to move a domain between accounts at the same registrar confidently, whether you are sending or receiving it.

What an account transfer is

An account transfer — also called an internal transfer, an account change, or a ‘push’ — is the process of moving a domain from one account to another account at the same registrar. The domain stays with the registrar throughout; only the account that owns and manages it changes. This is fundamentally different from a registrar transfer, which moves the domain’s registration to a different registrar entirely.

Because the domain does not leave the registrar, an account transfer sidesteps most of the machinery of a registrar transfer. There is typically no auth/EPP code involved, no 60-day rule in the same way, and no multi-day inter-registrar process — the registrar simply reassigns the domain from one of its accounts to another within its own system. It is an internal administrative change, which is why it is usually far simpler and faster.

So an account transfer is moving a domain between accounts at the same registrar, as opposed to moving it between registrars. Recognising which kind of move you actually need is important, because the process, requirements, and speed are quite different. If your goal is to hand a domain to someone else’s account at the same registrar (or move it between your own accounts there), an account transfer — not a registrar transfer — is the right, and simpler, tool.

How it differs from a registrar transfer

The differences between an account transfer and a registrar transfer are worth laying out clearly, since confusing the two leads to using the wrong process:

• Where the domain ends up: account transfer keeps the domain at the same registrar (different account); registrar transfer moves it to a different registrar.
• Auth code: an account transfer usually needs no auth/EPP code; a registrar transfer always does.
• Speed: account transfers are often near-instant or quick; registrar transfers take up to five to seven days.
• The 60-day rule: generally does not block an account transfer the way it blocks a registrar transfer (though the registrar’s own policies may vary).
• Fee: account transfers are often free or low-cost, since there is no year-adding renewal like a registrar transfer’s fee.

The through-line is that an account transfer is a lighter, internal operation, while a registrar transfer is the heavier, standardised inter-registrar process with all its prerequisites and timing. This is good news when an account transfer is what you need: it avoids the auth code, the waiting period, and the fee structure of a registrar transfer. The key is simply identifying that both accounts are at the same registrar, in which case the account transfer is the appropriate and much simpler path.

When you’d use an account transfer

Account transfers are the right tool in several common situations. The most frequent is handing a domain to a client: if you registered a domain on behalf of a client (in your own account) and now want to give them ownership in their own account at the same registrar, an account transfer (push) moves it to their account cleanly. Similarly, receiving a domain from someone — a client, a partner, a previous owner — into your account works the same way.

Another common use is reorganising your own domains: if you manage multiple accounts at the same registrar, you can use account transfers to move domains between them for consolidation or organisation. And in a sale or handover of a website or business, if buyer and seller both use the same registrar, an account transfer is a simple way to move the domain to the new owner without the complexity of a full registrar transfer.

So you use an account transfer whenever the domain needs to change hands (or accounts) but stays at the same registrar — client handovers, receiving a domain, reorganising your own accounts, or a same-registrar sale. If, on the other hand, the domain needs to end up at a different registrar, that is a registrar transfer instead (possibly in addition to an account change). Matching the situation to the right kind of move is the first step, and for same-registrar account changes, the account transfer is both correct and easy.

How the process generally works

While the exact steps vary by registrar, an account transfer generally works by one account initiating a push of the domain to another account, which the receiving account then accepts. The sending account typically goes to the domain, chooses an option like ‘transfer to another account’, ‘push domain’, or ‘change account’, and specifies the recipient — usually by their account username or the email associated with their account at that registrar.

The receiving side then usually confirms or accepts the incoming domain, often via an email notification or a pending-transfer item in their account, at which point the domain moves into their account. Some registrars complete the push immediately once initiated with the correct recipient details; others require the explicit acceptance step as a confirmation. Either way, it is an internal reassignment handled within the registrar’s own system.

So the general process is: the sender initiates the push to the recipient’s account (identified by username or email), and the recipient accepts it, after which the domain is in the new account. Because registrars implement this differently, checking your specific registrar’s help documentation for its exact ‘push’ or ‘account transfer’ steps is worthwhile — but the shape is always this sender-initiates, recipient-accepts pattern, which is much simpler than the multi-step registrar transfer.

What you need from the other account

To do an account transfer, you need a specific piece of identifying information about the other account — and knowing what to ask for in advance smooths the process. Most commonly, the sender needs the recipient’s account identifier at that registrar: typically their account username or the email address registered to their account. The push is directed to that identifier, so it must be correct.

This means coordination between the two parties: if you are sending a domain, get the recipient’s exact registrar account username or email; if you are receiving, provide yours to the sender (and make sure you actually have an account at that registrar to receive into — creating one first if needed). An incorrect recipient identifier is the main thing that causes an account transfer to go to the wrong place or fail, so confirming it precisely matters.

So what you need is the correct account identifier for the other party (username or email at that registrar), plus, for the recipient, an existing account there to receive the domain. Coordinating this information beforehand — the sender knowing exactly where to push, the recipient ready to accept — is what makes the account transfer go smoothly. It is a small amount of information, but getting it exactly right is the key practical detail, since the whole push is directed by that identifier.

Common pitfalls to avoid

A few pitfalls trip up account transfers, and all are easy to avoid once known. The first is confusing an account transfer with a registrar transfer — trying to use an auth code and the inter-registrar process when both accounts are at the same registrar (which needlessly complicates things), or conversely expecting an account-transfer push to move a domain to a different registrar (which it cannot). Match the process to whether the registrar changes.

The second is getting the recipient identifier wrong, sending the push to the wrong username or email, or to an account that does not exist — so double-check the recipient’s exact account details. The third is DNS: even though the domain stays at the same registrar, confirm after the account transfer that the DNS records are intact and the domain still points where it should, since account or management changes can occasionally affect settings — the same ‘preserve and verify DNS’ discipline that applies to any domain move.

So avoid these pitfalls by: correctly identifying whether you need an account transfer (same registrar) or a registrar transfer (different registrar), confirming the recipient’s exact account identifier, and verifying DNS after the move. Handled with these in mind, an account transfer is a quick, clean way to move a domain between accounts — often near-instant, with no auth code or multi-day wait — which is exactly why it is the right tool for same-registrar handovers, once you have identified that the same registrar is involved on both sides.

FAQs

How do I transfer a domain between accounts at the same registrar?

Use an account transfer (also called an internal transfer or ‘push’), not a registrar transfer. Generally, the sending account initiates a push of the domain to the recipient’s account — specifying them by their account username or email at that registrar — and the receiving account accepts it. The domain then moves into the new account, staying at the same registrar. Check your registrar’s specific ‘push’ or ‘account transfer’ steps, as they vary.

What’s the difference between an account transfer and a registrar transfer?

An account transfer moves a domain between two accounts at the SAME registrar; a registrar transfer moves it to a DIFFERENT registrar. The account transfer is much simpler: usually no auth/EPP code, often near-instant rather than 5-7 days, frequently free or low-cost, and generally not blocked by the 60-day rule. A registrar transfer is the heavier standardised process with all its prerequisites. Match the process to whether the registrar changes.

When would I use an account transfer?

Whenever a domain needs to change accounts but stay at the same registrar: handing a domain to a client’s account, receiving a domain from someone, reorganising domains between your own accounts, or a website/business sale where buyer and seller use the same registrar. If the domain needs to end up at a different registrar, that’s a registrar transfer instead. For same-registrar account changes, the account transfer is the correct, simpler tool.

Do I need an auth code for an account transfer?

Usually no — an account transfer (internal push) at the same registrar typically doesn’t involve an auth/EPP code, unlike a registrar transfer which always does. The registrar reassigns the domain within its own system based on the recipient’s account details, not an auth code. This is one of the ways account transfers are simpler and faster than registrar transfers. Check your specific registrar’s process, as implementations vary.

What information do I need to push a domain to another account?

The recipient’s account identifier at that registrar — usually their account username or the email registered to their account. The push is directed to that identifier, so it must be exactly correct. The recipient also needs an existing account at that registrar to receive the domain. Coordinate this beforehand: the sender needs the recipient’s exact details, and the recipient should be ready to accept the incoming domain.

Is an account transfer faster than a registrar transfer?

Yes, usually much faster — often near-instant or quick, because the domain never leaves the registrar; it’s just reassigned between accounts within the registrar’s own system. A registrar transfer, by contrast, takes up to five to seven days due to the standardised inter-registrar process and its security waiting period. The account transfer avoids that waiting period entirely, along with the auth code and (usually) the fee.

The bottom line

Moving a domain between two accounts at the same registrar — an account transfer, internal transfer, or ‘push’ — is a different and much simpler operation than transferring to a new registrar, and recognising which one you actually need is the first and most important step. An account transfer keeps the domain at the same registrar and merely changes which account owns and manages it, so it sidesteps almost all the machinery of a registrar transfer: typically no auth/EPP code, no multi-day inter-registrar waiting period, often no fee, and generally no 60-day-rule block. It is an internal administrative reassignment, which is why it is usually quick, often near-instant. A registrar transfer, by contrast, is the heavier standardised process for moving a domain to a different registrar entirely, with all its prerequisites and timing.

You reach for an account transfer whenever a domain needs to change hands or accounts but stay at the same registrar — handing a domain to a client, receiving one from someone, reorganising your own accounts, or a same-registrar sale. The process follows a consistent shape across registrars: the sending account initiates a push to the recipient’s account (identified by their exact username or email at that registrar), and the recipient accepts it, after which the domain sits in the new account. The main things to get right are identifying the correct process (same registrar means account transfer, not registrar transfer), confirming the recipient’s exact account identifier so the push goes to the right place, and verifying your DNS is intact afterward with the same preserve-and-verify discipline any domain move deserves. Get those right, and an account transfer is a fast, clean handover — exactly the right, simple tool for moving a domain between accounts at the same registrar.

When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. To move a domain between accounts at the same registrar, use an account transfer (‘push’) — not a registrar transfer. The sending account pushes the domain to the recipient’s account (identified by their username or email at that registrar), and the recipient accepts it. It’s usually near-instant, with no auth code, no 5-7 day wait, and often no fee, since the domain never leaves the registrar. Confirm the recipient’s exact account identifier, match the process to whether the registrar changes, and verify DNS afterward.