Domain transfer service in Japan – move registrars without downtime

What a domain transfer is – and what it is often confused with

A domain transfer moves your domain from one registrar (the company you pay renewals to) to another. Several related tasks sound similar, and knowing which one you actually need saves time.

• Domain transfer: the registrar and admin panel change. The domain name stays the same
• Nameserver change: you switch where DNS – the domain's address book – is managed. This works without a transfer
• Hosting migration: website files and mailboxes move to a new server. The registrar can stay as it is
• Registrant change: the legal owner of the domain is updated. This comes first if your agency registered the domain in its own name

If you are changing agencies and only moving the website to new hosting, a transfer is optional. If the domain sits in the agency's account, though, bringing it back under your control through a transfer or registrant change is a smart move. For the basics, see setting up your own domain.

When a transfer makes sense, and what to check first

These are the usual reasons to move a domain, followed by the points worth checking before you start.

• A former agency or ex-employee manages the domain and you have no login
• Hosting and domain are with different providers, with renewals and invoices all over the place
• Your registrar raised its renewal price or its admin panel is hard to use
• You want several domains in a single account
• You are switching shop or booking platforms and want to clean up DNS at the same time

Check three things: whether the domain is registered in your company's name, whether there is enough time left before it expires, and where DNS is currently managed. Registrars often refuse transfers close to expiry or after it, so renew first if the date is near. If it has already lapsed, see what to do when a domain expires.

How to transfer a domain in six steps

Screens differ between .com, .jp and other extensions, but the process typically looks like this and takes a few days to about a week from request to completion.

• Record your current DNS: write down every A, CNAME, MX and TXT record (including SPF and DKIM)
• Prepare DNS at the destination: recreate the same records at the new registrar or an external DNS service
• Unlock the domain: turn off the registrar or transfer lock in the current admin panel
• Get the auth code: for gTLDs such as .com, request the AuthCode (EPP code). For .jp, follow your registrar's procedure
• Request the transfer: enter the domain and code at the new registrar and pay the fee
• Approve and verify: confirm the approval email sent to the registrant, then test the site, email and SSL

The order of steps 1 and 2 is what keeps everything online. When the destination already serves the same DNS records before the switch, your site and inbox keep working throughout.

Typical costs and timing

The main cost is the transfer fee set by the new registrar. For gTLDs such as .com, it is typically close to one year's renewal and sometimes discounted; .jp and .co.jp are usually priced higher. A gTLD transfer normally adds one year to the expiry date, so the fee works much like a prepaid renewal.

• Transfer fee: check the destination's price list – it varies by extension
• DNS and email: if you rely on the old registrar's free DNS or email forwarding, you need a replacement at the destination
• Timing: a few days to a week, longer if the approval email waits in an old inbox
• Lock period: gTLDs generally cannot be transferred within 60 days of registration or a previous transfer

When comparing quotes for a transfer service, check that DNS migration and post-switch testing are included in the price.

Common transfer mistakes and how to avoid them

Most transfer problems trace back to preparation steps that were skipped before or after the request.

• The old registrar's free DNS disappears with the transfer and the website stops loading
• MX or SPF records are not copied, so email bounces or lands in spam
• The registrant email is outdated, the approval message is never seen and the request is cancelled
• The request is made days before expiry, the transfer misses the date and you pay for an auto-renewal as well
• Verification TXT records for Google Search Console or Microsoft 365 get deleted

The fix is straightforward: export every DNS record before you start, update the registrant email to an address you read, and request the transfer well ahead of expiry. After the switch, actually load the site, submit the contact form and send and receive a test email.

How UNANOBO handles your domain transfer

UNANOBO takes care of the transfer on your behalf: exporting your DNS, recreating it at the destination, filing the request and testing everything after the switch. The domain ends up registered in your name and in your own account, so you stay in control whoever works on your site in the future.

Transfers often come up alongside a website renewal or an agency change. If you are thinking about a new site, we first build a free demo based on your current one, and you decide whether to go ahead after seeing it. The founder handles every project personally, from the first message to growth after launch, and everything runs by message in Japanese or English. For the bigger picture, see changing your web agency.