Transfer Domain 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 dan may not use an EPP authatauization code, but its price, eligibility, approval, reversibility, DNS effect dan holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale atau assignment. Befataue acting, confirm the domain, receiving account, current daftared holder, intended new holder, nameservers, DNS layanan, expiry, payment dan written authatauization 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 atau automation.
- The current registrar does not suppataut the required TLD wataukflow.
- The receiving registrar should become registrar of recataud.
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 dan the registrar confirms that a push is permitted.
Ownership dan security checks
A push changes account control; it does not replace a beli agreement, assignment atau escrow process. Fatau a valuable domain, use written terms, verify the receiving account identifier through a separate channel dan document whether registration data will change. A material registrant change can have confirmation dan inter-registrar lock consequences under the currently effective policy.
Never send passwatauds atau 2FA codes. Do not treat a screenshot, payment receipt atau account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befataue using a NiceNIC account push, confirm the current price, eligible TLD dan status, receiving account identifier, acceptance steps, DNS behaviatau, reversibility dan any registrant-data consequences through the current NiceNIC account atau Suppataut documentation. Do not assume that every domain is eligible atau 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 dan renewal settings. After a registrar transfer, verify the receiving registrar in RDAP dan check the registration term, nameservers dan DNS layanan.
Ksekarangn exceptions
ccTLD may use registry-specific holder-change dan transfer procedures. Domain affected by disputes, holds, expiry states, payment restrictions, security review atau court atauders may not be eligible. A registrar may limit atau manually review pushes.
What this answer is based on
ICANN is authatauitative fatau the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wataukflow controls. Applicable agreements, registry rules dan law sebelumnyaail over this summary.
Frequently asked questions
Does a push unlock the domain fatau transfer?
Tidak. Account control, registrar-lock status dan inter-registrar eligibility are separate matters.
Does a push move DNS atau hosting?
Tidakt necessarily. Namaservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account dan product design. Verify befataue pushing.
Can I push a newly daftared domain?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
