Transfer a domain to Saplo. Transfer.pl domains for free.

1. A domain transfer does not have to interrupt your website.

Transferring a domain to a new registrar can raise concerns: will the website stop working, will business email stop receiving messages, will you need to manually re-enter DNS records during the transfer? None of these concerns become an issue when the transfer is carried out correctly, because only the registrar changes, not the servers the domain points to.

In Saplo, the transfer starts by entering the domain name and the AuthInfo code (the transfer code issued by your current registrar). The system then checks whether the domain is eligible for transfer (status OK, no transfer lock, and at least 60 days remaining before registration expires, in line with NASK's rules for.pl domains).

The.pl domain transfer process also requires the registrant's details (the domain owner's details) to match the information provided for the transfer. NASK sends a confirmation email to the old registrar. This is a standard security step against unauthorized domain takeover.

2. How much does a domain transfer cost on Saplo?

Transferring a.pl domain or a Polish second-level domain (.com.pl,.net.pl,.org.pl,.info.pl,.biz.pl) is free ($0). NASK does not charge a wholesale transfer fee for these domains, so Saplo does not add a margin on top of the zero cost.

Transferring a global domain (.com,.eu, and others) costs the amount set by Saplo's pricing formula for this operation: the wholesale cost plus VAT and a fixed $2 surcharge, with no percentage margin that would significantly inflate the price for more expensive TLDs. For example, under this formula, transferring a.com domain costs around $17 and a.eu domain around $11 (including any price overrides, as of 2026-10-10).

After the transfer, the domain renews at the renewal rate applicable to its TLD (e.g. $20/year for.pl, based on the current wholesale cost), with no first-year promotional price, because a transfer moves an existing registration rather than creating a new domain registration.

3. How does it compare with the competition?

Competitor A offers.pl domain transfers for $0 net for the first year (public price lists and.pl transfer guide, as of 2026-10-10), showing that free.pl transfers are a market standard resulting from NASK's policy, not a one-off promotion by a single registrar.

Competitor B's domain price list states that.com registration costs $12 net per year and renewal costs $31 net per year (public price lists, as of 2026-10-10). This is a higher renewal price than Saplo's formula (about $20 gross for.com), although providers' net/gross calculation methods can vary.

The difference between registrars often isn't in the transfer price itself, because many domains (especially.pl) can be transferred for free regardless of the provider. The renewal price in subsequent years has a greater impact on a domain's total cost over several years than the one-time transfer fee.

4. Four steps to transfer your domain

Step one: Unlock your domain with your current registrar by disabling the transfer lock if it is active, then get the AuthInfo code. The code is usually available in your domain management panel with your current provider, or it can be sent by email on request.

Step two: Enter the domain name and AuthInfo code in the Saplo panel. The system checks the domain status and tells you whether the transfer can start immediately or whether you first need to remove the lock or wait for the minimum period since registration to pass.

Step three: for.pl domains, confirm that the registrant's details match those held by your current registrar. NASK will send a confirmation email about the transfer to the old registrar. This is a standard security step required by the registry.

Step four: wait for the transfer to complete (usually a few days for global domains and less for.pl). The domain will automatically start pointing to Saplo's servers without website downtime, provided the DNS records were copied correctly beforehand.

5. Before you begin: what to keep in mind

Check that your domain has at least 60 days remaining before it expires. If the remaining term is too short, there may not be enough time to complete the transfer before the registration expires at your previous registrar.

Make sure the registrant's details (the domain owner's details) are up to date at your current registrar. A mismatch is the most common reason NASK rejects a.pl domain transfer.

If your domain has active business email, copy the MX records to the new DNS zone before the transfer completes. This prevents email from stopping for even a few hours during the switchover.

6. Transfer a domain with active business email

If your domain has active business email with another provider, first copy the MX records to the Saplo panel and wait for them to propagate before the transfer completes. This prevents email from stopping for even a few hours.

Mailcow on Saplo can take over business email after the domain transfer, with a storage limit that depends on your selected Box plan, so plan the mailbox migration alongside the domain transfer.

Best practice is to test the new MX records before the final switchover, for example by adding a temporary test subdomain, before your production domain starts using the new email configuration.

If the transfer and email migration happen at the same time, schedule them outside peak business communication hours to minimize the impact of any brief interruption on real email traffic to clients.

7. What happens to your existing website during a domain transfer?

A domain transfer changes only the registrar, meaning the company that manages the domain registration. It does not automatically change the server your domain points to, so your website may remain on its current hosting until you manually switch the DNS records.

For a full migration of the domain and website, first move the website to Saplo and test it on a temporary subdomain, then switch the domain and transfer the registration at an agreed time.

DNS propagation after changing the records usually takes anywhere from a few minutes to a few hours, depending on the TTL settings in the previous configuration. A brief delay in seeing the changes for some visitors is therefore normal and unavoidable.

Transferring the domain registration itself, meaning changing registrars, and migrating the website content are independent processes. You can complete them at different speeds and do not have to do both on the same day.

8. What can go wrong during a domain transfer, and how to avoid it

The most common reason a.pl domain transfer is rejected is a mismatch between the registrant's details (the domain owner's details) provided during the transfer and the details registered with the current registrar. NASK verifies this automatically before approving the transfer to the new registrar.

The second most common reason is an active transfer lock at the current registrar. It is often enabled by default to protect against unauthorized domain takeover and must be manually disabled in the old provider's panel before the transfer can begin.

A third reason is that the domain registration is too close to expiry. The transfer process needs a time buffer, with at least 60 days recommended, so it can finish before you lose the registration at your current registrar. A delayed transfer could otherwise result in the loss of the domain.

The fourth reason, which is less common but still occurs, is a failure to respond to a confirmation email from the old registrar or NASK. This holds up the transfer until the domain owner or contact person responds to the required transfer confirmation.

For global domains (.com,.eu, and others), the process is similar, but it is governed by the registry for the relevant TLD rather than NASK. This means that timelines and requirements vary slightly depending on the specific top-level domain you want to transfer.

The Saplo panel keeps you informed of the transfer status and any blocks that require action from you. If there is a problem, you do not need to guess what went wrong. Simply check the specific message in the panel and take the indicated action.

9. Documents and details needed to transfer a company domain

For a domain registered to a company rather than an individual, the transfer requires the registrant details to match those in the registry. This can be more demanding for company domains than for personal domains, especially if the company name, address, or legal form has changed since the domain was first registered.

If the domain was registered many years ago and the company's details have since changed, such as its registered address, update the registrant details with the current registrar before starting the transfer process. This helps avoid rejection due to a data mismatch.

For.pl domains, the technical and administrative contact specified at registration should be reachable at the email address provided throughout the transfer, because this is where NASK may send the confirmations required during transfer verification.

For global domains (.com,.eu, and others), verification requirements vary by TLD registry, but the principle is the same: current and accurate domain owner details make the entire transfer process easier and faster.

The Saplo team assists with unusual transfer situations, such as a domain registered to a company's former owner. However, final authorization must come from the person or entity formally listed as the domain owner in the registry.

10. Transferring multiple domains for a larger portfolio

You can transfer domains to Saplo one by one if you run a company or agency with many domains (your own brands and clients' domains). This lets you spread the process over time and test each transfer thoroughly instead of moving everything at once and risking that a problem with one domain complicates the entire process.

For a portfolio of domains, keep a simple list of expiry dates and transfer statuses. This makes it easier to plan which domains to transfer first. Domains close to expiry need faster action than those with a longer buffer.

Agencies that manage domains for multiple clients should pay particular attention to registrant details for each domain. Client details may differ between domains, even when the same agency manages them on behalf of different owners.

A domain tracker maintained by an agency, including each domain name, owner, expiry date, and transfer status, is a practical tool when managing a large number of client domains. It works whether all domains have already been transferred to Saplo or some transfers are still in progress. Even a simple spreadsheet makes it easier to discuss renewal dates with clients before an approaching expiry becomes a last-minute problem.

11. Summary: a simple, predictable domain transfer process

Despite sounding like an operation with a high risk of downtime, a domain transfer is in practice a simple, well-defined process, provided the registrant's details are up to date, the domain has no transfer lock, and there is enough time left before the registration expires. For.pl domains, the transfer fee is $0, and your website and email continue without interruption because only the registrar changes, not the infrastructure to which the domain points. This makes the whole process much less stressful than it may seem before you carry out your first transfer yourself.