How to Push a Domain to Another Account at the Same Registrar
VigilDog Team · October 18, 2026 · 6 min read
You need to move a domain from one account to another, a client handing you their domain, consolidating two logins, or splitting a portfolio after a sale, but both accounts live at the same registrar. You do not want a full registrar transfer with its 60-day locks and auth codes. What you want is a domain account change push: an internal move that keeps the domain exactly where it is and only changes who owns the account it sits in.
Push vs transfer: know which one you need
These are two different operations and mixing them up causes most of the pain. A registrar transfer moves a domain from one registrar company to another (say, GoDaddy to Namecheap). It requires unlocking the domain, an EPP/auth code, and it triggers ICANN's rules, including the 60-day lock after a recent registration or previous transfer.
A push, variously called an account change, account move, or change of account, moves a domain between two accounts at the same registrar. The registrar of record does not change, so most registrars treat it as an internal operation: faster, usually free or cheap, and generally not blocked by the 60-day inter-registrar transfer lock. If the goal is 'get this domain into a different login at the same company', a push is the tool.
Before you start: check eligibility
A push is simple, but a few conditions will stop it. Walk this list first so you are not halfway through when it fails.
One nuance worth flagging: a push changes the account holder, and depending on how the registrar records ownership, it can also change the registrant contact in WHOIS. A registrant change can itself start a 60-day lock on outbound inter-registrar transfers under ICANN's Transfer Policy. That does not block the push, but if you plan to move the domain to a different registrar soon after, do the push first and the transfer later, not the other way around.
- The domain is not expired or in redemption, renew it first if it is close
- Both accounts are at the same registrar and in good standing
- You have the exact receiving account's identifier (account number, email, or customer ID) the registrar requires
- The domain is unlocked if your registrar requires it for account moves (many do not)
- You know whether the registrar charges a small push fee or requires the receiver to accept
How to push at the major registrars
The exact label differs, but the flow is the same: the sender initiates, the receiver confirms. GoDaddy calls it 'Account Change'under Domain Settings you enter the receiving GoDaddy customer's account details, and they receive a request to accept. Namecheap uses a 'Change Ownership' / push flow where you enter the recipient's Namecheap username; the domain moves once they accept. Cloudflare Registrar does not support account-to-account pushes at all, there you must do a full transfer out and back, which is a different, slower path.
Squarespace Domains (formerly Google Domains) and Porkbun each have their own transfer-to-another-account option in the domain's management screen. Whatever the brand, look for 'move', 'push', 'change account', or 'transfer to another account here'wording that stays inside the registrar rather than mentioning auth/EPP codes, which signal an inter-registrar transfer instead.
Whichever registrar you are on, read their specific help article for that exact button before clicking. The steps below are the general shape, not a substitute for the registrar's own confirmation screen.
Keep DNS and email running during the change
The best news about a push: it does not touch your DNS. Because the registrar of record stays the same and the nameservers are a property of the domain, not the account, your A records, MX records, and everything else keep resolving throughout. Websites stay up, email keeps flowing. This is the single biggest advantage over a full transfer, where nameservers can reset to registrar defaults and knock services offline if you are not careful.
That said, verify rather than assume. Right before the push, record the current nameservers and the critical records, A/AAAA for the site, MX and any SPF/DKIM/DMARC TXT records for mail. You can capture the DNS state quickly with our DNS checker. Right after the push completes, run the same check and confirm nothing moved. If the receiving account has a default DNS template or parking setting, that is the one place a careless registrar could override records, catching it in minutes beats discovering it from a bounced-email complaint.
After the push: verify ownership, contacts, and expiry
Once the receiver accepts, do a short close-out pass. Confirm the domain now appears in the destination account and is gone from the source. Check the WHOIS registrant, admin, and technical contacts, a push often carries over the old contacts, and if this move was a client handover, the new owner's details belong there. Re-enable auto-renew in the new account; it does not always survive the move, and a domain that silently stops renewing is the most expensive kind of mistake.
Finally, make sure the expiry date is being watched by someone. Ownership moves are exactly when domains fall through the cracks, the old owner stops paying attention and the new one assumes it is handled. Confirm the renewal date with our domain expiry checker, and if you are not sure how registrar expiry, grace, and redemption periods stack up, our guide on when your domain expires lays out the timeline.
Make the new owner the one who never forgets
A push is quick; the risk lives in the weeks afterward, when everyone assumes someone else has an eye on renewal and DNS. The clean handoff is not just moving the account, it is making sure the domain's expiry, nameservers, and email records are actively monitored under the new owner.
VigilDog monitoring tracks domain expiry, DNS drift, and email records across every domain in a portfolio, so a domain that just changed hands is watched from day one, no matter which login it now lives in.