Domain Transfer vs Account Push: Which Do You Need?
Policy status notice
The current ICANN Transfer Policy remains in effect on September 1, 2026. The ICANN Board approved new Transfer Policy Review recommendations on June 7, 2026, but implementation is pending. Account pushes remain registrar-specific.
Direct answer
Use an inter-registrar transfer when the domain must move to a different registrar. Use an account push when control should move between two accounts at the same registrar. A push is often faster and may not use an EPP authorization code, but its price, eligibility, approval, reversibility, DNS effect and holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale or assignment. Before acting, confirm the domain, receiving account, current registered holder, intended new holder, nameservers, DNS service, expiry, payment and written authorization from the relevant parties.
Compare the operations
Use an inter-registrar transfer when
- The receiving party requires a different registrar.
- You are consolidating billing, controls or automation.
- The current registrar does not support the required TLD workflow.
- The receiving registrar should become registrar of record.
Use an account push when
- Both parties will continue using the same registrar.
- The registrar provides a documented, verified push process.
- A separate account should control the domain without changing registrar.
- An external transfer is currently unavailable and the registrar confirms that a push is permitted.
Ownership and security checks
A push changes account control; it does not replace a purchase agreement, assignment or escrow process. For a valuable domain, use written terms, verify the receiving account identifier through a separate channel and document whether registration data will change. A material registrant change can have confirmation and inter-registrar lock consequences under the currently effective policy.
Never send passwords or 2FA codes. Do not treat a screenshot, payment receipt or account push alone as conclusive proof of legal ownership.
NiceNIC account push
Before using a NiceNIC account push, confirm the current price, eligible TLD and status, receiving account identifier, acceptance steps, DNS behavior, reversibility and any registrant-data consequences through the current NiceNIC account or Support documentation. Do not assume that every domain is eligible or that the process is free merely because it is internal.
Expected result
After a push, verify that the domain appears in the intended account with the expected registration data, nameservers, lock and renewal settings. After a registrar transfer, verify the receiving registrar in RDAP and check the registration term, nameservers and DNS service.
Known exceptions
ccTLDs may use registry-specific holder-change and transfer procedures. Domains affected by disputes, holds, expiry states, payment restrictions, security review or court orders may not be eligible. A registrar may limit or manually review pushes.
What this answer is based on
ICANN is authoritative for the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented workflow controls. Applicable agreements, registry rules and law prevail over this summary.
Frequently asked questions
Does a push unlock the domain for transfer?
No. Account control, registrar-lock status and inter-registrar eligibility are separate matters.
Does a push move DNS or hosting?
Not necessarily. Nameservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account and product design. Verify before pushing.
Can I push a newly registered domain?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
