Transferring a domain to ITA Network Solutions from another registrar is usually straightforward, but the safest result depends on completing each step in the right order. During a registrar move, your website, DNS records, and email can remain online if you keep the domain unlocked, use the correct authorisation code, and avoid changing nameservers too early. For managed hosting customers, this matters even more because DNS often controls services such as website hosting, mail routing, and verification records for SSL, Plesk, or third-party applications.
This guide explains how to move your domain to ITA Network Solutions, what to check before you start, how long the transfer can take, and how to prevent downtime for websites and email. It is written for domain owners who need clear, practical steps and for teams managing domains in a hosting platform or control panel environment.
Before you start the transfer
Before you begin, make sure the domain is eligible for transfer and that you have access to the current registrar account or the administrative contact email. Most domain transfers require a valid transfer authorisation code, also called an EPP code, Auth code, or transfer key.
Check transfer eligibility
- The domain must not be within the initial registration lock period for its TLD.
- The domain must be unlocked at the current registrar.
- You must be able to receive transfer confirmation emails.
- The domain should have a valid and up-to-date contact email address.
- If the domain is already in transfer, wait until that process is complete or cancelled.
Many gTLDs such as .com, .net, and .org are subject to a 60-day transfer restriction after registration or a recent registrar change. Some ccTLDs and EU-related extensions may have different rules, so always check the policy for the specific extension before proceeding.
Prepare website and email records
If your domain currently points to active hosting, review the DNS zone before making any change. This is especially important if your website uses:
- A records for the main site or subdomains
- CNAME records for web services or verification
- MX records for email delivery
- TXT records for SPF, DKIM, DMARC, or domain verification
- SRV records for Microsoft 365, VoIP, or other services
Record the current DNS settings before you transfer the domain. If the DNS is managed in Plesk or another control panel, export or copy the zone contents so you can restore them quickly if needed.
Step 1: Unlock the domain at the current registrar
The domain transfer can only start if the domain is unlocked. Log in to the account where the domain is currently registered and look for a setting such as Domain Lock, Registrar Lock, or Transfer Lock. Turn that option off.
Some registrars also show a clientTransferProhibited status in the WHOIS record. This should disappear after unlocking, although WHOIS updates can take some time to propagate.
If you do not see an unlock option, contact the current registrar’s support team and ask them to remove the transfer lock.
Step 2: Request the transfer authorisation code
Next, request the authorisation code from the current registrar. This code proves that you are authorised to move the domain. Depending on the registrar, it may be visible in the control panel or sent to the administrative contact email.
Keep the code ready before you begin the transfer to ITA Network Solutions. If the code is incorrect, expired, or incomplete, the transfer request may fail.
Useful checks for the auth code
- Confirm that the code was generated recently if the registrar issues time-limited codes.
- Copy it exactly as provided, including capital letters if shown.
- Do not add spaces before or after the code when entering it.
- Make sure you are using the code for the correct domain.
Step 3: Verify the registrant and admin contact details
Transfer approval messages are often sent to the registrant or admin contact email. If those details are outdated, the transfer can stall. Review the domain contact information at the current registrar and update it before starting the move if necessary.
For business domains, it is best to use a monitored mailbox such as a role account or an operational email address rather than a personal inbox that may be inaccessible during staff changes. If the transfer involves a compliance-sensitive domain, keep a record of the current registrant data in case verification is required.
Step 4: Start the transfer in ITA Network Solutions
Once the domain is unlocked and you have the auth code, initiate the transfer from your ITA Network Solutions account or the relevant order page. Enter the domain name exactly as it is registered, then provide the authorisation code when prompted.
If the platform asks whether to update nameservers during transfer, review that option carefully. In many cases, you should keep the current nameservers in place until the transfer is complete and DNS has been confirmed. This helps avoid interruption to the website, mail flow, and any connected services.
What usually happens after the request is submitted
- ITA Network Solutions submits the transfer request to the current registrar or registry process.
- The existing registrar may send a confirmation email or hold the request for approval.
- The domain owner or admin contact may need to approve the transfer manually.
- The transfer completes after the approval window expires or after immediate approval, depending on the TLD and registrar workflow.
Step 5: Approve the transfer if confirmation is required
Some transfers complete quickly once the request is made, while others require explicit approval from the current registrar or by email. Watch for messages in the domain contact mailbox and any registrar dashboard notifications.
If you receive a transfer approval email, verify the domain name and destination registrar before approving. Only approve the request if you initiated it and you trust the destination account details.
For domains that are tied to a hosting platform, it is a good practice to keep the website and email configuration unchanged until the registrar move is complete. Registrar transfer and DNS changes are separate actions, and mixing them can create unnecessary risk.
How long the transfer takes
Transfer timing depends on the TLD and the policies of both registrars. Many transfers finish within 5 to 7 days if no one manually rejects them. In some cases, the transfer may complete sooner if the losing registrar approves it immediately.
Delays are common when:
- The domain is still locked at the current registrar
- The auth code is invalid or missing
- The approval email cannot be delivered
- The transfer is subject to a registry hold or policy check
- The domain was recently registered or transferred
If you need to meet a project deadline, initiate the transfer early. That gives enough time to resolve any contact or policy issues before a launch, migration, or renewal date.
How to avoid website and email downtime
Domain transfer itself does not have to interrupt service. In most cases, the safest approach is to keep DNS exactly as it is until the transfer is fully complete. Your website and email usually continue working because the domain’s nameservers remain unchanged during the registrar move.
Recommended order of operations
- Check current DNS records and save a copy.
- Unlock the domain at the old registrar.
- Obtain the auth code.
- Start the transfer to ITA Network Solutions.
- Keep existing nameservers active until the transfer completes.
- Verify website, mail, and SSL-related records after completion.
- Only then make DNS changes if you need to move hosting or mail services.
If your website is hosted on a Plesk server or managed hosting platform, check whether the domain’s zone is managed in Plesk, in the registrar panel, or both. Make sure there is only one active source of truth for DNS, otherwise records can drift and email may stop delivering as expected.
DNS records to review after the move
- A and AAAA records for the website
- MX records for inbound email
- TXT records for SPF, DKIM, and DMARC
- CNAME records for www, autodiscover, or verification
- NS records if you intend to change nameservers
How to transfer the domain if DNS is managed in Plesk
If your domain is connected to Plesk, the transfer process at the registrar level is still the same, but you should be especially careful about DNS ownership. In many hosting setups, Plesk can manage the zone file while the registrar only points the domain to the correct nameservers.
Before transferring, confirm whether Plesk or the registrar currently controls DNS updates. If Plesk manages the zone, transferring the registrar account should not affect website content, mailboxes, or scheduled tasks. However, if the nameservers are also changing, plan the move carefully and test all records after the transfer.
Typical Plesk-related checks include:
- Confirm that the domain still resolves to the correct web root
- Check mail routing settings and mailbox aliases
- Verify DKIM and SPF records after any nameserver change
- Review SSL certificate bindings if the domain is used by multiple services
- Make sure Plesk DNS zone changes are published to the active nameservers
What to do after the transfer completes
After the transfer has finished and the domain appears in your ITA Network Solutions account, verify a few important items right away.
Post-transfer checklist
- Confirm the domain status in the control panel
- Check renewal date and auto-renew settings
- Review registrant contact information
- Verify nameservers and DNS records
- Test the website from a browser and a DNS lookup tool
- Send and receive a test email if the domain handles mail
- Review SSL and application settings if the domain is tied to hosting services
If the domain was transferred to consolidate services, also check whether billing, DNS management, and hosting are now aligned under the same account. That reduces administrative overhead and helps prevent accidental expiry.
Common problems and how to fix them
The transfer code is not accepted
Recheck the code for typos, extra spaces, or an expired token. If necessary, generate a new code from the current registrar and try again. Some registrars issue a new code each time you request one.
The domain is still locked
Return to the current registrar and confirm the unlock setting was applied. WHOIS changes may take time to update, so wait a little before retrying. If the control panel does not expose the setting, ask support to unlock the domain manually.
The approval email never arrives
Check spam folders, mail filters, forwarding rules, and whether the contact email address is correct. If the domain uses the same mail system that may be affected by DNS changes, avoid altering MX records until the transfer is complete.
The website or email stops working during the transfer
This is usually caused by a DNS change, not the transfer itself. Compare the current nameservers and zone records with your saved copy. Restore the original settings if required and wait for propagation.
The transfer is pending for longer than expected
Some registrars hold transfers for the full approval period. Check whether the losing registrar has a manual approval page or a release option. If not, the transfer should complete automatically once the waiting period ends.
Best practices for managing future domain transfers
If you manage multiple domains for clients or internal projects, establish a transfer checklist before any registrar move. This saves time and prevents service interruptions.
- Keep administrative contact emails updated
- Document current nameservers and DNS records
- Track expiry dates well in advance
- Use a control panel or password manager to store auth codes securely
- Avoid making DNS and registrar changes at the same time unless necessary
- For hosting migrations, separate the domain transfer from the website migration where possible
In managed hosting environments, it is often easier to complete the registrar transfer first, then plan any DNS cutover or platform migration during a maintenance window. This reduces risk and gives you a clear rollback path if needed.
FAQ
Will my website go offline when I transfer the domain?
Usually no. If you keep the existing nameservers and DNS records unchanged, the website should continue to resolve normally during the transfer.
Will email stop working during the transfer?
Not if MX and related DNS records stay the same. Email issues normally happen when DNS is changed at the same time as the transfer.
Do I need to change nameservers to transfer the domain to ITA Network Solutions?
No. The registrar transfer and nameserver change are separate actions. You can transfer the domain first and change DNS later if needed.
What is an auth code?
An auth code is a transfer authorisation code provided by the current registrar. It allows the new registrar to request the domain transfer.
Can I transfer a domain if it is expiring soon?
Yes, but start early. If the domain expires during transfer, the process may be delayed or fail depending on the extension and registrar rules.
What if my domain was recently registered?
Many domains cannot be transferred within the first 60 days after registration. Check the policy for your specific TLD before starting.
Should I update DNS records before or after the transfer?
Usually after the transfer, unless you need to prepare a migration. Keeping DNS stable during the registrar move is the safest approach.
Conclusion
Transferring a domain to ITA Network Solutions from another registrar is a manageable process when you follow the correct sequence: unlock the domain, request the auth code, verify contact details, submit the transfer, and keep DNS stable until completion. If your domain supports a website, email service, or Plesk-managed hosting, the most important rule is to separate the registrar change from any DNS or hosting changes. That keeps the site and mail online while the transfer finishes.
For the smoothest result, prepare your DNS records in advance, monitor approval emails closely, and verify the domain settings immediately after the transfer. This approach gives you a clean registrar move with minimal risk and no unnecessary downtime.