Zero Downtime, DNS Intact: Bulk Transferring .ie Domains to Another Host

Yes, you can arrange multiple .ie domain transfers as one coordinated project, but each domain needs its own valid Authcode and transfer request; the receiving registrar’s ordering system and support arrangements determine whether you submit the portfolio together or in smaller batches.

Bulk transfer describes how the work is organised. It does not mean one authorisation covers every domain. Each registration still needs to pass through the required transfer process. The .IE registry confirms that an individual domain’s Authcode authorises its move to another registrar.

Before proceeding, distinguish between four separate changes:

• Registrar transfer: changes the provider managing the domain registration.
• Registrant transfer: changes the registered domain holder.
• Hosting migration: moves website files, databases or mailboxes.
• DNS change: changes the records or nameservers directing traffic to services.

These changes can form part of a wider project, but one does not automatically complete the others.

For agencies, centralised management should preserve each client’s correct registration details and agreed authority. Bringing domains into one account does not require the agency to become their registered holder.

To transfer multiple .ie domains, build an accurate inventory, confirm authority for each registration, check service dependencies, obtain individual Authcodes, agree the receiving registrar’s submission process, pay the applicable fees and verify each completed transfer before changing or cancelling existing services.

1. Create an accurate domain inventory

Start with one record for every domain. Include its current registrar, registered holder, expiry date, contact email, nameservers, website host and email provider. Record who can approve the transfer and who will resolve any problems.

The .IE WHOIS service can help identify the registrar and renewal date. Compare its information with your provider accounts rather than relying solely on old invoices.

Flag domains approaching expiry. If there is insufficient time to resolve access or authorisation problems comfortably, agree whether renewal should happen before the transfer.

2. Confirm access and authority

Access to a billing account does not necessarily mean the registration’s contact details are current.

Check that the recorded contact email remains accessible and that the appropriate person has approved the move. For client domains, document that approval alongside the intended destination account.

If an address belongs to a former employee or an unused mailbox, ask the current registrar to correct the details before scheduling the transfer.

3. Check existing service dependencies

Find out whether the outgoing provider supplies DNS hosting, email forwarding or other services as part of the registration package.

Ask what happens to those services after transfer. Export the DNS zone where possible and record the existing nameservers. If DNS hosting must also move, prepare and test that change separately.

4. Request an Authcode for each domain

The .IE registry allows customers to request Authcodes from their current registrar or its Registration Services team. Codes are sent to the Registrant and Administrative Contact email addresses recorded against the domain.

Match each code carefully to its domain. Treat Authcodes as sensitive credentials and use the receiving provider’s agreed secure submission method.

5. Agree the submission process

Before authorising the portfolio, confirm:

• The accepted domain-list format and any batch limits.
• Transfer charges, renewal prices and VAT treatment.
• Whether existing nameservers will be preserved.
• Who will investigate unsuccessful requests.
• How completion will be confirmed for each domain.

A small initial batch can help validate your records and the agreed process before the remaining domains are submitted.

6. Track and verify every result

Use clear statuses such as awaiting authorisation, submitted, completed and needs attention.

After completion, check the registrar, expiry date, nameservers, renewal settings and account access. Keep exceptions open until they have an explained and verified outcome.

A registrar transfer should not interrupt your website or email when the existing nameservers, DNS records and underlying services remain active, but continuity depends on checking those dependencies beforehand, particularly where the outgoing provider bundles DNS hosting or forwarding with the domain registration.

The registrar manages the registration. Authoritative DNS tells other systems where to find your website and email. These functions can sit with different providers.

For a registration-only transfer, confirm that the receiving registrar will preserve the nameservers and that the existing DNS provider will continue serving the records. The .IE registry treats nameserver updates as a separately managed change.

If DNS is moving too, check website records, MX records for email routing, service-verification records and email authentication settings. SPF, DKIM and DMARC records help receiving systems assess legitimate messages. Missing records can affect delivery even when the mailboxes themselves remain available.

Do not cancel the old account immediately after the registration moves. First confirm which services remain there, test the website and check email in both directions.

The cost depends on the receiving registrar’s charges for each domain, any agreed portfolio pricing and separately scoped technical work; a .ie registrar transfer includes a one-year renewal, so assess the immediate payment alongside future renewal prices and the practical savings from simpler administration.

The registry states that a renewal payment is required when transferring. If renewal is not yet due, the payment renews the domain in advance.

Request a written comparison covering transfer payments, subsequent renewal prices, optional services and charges for any DNS or hosting work. Check whether all figures include or exclude VAT.

For illustration, a €6 annual difference across 40 domains represents €240 in annual registration savings. That is a calculation example, not a SmartHost quotation.

Administration matters too. Fewer accounts and clearer renewal responsibilities can reduce routine work, but transferring domains together does not necessarily align their expiry dates. Confirm those dates individually.

A bulk .ie transfer has no single completion time because preparation, contact corrections, authorisation, payment and registrar processing vary by domain; the registry automatically passes successfully submitted requests and publishes transfer details at its next zone update, which it says occurs every two hours.

That registry interval excludes the work needed to prepare and submit the portfolio. It is not a promise that every domain will transfer within two hours.

Separate straightforward registrations from domains with missing access, unclear authority or service dependencies. Ready domains can then progress while exceptions receive individual attention.

Agree a realistic timetable with the receiving provider and leave room for corrections before important renewal dates.

SmartHost provides a domain transfer service and support contacts; for a portfolio, share the domain list and required scope first so the team can confirm the submission method, pricing and assistance available before you authorise transfers or schedule related DNS, website or email changes.

For larger portfolios, establish whether the requirement is registration consolidation alone or a wider migration. Agree responsibilities, checks and costs before setting the timetable.

A registrar transfer alone does not change website speed, server location or application data residency. Those outcomes depend on the hosting services you separately choose.