A domain managed in CURIAWEB can, in certain cases, be transferred from one CURIAWEB customer account to another. This is useful, for example, if a domain is to be managed in the future via a different company, a different customer, or a newly created customer area.
This is a internal transfer within CURIAWEB. The domain is not being transferred to another registrar.
Briefly explained: During an internal transfer, the domain is moved from one CURIAWEB customer account to another CURIAWEB customer account. This is different from a domain transfer to another domain registrar.
What does „pushing a domain“ mean? #
The term Domain Push is used differently by various domain providers. It often refers to the transfer of a domain between two customer accounts at the same provider.
At CURIAWEB, such a transfer is carried out administratively by CURIAWEB. In the underlying customer system, the assignment of the domain to the previous customer account is changed and the domain is assigned to the new customer account.
The domain itself does not need to be transferred to another registrar for this.
What is the difference to a domain transfer? #
During a classic domain transfer, the management of a domain moves from one registrar or domain provider to another. Depending on the domain extension, an auth code or transfer code, for example, is required for this.
With an internal transfer between two CURIAWEB customer accounts, however, the domain remains within the existing CURIAWEB domain management.
We explain how an actual registrar transfer works at Domain transfer to CURIAWEB: How the transfer works.
Can I transfer a domain myself to another CURIAWEB customer area? #
No. An internal transfer of the domain between two CURIAWEB customer accounts is carried out by CURIAWEB.
Among other things, this is intended to prevent a domain from being accidentally or without sufficient authorization assigned to another customer account.
If you want to move a domain to another CURIAWEB customer area, please contact CURIAWEB support.
Important: A domain should only be assigned to a different customer account if it is clearly established that the transfer is authorized. CURIAWEB may therefore request additional information or confirmation before carrying out the transfer.
What is required for the postponement? #
For processing, it must be clearly identifiable which domain is to be transferred and to which CURIAWEB customer account it is to be assigned in the future.
The target account must already exist. If a corresponding CURIAWEB customer account does not yet exist for the future domain holder or contractual partner, it must be set up first.
Which additional information or confirmations are required depends on the specific case. This applies in particular if the previous and future contracting parties are not identical.
Does an internal transfer change the name servers? #
A purely internal assignment of the domain to a different customer account is not the same as a nameserver change.
The DNS configuration should nevertheless be checked after an administrative change, especially if hosting, email, or other services are reorganized at the same time.
The CURIAWEB nameservers are:
ns1.curiaweb.ch
ns2.curiaweb.chYou can find more information at Finding and correctly using CURIAWEB nameservers.
Does the website change due to the shift? #
Not automatically.
The domain and web hosting are separate services in the customer system. If only the domain is assigned to a different customer account, this does not automatically mean that an associated hosting account is also moved.
If domain and hosting are to be transferred together to another customer account, this should be explicitly stated in the request.
Practical Tip: Let us know in your request whether only the domain or also associated hosting or other services should be reassigned. This allows the desired account structure to be checked prior to the change.
What happens to the email accounts? #
An internal transfer of the domain record does not automatically transfer a hosting account or email mailboxes stored within it.
If the email accounts are part of an existing web hosting package and this hosting remains unchanged, the administrative domain assignment does not automatically affect the stored messages.
If, on the other hand, hosting or email services are also to be moved to a different customer account or a different hosting environment, this must be taken into account separately.
Does the domain owner change automatically? #
No.
The assignment of a domain to a different customer account and the contact data stored with the registry or registrar are not the same thing.
Therefore, an internal transfer within the CURIAWEB customer system does not automatically change the stored domain holder or contact data.
Important: If both the customer account and the legal or registered domain owner are to be changed, this must be explicitly stated. Depending on the domain extension and registry, additional requirements may apply.
What happens to existing invoices? #
Invoices that have already been issued belong to the previous customer account and are not automatically transferred to the new customer account as a result of the internal transfer of a domain.
This is particularly important if an invoice has already been issued for the domain or if there are still outstanding amounts.
Therefore, in the event of a transfer, CURIAWEB checks how the domain is to be billed in the future.
What will happen to future domain renewals? #
After a correctly executed internal transfer, the domain is assigned to the new CURIAWEB customer account.
Future management and billing can then take place via this customer account.
However, existing invoices from the previous account will not be retroactively transferred as a result.
Do I need an auth code for the internal transfer? #
Usually not.
An auth code serves primarily to authorize a domain transfer between registrars or domain providers. During an internal transfer within the existing CURIAWEB management, such a registrar change does not take place.
Therefore, an internal account transfer should not be confused with a classic domain transfer.
Can a domain be transferred to a customer account of another person or company? #
In principle, an internal reassignment may also be necessary if the future contractual partner is different.
In such a case, however, this is no longer merely an organizational transfer between internal customer accounts. CURIAWEB must be able to verify whether the change is authorized and which contract or domain holder data need to be updated.
Depending on the domain extension, additional requirements from the responsible registry or registrar may apply.
What should I check before a move? #
First, check whether actually only the domain is to be assigned to another customer account or whether other services are affected at the same time.
Particularly relevant are web hosting, e-mail, DNS, additional domains, or other services associated with the previous customer account.
If the DNS configuration is also to be changed, you can check the currently publicly visible entries beforehand with the CURIAWEB DNS-Check document.
You can find further information at Check DNS records: View current DNS configuration of a domain.
Internal transfer or domain transfer – what do I need? #
If your domain is already managed via CURIAWEB and only needs to be assigned to another CURIAWEB customer account, this is an internal transfer.
If a domain is to be transferred from another provider to CURIAWEB, you need a domain transfer instead.
If the domain is to remain registered with another provider and only CURIAWEB hosting is to be used, neither of the two options is necessary at all. In this case, the domain can be connected to CURIAWEB via nameservers or DNS entries.
We explain how this works at Keep domain with another registrar and connect to CURIAWEB Hosting.
Summary #
A domain managed in CURIAWEB can be reassigned to another CURIAWEB customer account if necessary.
This internal transfer is not a classic domain transfer. The domain does not change to another registrar, and normally no auth code is required for this.
The migration will be carried out by CURIAWEB. The target account must be clearly determined, and CURIAWEB may request confirmation or additional information prior to the change.
It is also important to distinguish between domain, hosting, email, and domain owner data. Transferring the domain does not automatically transfer these components with it.
If you want to reassign other services in addition to the domain, or if the domain owner is also to change, please explicitly state this in your request.
