Domain Transfer for Resellers and Hosting Providers: What to Check Before Moving Customer Domains

Moving customer domains between registrars is not just a matter of collecting EPP codes and submitting transfer requests.

For a hosting provider or domain reseller, every domain has a customer, a registration owner, an expiration date, a billing arrangement, and potentially a live website or email service behind it.

Before transferring customer domains, verify authorization, transfer eligibility, DNS continuity, renewal costs, billing records, and the workflow you will use to manage each transfer.

NiceNIC provides bulk transfer tools, Domain API v2, a WHMCS registrar module, and reseller account options. These can help you manage domain operations more efficiently, but they do not eliminate registry restrictions or the need to verify each customer’s domain individually.

This guide explains how to prepare a customer portfolio, choose the right NiceNIC transfer method, prevent service interruptions, and handle failed or pending transfers.

First, Decide Whether Each Customer Domain Actually Needs a Transfer

Consider a hosting company managing 80 customer websites.

Some domains may be registered through the hosting company’s reseller account. Others belong to customers who registered them independently. A few may use DNS hosting or email services bundled with their current registrar.

Transferring all 80 domains at once might simplify administration, but it could also introduce unnecessary work and risk.

Before recommending a transfer, determine what problem you are solving.

This distinction protects the customer’s interests and avoids unnecessary registration changes.

The goal is not to transfer as many domains as possible. It is to make the domains you manage easier to support, renew, and protect.

Keep Customer Ownership Separate From Registrar Management

One of the most important responsibilities of a hosting provider or reseller is maintaining a clear distinction between domain ownership and administrative access.

Managing a customer’s website does not automatically give you authority to transfer their domain.

Before initiating a transfer, establish who the registered name holder is and obtain the appropriate authorization.

Your internal customer record should answer these questions:

• Who is the legal registrant or registered name holder?
• Who is authorized to request a registrar transfer?
• Which account will manage the domain after transfer?
• Who receives domain verification and transfer notices?
• Who is responsible for renewal payments?
• Who may change nameservers, contacts, or security settings?
• How can the customer regain independent management if the business relationship ends?

For many agency and hosting relationships, keeping the customer as the registrant while the provider manages the domain under an agreed service arrangement can make future handovers easier.

If a different registrant arrangement is necessary, document it clearly and obtain the appropriate agreement.

Be Careful About Changing Registrant Information

Do not automatically change a customer’s registrant name, organization, or email address while preparing a transfer.

For gTLDs subject to ICANN’s Transfer Policy, a qualifying Change of Registrant can trigger a 60-day inter-registrar transfer lock unless an applicable opt-out was offered and exercised before the change.

If the customer’s ultimate goal is to change registrars, confirm the appropriate sequence before modifying registration ownership details.

Review the ICANN Transfer Policy for the applicable rules.

Build a Transfer Inventory Before Moving Any Customer Domains

For service providers, a structured transfer inventory is more useful than an informal list of domain names.

It allows your support, billing, and technical teams to work from the same information.

A practical inventory might contain the following fields:

Security note: Do not store raw EPP/Auth Codes in an unrestricted spreadsheet, support ticket, or customer-facing report. Use appropriately secured storage and limit access to authorized personnel.

The inventory should track whether a code is available without unnecessarily exposing the code itself.

For larger portfolios, add a field identifying the employee responsible for each transfer exception.

What Must Be Checked Before Submitting Customer Domains?

Not every domain is transferable at the same time, even when all domains belong to the same customer.

Transfer Eligibility and Registry Restrictions

For many gTLDs, check whether the domain is:

• Within 60 days of initial registration.
• Within an applicable 60-day period following an inter-registrar transfer.
• Subject to a Change of Registrant transfer lock.
• Protected by a registrar transfer lock such as clientTransferProhibited.
• Involved in a dispute or another condition that restricts transfer.
• Subject to expiration-related or registry-specific restrictions.

A domain that is expired is not automatically ineligible for transfer in every situation. Its actual status, registry rules, and available renewal or recovery options matter.

Country-code extensions may follow different procedures. Some require additional documentation, use different authorization methods, or have special transfer and renewal conditions.

Do not apply one generic gTLD procedure to every ccTLD in a customer portfolio.

Auth Codes and Approval Access

For standard gTLD transfers, the correct Auth Code is essential.

Each domain requires its applicable authorization credentials, and the domain holder or appropriately authorized representative must approve the transfer through the required process.

Verify that the registrant can receive and act on any relevant transfer communications.

Never assume that a successful request submission means all customer approvals have been completed.

Renewal and Expiration Timing

A reseller should review the expiration date of every domain before creating a batch.

Avoid starting nonurgent transfers immediately before expiration, especially where approval or registry processing could take several days.

However, renewing first is not always the best financial or operational choice. Registry rules, grace periods, and the effect of a recent renewal can influence the result.

Check the specific extension before deciding whether to renew first or transfer first.

Protect DNS, Email, and Website Services

A registrar transfer normally changes the company managing the domain registration. It does not automatically migrate website files, email accounts, or DNS records.

But service continuity depends on the existing infrastructure remaining operational.

The most important question is:

Will the current DNS provider continue serving the domain after the registrar transfer completes?

If the DNS provider is independent of the current registrar, and nameserver delegation remains unchanged, a registrar transfer should not normally interrupt DNS resolution.

If the old registrar also hosts the DNS zone, confirm that it will keep the service active after the domain leaves.

Before transferring a live customer domain, record its nameservers and back up all relevant DNS settings, including A, AAAA, CNAME, MX, SPF, DKIM, DMARC, CAA, and any other records the customer relies on.

Check DNSSEC as well. If a DNS migration is also planned, incorrect DS records or mismatched signing keys can cause DNS validation failures.

Avoid Combining Too Many Changes

Suppose a customer is changing hosting providers, switching email services, and transferring their domain to NiceNIC.

These are three separate operations.

A safer plan is to prepare and test the new services, complete any necessary DNS migration, verify website and email operation, and then perform the registrar transfer separately.

That approach makes it easier to identify the cause of a problem.

If website hosting, email, or SSL services are bundled with the old registrar, confirm that those subscriptions will remain active after the transfer.

For a detailed technical explanation, see Will Transferring a Domain Affect My Website, Email, DNS, or SEO?.

How to Transfer Customer Domains in Bulk at NiceNIC

NiceNIC's current Bulk Domain Transfer interface supports submitting up to 500 domains in one request.

This can reduce repetitive manual entry when a provider needs to move a customer portfolio.

However, the 500-domain limit describes the capacity of the submission form. It does not mean that every domain in a batch will be accepted or completed simultaneously.

Each domain remains subject to its own authorization, eligibility, and registry processing requirements.

Prepare the Transfer List

The current bulk transfer form uses one domain and its Auth/EPP Code per line, separated by a space.

For example:

These are illustrative values, not valid transfer credentials.

Use the current formatting instructions on the bulk transfer page rather than older screenshots or tutorials.

Before submitting, ensure that every code matches its domain and that the appropriate transfer permissions have been obtained.

Transfer in Controlled Batches

For a customer portfolio containing many domains, it is usually better to begin with a small, low-risk group than to submit everything immediately.

A practical approach is to divide domains according to operational risk.

A successful pilot should confirm more than order acceptance. Verify the domain’s final registrar status, DNS service, billing result, and customer-facing records.

After the pilot, expand the migration at a pace your support team can manage.

Start a batch: Bulk Transfer Domains to NiceNIC

Should You Use Bulk Transfer, API v2, or WHMCS?

These NiceNIC options serve different operational needs.

Domain API v2: Build Transfer Operations Into Your Platform

NiceNIC Domain API v2 supports domain transfer-in operations along with related domain management functions.

API access is available to both active Market Accounts and Reseller Accounts. Reseller pricing is a separate account-level benefit.

The published transfer endpoint operates on an individual domain. A custom system can coordinate multiple domain requests, but should not assume that there is a native, single-request bulk transfer API equivalent to the web form’s 500-domain submission feature.

Important: Verify Nameserver and Registrant Details in API Transfer Requests

NiceNIC’s documented API transfer-in request includes dns1 and dns2 parameters, along with registrant contact information.

When automating customer transfers, do not assume that these parameters will preserve the previous configuration automatically. Check the domain’s existing nameservers and registration details, use accurate values consistent with the customer’s authorization, and verify the final nameserver delegation after the transfer.

If you are unsure how the transfer parameters will be processed for a particular TLD, confirm the expected behavior with NiceNIC before submitting live requests.

A registrar transfer does not inherently require a DNS migration, but incorrectly configured transfer parameters could create an unintended service change.

A reliable integration should:

1. Authenticate using the approved API credentials and server settings.
2. Check current TLD pricing and the available account balance.
3. Confirm customer authorization and domain transfer eligibility.
4. Verify nameserver and registrant information before submitting the transfer.
5. Submit the transfer request with the correct parameters.
6. Record the response and track the domain's actual transfer status.
7. Reconcile the final result before updating customer billing or reporting completion.

NiceNIC’s API documentation distinguishes successful completed operations from pending orders.

For example, a transfer response with code: 201 means the transfer order is pending processing. It does not establish that the registry has completed the transfer.

Your software should avoid automatically repeating a paid transfer request simply because it receives a timeout or a pending response. Check the existing order and transaction state first to avoid duplicate actions.

If you are developing an integration, begin with safe read-only requests and use the documented testing environment before placing live paid orders.

Technical reference: NiceNIC Domain API v2 Documentation

WHMCS: Connect Domain Transfers to Customer Billing

For hosting providers already using WHMCS, NiceNIC provides a registrar module that supports eligible domain registration, transfer, renewal, and management operations.

NiceNIC’s published integration information confirms support for the WHMCS 9.0 release line as of September 2026.

Before enabling live customer orders:

• Select the module package appropriate for your WHMCS environment.
• Configure your NiceNIC API credentials and authorize the correct server outbound IP address.
• Assign NiceNIC as the registrar for the relevant supported TLDs.
• Set registration, renewal, and transfer selling prices in WHMCS.
• Review currency conversion, scheduled tasks, and automation settings.
• Test a controlled order before expanding to customer volume.

Installing the module does not automatically configure your customer selling prices or reconcile existing client invoices.

This matters especially when migrating existing customer domains.

For example, a customer may have already paid your hosting company for an upcoming domain renewal. Transferring the domain to NiceNIC does not automatically reconcile that payment with the registration term or the existing WHMCS billing schedule.

After a successful transfer, review the actual registration expiration date, customer renewal date, registrar assignment, and invoice history.

A WHMCS invoice marked paid does not by itself prove that the corresponding registry operation has completed.

Integration guide: NiceNIC WHMCS Registrar Module

Calculate the Real Cost of Moving a Customer Portfolio

Transfer pricing is important, but it is only one part of the business decision.

For each extension, compare the applicable transfer cost, future renewal rate, any registry-specific requirements, and the ongoing support work involved.

NiceNIC publishes different pricing levels for Market, Basic Reseller, Super Reseller, and VIP Reseller accounts.

The current reseller program starts with $200 in usable account credit at the Basic level. The qualifying deposit becomes account balance for eligible purchases rather than a separate setup or annual membership fee.

API access itself is separate from reseller pricing. A Market Account can access supported API capabilities without automatically receiving Basic or VIP reseller rates.

You should not assume that the same transfer price applies to every account or every TLD.

What Should a Reseller Include in the Cost Calculation?

The extension added by a successful transfer is not identical across all TLDs, and exceptions can apply.

Reconcile the actual post-transfer expiration date instead of assuming that every transfer adds exactly one year.

For a hosting company, sustainable margins come from the entire customer lifecycle, not just the first transfer transaction.

Compare costs through the NiceNIC Domain Price List and Domain Reseller Program.

Keep Clients Informed Without Creating Unnecessary Alarm

A well-managed customer transfer should have a clear communication owner.

Clients need to understand why the transfer is being performed, what approval may be required, and what will remain unchanged.

For a planned transfer, send a short notice before submission.

Example customer notice:

Subject: Upcoming Domain Registrar Transfer

We are preparing to move the registration management of your domain to our domain service platform. Your website hosting and email services are not being moved as part of this registrar transfer.

We have reviewed the current DNS setup and will monitor the transfer. You may receive a transfer authorization message requiring your approval. Please follow only the verified instructions from the relevant registrar and contact our support team if anything looks unexpected.

We will confirm once the transfer has completed and our post-transfer checks are finished.

Avoid promising a specific completion date unless it is supported by the actual registry process.

Also avoid guaranteeing zero downtime. A registrar-only transfer normally does not interrupt the website or email, but service continuity depends on existing DNS and hosting remaining operational.

Communicate at Meaningful Milestones

A simple customer communication process has four stages:

For a larger portfolio, automate internal status updates while keeping customer messages concise.

An internal “pending” status should never generate a “transfer completed” email.

What to Do When Customer Transfers Fail or Stay Pending

Failed transfers should be handled individually, even when they were submitted as part of a larger batch.

A reseller needs to distinguish transfer rejection from normal pending processing, DNS problems, and billing inconsistencies.

For rejected gTLD transfers, ICANN policy establishes requirements around permissible grounds for denial.

Check the stated reason rather than assuming that every unsuccessful transfer is caused by an incorrect EPP code.

When a transfer request remains pending, avoid unnecessary nameserver or ownership changes unless there is a separately verified operational reason.

Escalate account-specific or registry-specific problems to NiceNIC Support with the domain, current status, relevant time, and error details.

Never include passwords or API secrets in an unsecured message.

What Should Happen After a Successful Transfer?

A completed registry transfer is only one milestone in the customer’s service lifecycle.

Before closing the migration ticket, verify that the domain is associated with the intended NiceNIC account and that the recorded nameservers match the expected configuration.

Check that the website resolves, business email can send and receive messages, and DNSSEC validation works if enabled.

Then reconcile the domain’s actual expiry date, renewal configuration, customer billing record, and account ownership information.

Update your internal inventory to reflect the final registrar, completion date, operational status, and support contact.

For providers using WHMCS or custom software, confirm that the customer-facing system reflects the same final state as the registrar account.

If the customer eventually leaves your hosting service, you should have a documented, authorized process for handing back control of the domain.

Transparent ownership and handover procedures are part of a reliable managed domain service.

Can Domain Transfers Become a Profitable Hosting Service?

For a small hosting company, domain management can complement existing website hosting, SSL, DNS, and technical support services.

The potential commercial benefits include recurring domain renewal revenue, fewer disconnected control panels, and closer integration between the services the customer already purchases.

However, profitability should not be measured by transfer fees alone.

A transfer service adds responsibilities: monitoring expirations, protecting registration access, resolving failed orders, communicating with customers, and maintaining accurate billing records.

A provider that charges a small domain-management fee but spends excessive time on preventable support requests may find the service less profitable than expected.

The stronger opportunity is to build an efficient and transparent managed-domain offering.

That means pricing the service realistically, maintaining customer ownership rights, automating repetitive work, and giving customers a clear point of contact when something goes wrong.

NiceNIC’s reseller pricing, bulk transfer tools, Domain API, and WHMCS module provide different ways to support that model.

The right choice depends on the provider’s current systems, domain volume, and TLD mix.

Frequently Asked Questions

Can hosting providers transfer client domains without the customer doing it themselves?

A hosting provider can coordinate a transfer when properly authorized, but it must respect the registered name holder’s rights and any applicable registrar or registry approval procedures.

Managing a customer’s hosting account alone does not authorize transferring the domain.

How many domains can I transfer at once with NiceNIC?

NiceNIC’s current bulk transfer web form supports up to 500 domains per submission.

Each domain still needs its own applicable authorization information and eligibility checks. Not all submitted domains are guaranteed to complete.

Does NiceNIC API v2 support domain transfers?

Yes. NiceNIC documents a domain transfer-in API operation.

The published endpoint accepts an individual domain transfer request.

If you need to coordinate many transfers through your own platform, your application must manage individual requests, nameserver parameters, pending statuses, errors, and billing reconciliation.

Can I automate customer domain transfers through WHMCS?

NiceNIC provides a WHMCS registrar module with supported transfer functions.

You must configure the connection, assign the correct registrar, set the relevant TLD prices, and confirm how pending orders and customer billing are handled.

Will transferring customer domains affect websites or email?

A registrar-only transfer should not normally interrupt the website or email when the existing DNS, hosting, and email services remain operational.

Problems can occur if old registrar-provided DNS or bundled services are discontinued, or if additional DNS changes are made incorrectly.

Do customers have to change their nameservers?

Usually not for a standard registrar transfer.

Nameserver requirements can vary by extension or transfer scenario.

When transferring through an API, check how the provided nameserver parameters will be processed.

Verify that the DNS provider will continue serving the domain after the transfer.

Does every transferred domain receive one additional registration year?

No universal guarantee applies to every TLD and transfer scenario.

Review the applicable registry rules, transfer charge, and final expiration date before adjusting customer renewal billing.

Move Customer Domains With a Workflow Built for Your Business

The safest domain migration is not necessarily the fastest one.

It is the one where every customer has authorized the transfer, every domain has been checked for eligibility, critical services remain available, and billing records accurately reflect the final result.

NiceNIC gives hosting companies, domain resellers, agencies, and software platforms several ways to handle these operations.

Ready to transfer several customer domains?

Start a Bulk Domain Transfer

Want to offer recurring domain services under your own customer-facing business?

Explore the NiceNIC Domain Reseller Program

Already running WHMCS or building your own domain management platform?

View WHMCS Integration or Explore Domain API v2.

For a general walkthrough of moving a domain registration to NiceNIC, see Transfer Your Domain to NiceNIC: A Practical Guide for Better Domain Control.

NiceNIC — ICANN-Accredited Registrar Since 2006.

Transfer eligibility, available operations, pricing, and registration terms depend on the TLD, account level, and applicable registry rules. Confirm current conditions before submitting customer orders.