# Transfers / Portfolio Consolidation # Bulk transfer of domains in a TransIP account This article presents a ready-to-use script (written in PHP) that can be used to easily transfer domains from your TransIP account to your Openprovider account. As you are a TransIP customer and we are Openprovider and not TransIP, you will be much more experienced with TransIP than we are. From your experience, feel free to add a comment to this article with your feedback, tips or tricks! Of course, you can send an e-mail as well. **Important disclaimer: this script is created as a courtesy to our customers. Running it is completely on your own responsibility. We strongly advise to run the script in test mode first, before actually ordering the domain transfers. Openprovider is not responsible for any unforeseen situation that is the result of running this script.** ## Download and install the TransIP API If you already use the TransIP API, you can probably skip most instructions in this section. If you do not already use the TransIP API, please follow the next steps: - **Enable API access** - Log in to your TransIP control panel - Navigate to Config > My account > [API](https://www.transip.nl/cp/account/api/) - Enable API access with the slider under "API settings" - Optionally (recommended from security perspective), add your IP address to the IP whitelist - Under "Key pairs", create a new key pair by typing a label and clicking the "Add key pair" button; optionally tick the "Whitelisted IP" checkbox - The private key will be shown on your screen; copy this private key as you cannot retrieve it again at a later moment - **Download API** - Clone the API source repository [https://github.com/transip/transip-api-php](https://github.com/transip/transip-api-php) After having finished those steps, you're ready to use the TransIP API and prepare and run the transfer script. ## Download and install the Openprovider API If you already use the Openprovider API, you can probably skip most instructions in this section. If you do not already use the Openprovider API, please follow the next steps: - **Enable API access** - Log in to your Openprovider control panel - Navigate to the menu [Account](https://cp.openprovider.eu/account/dashboard.php) - Click the "Add contact person" button - Define the new user, ensure that you set the type to "technical" and enable API access - Add your IP address to the IP whitelist by clicking the "Edit" button under the "API access restrictions" section. - Click the link in the e-mail that you received and set your password - After setting the password, a hash value will be shown; copy this value as you cannot retrieve it again at a later moment - **Download API** - Download the API.php file from the [Openprovider API documentation](https://doc.openprovider.eu/API_General_Howto) - In this article, I assume that the API.php file is stored in the same directory as the transfer-from-transip.php script ## Prepare and run the transfer script **Download and customise** - Download the script that is [attached to this article](https://support.openprovider.eu/hc/en-us/article_attachments/360018066620). *The script is prepared to be run in the root directory of the TransIP API source code that you just downloaded (e.g. ~/Downloads/transapi\_transip.nl\_v5\_9/), but you can place it at any other location - just be sure to update the paths to the includes in the script.* - Open the script and populate the $auth variable with the Openprovider API credentials and populate the $login and $privateKey variebles with the TransIp credentilas. **Define domain list** Create a file in which you put each domain to transfer on a separate line. IDNs must be written in punycode, so *domain.онлайн* must be written as *domain.xn--80asehdb*. **Run the script** The script accepts the following parameters: - **-f** (required): this is the file name that contains the domain list - **-t**: "test mode", can be "0" or "1". If test mode is enabled (default value), the script will behave as "read only" and output data, but it will not create DNS zones, unlock domains or transfer domains - **-d**: whether or not to copy the DNS zones. Allowed values: - 0: do not import DNS zones (default value) - **1**: import DNS zones if no zone already exists - **overwrite**: import DNS zones; if a zone already exists, delete it first - **-h**: can be "0" or "1", and defines whether or not to force creation of new handles for every contact. If set to "0" (default value), the script will check the data of a handle; if an Openprovider handle already exists with the same data, this existing handle is used instead of creating a new one. - **-v**: "verbose mode", can be "0" (default value) or "1", and defines whether or not to output debug and other information. - **--help**: send "transfer-from-transip.php --help" for command line information about the usage of the script. By running the script, the following steps will be performed for each domain in the domain list: - Retrieve the domain details from TransIP - If required, import the DNS zone - Create the contacts in Openprovider - If required, retrieve the authorisation code - If required, unlock the domain - Order the transfer in Openprovider From here on, the normal transfer process commences. Some extensions will be transferred instantly (e.g. .nl), some extensions will send an e-mail to the domain holder (e.g. .fr), some extensions will start a transfer period (e.g. .com). ## (Un)supported domains The script is pretty simple: it just reads contact and nameserver information and the authorisation code, unlocks the domain and initiates the transfer. This should be fine for most extensions, but some cases are not supported because of this simplicity: - **Additional data**: as soon as additional information or actions are required, the transfer is not supported and should be initiated manually. - **Authcode not retrievable**: if a domain requires an authorisation code that is sent to the registrant only (for example .be, .pt or .ro), the domain cannot be transferred with this script. Notes on a couple of specific TLDs: - **.eu**: before running the script, request the authcode through the TransIP web panel (feel free to place a comment with a TransIP API example how to retrieve .eu authcodes) - **.de**: if the trustee service is turned on, TransIP will not provide the authcode. Deactivate TransIP's trustee service before running the script. - **.fr**: if the trustee service is turned on, TransIP will not provide the authcode. Deactivate TransIP's trustee service before running the script. - **.uk**: the script will request the transfer, but the IPS tag for the domain must be changed to REGISTRAR-EU by TransIP. Contact TransIP support to do this. # Bulk transfer of domains in a Versio account This article presents a ready-to-use script (written in PHP) that can be used to easily transfer domains from your Versio account to your Openprovider account. As you are a Versio customer and we are Openprovider and not Versio, you will be much more experienced with Versio than we are. From your experience, feel free to add a comment to this article with your feedback, tips or tricks! Of course, you can send an e-mail as well. **Important disclaimer: this script is created as a courtesy to our customers. Running it is completely on your own responsibility. We strongly advise to run the script in test mode first, before actually ordering the domain transfers. Openprovider is not responsible for any unforeseen situation that is the result of running this script.** ## Configure the Versio API If you already use the Versio API, you can probably skip this section. If you do not already use the Versio API, please follow the next steps: - **Enable API access** - Log in to your Versio control panel - Navigate to Account > [Versio API](https://www.versio.nl/customer/account/api) - Enter your control panel password and the IP address from where you run the script under the "IP addresses with access to API" After having finished those steps, you're ready to use the Versio API and prepare and run the transfer script. ## Download and install the Openprovider API If you already use the Openprovider API, you can probably skip most instructions in this section. If you do not already use the Openprovider API, please follow the next steps: - **Enable API access** - Log in to your Openprovider control panel - Navigate to the menu [Account](https://cp.openprovider.eu/account/dashboard.php) - Click the "Add contact person" button - Define the new user, ensure that you set the type to "technical" and enable API access - Add your IP address to the IP whitelist by clicking the "Edit" button under the "API access restrictions" section. - Click the link in the e-mail that you received and set your password - After setting the password, a hash value will be shown; copy this value as you cannot retrieve it again at a later moment - **Download API** - Download the API.php file from the [Openprovider API documentation](https://doc.openprovider.eu/API_General_Howto) - In this article, I assume that the API.php file is stored in the same directory as the transfer-from-versio.php script ## Prepare and run the transfer script **Download and customise** - Download the script that is [attached to this article](https://support.openprovider.eu/hc/article_attachments/360009473659/transfer-from-versio.php). - Open the script and populate the $authVersio and $authOP variables with the Versio and Openprovider API credentials. **Define domain list** Create a file in which you put each domain to transfer on a separate line. IDNs must be written in punycode, so *domain.онлайн* must be written as *domain.xn--80asehdb*. **Run the script** The script accepts the following parameters: - **-f** (required): this is the file name that contains the domain list - **-t**: "test mode", can be "0" or "1". If test mode is enabled (default value), the script will behave as "read only" and output data, but it will not create DNS zones, unlock domains or transfer domains - **-d**: whether or not to copy the DNS zones. Allowed values: - 0: do not import DNS zones (default value) - **1**: import DNS zones if no zone already exists - **overwrite**: import DNS zones; if a zone already exists, delete it first - **-v**: "verbose mode", can be "0" (default value) or "1", and defines whether or not to output debug and other information. - **--help**: send "transfer-from-versio.php --help" for command line information about the usage of the script. By running the script, the following steps will be performed for each domain in the domain list: - Retrieve the domain details from Versio - If required, import the DNS zone - Create the contacts in Openprovider - If required, retrieve the authorisation code - If required, unlock the domain - Order the transfer in Openprovider From here on, the normal transfer process commences. Some extensions will be transferred instantly (e.g. .nl), some extensions will send an e-mail to the domain holder (e.g. .fr), some extensions will start a transfer period (e.g. .com). ## (Un)supported domains The script is pretty simple: it just reads contact and nameserver information and the authorisation code, unlocks the domain and initiates the transfer. This should be fine for most extensions, but some cases are not supported because of this simplicity: - **Additional data**: as soon as additional information or actions are required, the transfer is not supported and should be initiated manually. - **Authcode not retrievable**: if a domain requires an authorisation code that is sent to the registrant only (for example .be, .pt or .ro), the domain cannot be transferred with this script. Notes on a couple of specific TLDs: - *(no info yet)* Known issues with the script: - Versio runs into API rate limits very soon; if you have information about the Versio API rate limits, please let us know in a comment. - DNS zone creation is not yet tested; if you have a domain that should migrate its zone from the Versio to the Openprovider nameservers, let us know in the comments your experience. # DNS Belgium: Taking over complete or partial account ## How to initiate a bulk transfer of .be domain names Advantages of using the registry bulk transfer option: - all domains are moved at once - all handles are created automatically - nameserver settings are copied - expiration date stays unchanged - transfer codes are not required - can be used when you have an own registrar account or via a third party (partial transfer) ### Requirements - A completed and signed **bulk transfer form** ([full](https://support.openprovider.eu/hc/en-us/article_attachments/22768836202770) or [partial](https://support.openprovider.eu/hc/en-us/article_attachments/22768836202770)). Please fill in your registrar ID and registrar name and sign the form. - A **copy of the note** that you sent or will send to your customers about this change, if this is different from the example text that is included on the second page of the bulk transfer form. See further down in this article for the requirements to such text. - In case of a partial take-over, a **list of domains** to transfer, both as signed PDF and as plain text list. - When sending those documents to Openprovider, please inform us that you are aware of and approve the costs of the bulk transfer (see below). ### Process After receipt of the required documents and information, Openprovider will schedule the transfer together with the registry. Normally this can be scheduled within a week. The transfer will be completed by Openprovider and the registry, no further action from your side is required. After the transfer has finished, the domains, contacts and nameservers have been imported into your Openprovider account. From that moment on, you can manage your .be domains through Openprovider. Depending on the number of domains of the take-over, the import into Openprovider may take up to a couple of hours. That means that any updates must wait until the domain is in Openprovider. In case of urgent updates, we are able to assist you of course! Costs The costs of this kind of transfer depend on the number of domains involved: - 1 - 1.999 domains: € 500 - 2.000 - 4.999 domains: € 1.000 - 5.000+ domains: € 1.500 This is similar to the price that the registry charges to Openprovider. Even for a small portfolio the minimum fee of € 500 might be considerable, as it will save you a lot of manual effort and time: creation of contacts, retrieving the one-time authorization codes, starting the transfers, loss of registration period, et cetera. All prices mentioned are excluding VAT. **Domain renewals** Due to the billing processes of DNS Belgium, domains with their expiration date in the current month (between the 1st of the month and the date of import) will be renewed by Openprovider after the import. Be sure to enable auto-renewal in your account before initiating the bulk transfer, and ensure you have sufficient balance for the domains that will be renewed. ### Example notification to domain holders Often, the notification sent to domain holders is based upon the following example. This notification can be sent personally by e-mail, or included in a newsletter. The registry does not define the method of communication, they only require that domain holders are informed, and the notification should contain the following elements: - information about the new situation - confirmation that this operation is free of charge for them - confirmation that the expiration date remains unchanged - the notification that they may choose another registrar at any time (though such a transfer is not free) **Example notification text:** To simplify our administration and optimise our service to our customers, we will change the registrar of your .be domain(s). You will not notice anything from this change: your domain name will continue to function as it always did, the expiration date remains unchanged and no costs apply to this change. If you want to transfer your domain(s) to another registrar, you can do so at any moment. However, the new registrar will charge for such a transfer. ### Deleted and quarantined domains Domains for which a deletion date in the future was set or domains that are in quarantine are handled in a special way: - Quarantined domains are migrated to Openprovider's registry account, but we do not import them into your account. If you want to restore a domain from quarantine which was not imported, please contact our support department. The regular reactivation costs apply. - If you have set a deletion date for a domain name, Openprovider will remove that deletion date. The domain will autorenew at its expiration date. If you want to cancel such domain registration, set auto-renew to *off* for this domain. # Different transfer statuses and their meaning ## Question What do the different statuses in my transfer overview mean? ## Answer: You can find a complete list of all your transfers on the Transfer Overview Page, including the latest status. ![Screen_Shot_2021-09-07_at_16.31.27.png](https://openprovider.help/uploads/images/gallery/2026-08/embedded-image-0rklwe0q.png) In the list below you can find all the possible statuses from the transfer overview:
**Status****Explanation****Next steps?**
**In progress**The transfer is initiated and now in progress.In most cases, only patience is required. But we recommend to check the detailed TLD page --> *Transfer* section to see if any action (like email confirmation) or document is required to successfully finish this transfer.
**Scheduled**A date in the future was selected during the transfer request. The domain transfer is therefore not yet initiated. Wait until the selected transfer date.
**Completed \[new\]** Great, the transfer was successful!No further action is required. You could remove the domain-transfer from the transfer overview to keep the overview up-to-date.
**Locked \[new\]** It seems the domain is locked at the current provider, which prohibits the transfer.Please contact the current provider and request them to remove the transfer lock from the domain. In most cases you can confirm via the [whois](https://openprovider.com/domains/whois/) if the lock is successfully disabled. Status "ClientTransferProhibited" or "locked" is replaced by "OK". Simply click the "*Retry transfer*" button to retry the transfer immediately, using the same original settings.
**Invalid authorization code \[new\] **The provided transfer-code is not accepted by the registry.Please contact the current provider and request them to reset the transfer-code. Confirm with the old provider that the code is valid for external transfers. Got a new code? Simply click on the “*Change authorization code*” button, enter the new code and click on "Re*try transfer*". (See image below)
**Cancelled**This transfer has been cancelled by the reseller. You can delete it from the overview or start it again.
**Denied**The transfer is denied. In most cases this is caused by rejecting the verification link for the transfer.Review the transfer-process of this tld to see who will receive the confirmation email (registrant, admincontact or registrar). We advise to contact this party to accept the email in case you re-request the transfer.
**Expired**The transfer was not confirmed in time and therefore expired.Review the transfer-process of this tld to see which steps or email should have been confirmed
**Failed**The transfer is failed for an other reason.Please check your inbox for a system message with more details.
As you can see in the table, we are introducing 3 **\[new\]** statuses in our control panel: **COMPLETED, LOCKED & INVALID AUTH CODE** As these statuses are new in our system, they will only appear for transfers which were initiated after the introduction date of 2021-07-22. Completed or failed transfers before this date, will not be shown with this specific status in the overview. ### **New feature!** The new status " **INVALID AUTH CODE**" also comes with a new feature. No need to delete your old request when the code turns our to be invalid. Now you can easily replace the code via the same overview! Just click on the button “*Change authorization code*”, enter the new code and click on "*Retry transfer*". ![Screen_Shot_2021-09-08_at_14.32.20.png](https://openprovider.help/uploads/images/gallery/2026-08/embedded-image-ekmafrgi.png) # EURid: Taking over complete or partial account ## How to initiate a bulk transfer of .eu domain names Advantages of using the registry bulk transfer option: - all domains are moved at once - all handles are created automatically - nameserver settings are copied - expiration date stays unchanged - transfer codes are not required - can be used when you have an own registrar account or via a third party (partial transfer) ### Requirements - A completed and signed **bulk transfer form**. Please fill in your registrar ID, registrar name and address and sign the form. - A **copy of the note** that you sent or will send to your customers about this change, if this is different from the example text that is included on the second page of the bulk transfer form. See further down in this article for the requirements to such text. - In case of a partial take-over, a **list of domains** to transfer, both as signed PDF and as plain text list. - In case of a partial take-over, when sending those documents to Openprovider, please inform us that you are aware of and approve the costs of the bulk transfer (see below). - In case of a full take-over, be sure to send a [**termination request**](https://support.openprovider.eu/hc/article_attachments/360020316059) to EURid as well; only then, the full bulk transfer will be free of charge. You may send this form to us as well, so that we can send it to the registry together with the other documents. When planning the bulk transfer, note that you need to plan at least 3-5 days in advance, and the registry does not support bulk transfers on the first or last day of the month. ### Process After receipt of the required documents and information, Openprovider will schedule the transfer together with the registry. Normally this can be scheduled within a week. The transfer will be completed by Openprovider and the registry, no further action from your side is required. After the transfer has finished, the domains, contacts\* and nameservers have been imported into your Openprovider account. From that moment on, you can manage your .eu domains through Openprovider. Depending on the number of domains of the take-over, the import into Openprovider may take up to a couple of hours. That means that any updates must wait until the domain is in Openprovider. In case of urgent updates, we are able to assist you of course! ### Costs A EURid bulk transfer is free of charge, unless the registrar account is not terminated. Any additional customisations by Openprovider may be charged. A special quote will be made. In case of a partial take-over the costs are € 0,25 per domain name, with a minimum of € 500. This is similar to the price that the registry charges to Openprovider. In other words: if you transfer 2.000 domains or less, the price will be € 500. If you transfer more than 2.000 domains, the price will be the number of domains times € 0,25. For example, for a transfer of 10.000 domains, the price is € 2.500. But even for a small portfolio € 500 might be considerable, as it will save you a lot of manual effort and time: creation of contacts, retrieving the one-time authorization codes, starting the transfers, loss of registration period, et cetera. All prices mentioned are excluding VAT. ### Example notification to domain holders Often, the notification sent to domain holders is based upon the following example. This notification can be sent personally by e-mail, or included in a newsletter. The registry requires that domain holders are informed, but does not define the method of communication. **Example notification text:** To simplify our administration and optimise our service to our customers, we will change the registrar of your .eu domain(s). You will not notice anything from this change: your domain name will continue to function as it always did, the expiration date remains unchanged and no costs apply to this change. If you want to transfer your domain(s) to another registrar, you can do so at any moment. However, the new registrar will charge for such a transfer. ### Deleted and quarantined domains Domains for which a deletion date in the future was set or domains that are in quarantine are handled in a special way: - Quarantined domains are migrated to Openprovider's registry account, but we do not import them into your account. If you want to restore a domain from quarantine which was not imported, please contact our support department. The regular reactivation costs apply. - If you have set a deletion date for a domain name, Openprovider will remove that deletion date. The domain will autorenew at its expiration date. If you want to cancel such domain registration, set auto-renew to *off* for this domain. ### Terminating your EURid account You probably want to terminate your EURid account after the migration. In order finalize the termination EURid asks the registrar to confirm the security code which was sent to you upon accreditation. The security code is 12 digits long and looks like XXXX-XXXX-XXXX. This is the final security step to terminating the account. If you do not have this security code, please contact your EURid account manager. *\* All contacts, nameserver and DNSSEC data are copied, with one exception: the "whois e-mail address", the address that can optionally be assigned to a registrant object and which will be published in the whois, instead of the real registrant address. You will need to update these data after the import has been completed.* # Internal bulk transfer between two Openprovider resellers ## Question How to transfer a large number of domains/products between two Openprovider Reseller Accounts? ## Answer A single domain-transfer between 2 resellers works similar to a transfer from another registrar, it can be initiated via your control panel and, in most cases, will require a transfer code. The remaining registration period will also in most cases be transferred, which makes an internal transfer free of charge. (Exceptions might occur for some Tld's, the price is always shown in the control panel) If a large number of domains/products need to be transferred between two reseller accounts, (in case accounts are merged, split up or taken over), regular transfers may not be the most efficient way. In this case we can offer a manual procedure, done by our hard diligent 2nd line team. This procedure is in place and allows for an *internal bulk transfer* - a transfer of a larger number of domains between two Openprovider resellers that requires just two signatures on a transfer form. Apart from efficiency, the biggest advantage is that all contact data will be migrated as well and expiration dates do not change. The procedure is as follows: - Complete and sign the [internal bulk transfer form](https://support.openprovider.eu/hc/en-us/article_attachments/31026963626002); both the losing and the gaining reseller should sign and select the products that need to be transferred. - In case just a part of the account must be transferred, a list of the affected domains and products (only in case of partial transfers) must be sent in two formats: a list in plain text (e.g. a spreadsheet) and a list signed by both resellers. - As stated in the form, **the gaining reseller agrees on paying the fixed fee of €80 for the bulk transfer** and acknowledges that any additional services attached to the domain (including but not limited to trustee service, DNS zone, domain forwarding and whois privacy protection) will be taken over as well. - Openprovider will validate the bulk transfer with the losing and gaining reseller - After this validation, our 2nd line team will schedule for this transfer to take place (NOTE: this is a manual task and therefore not immediate). - Once completed you will receive a confirmation on the related support ticket. **Note:** For transferring domains and supported products from one account to multiple accounts, please use [this form](https://support.openprovider.eu/hc/article_attachments/36882338657554). - **We can transfer**: domain names, DNS zones (Openprovider and Sectigo Premium Anycast DNS), SSL certificates, and Plesk licenses. - **Currently, we're unable to transfer**: SpamExperts filters (per domain or bundles), Email Solution, and EasyDMARC. # Nominet (.uk): Taking over complete or partial account While registry Nominet has no official bulk transfer option to move a large portfolio to another registrar, we have created a process that allows for easy bulk transfer of up to 50.000 .uk (including .co.uk, .org.uk, .me.uk and .ltd.uk) domains. This process assumes you have access to the [Nominet registrar panel](https://secure.nominet.org.uk/). ## Full take-over The first step is to export a list of domain and contact data: 1. Log in to your Nominet account 2. Go to *Web Domain Manager*, choose *Manage Domains* 3. At the bottom, click *Download List...* (note that this list is limited to 50.000 domains; if you have more domains, you can use the [REST API of Nominet](https://registrars.nominet.uk/uk-namespace/registration-and-domain-management/registration-systems/list-api/rest-api/); this will, however, give a different output format and should be investigated by us before continuing this page) 4. Run the attached PHP script with the following two command line parameters: 1. filename of the exported file from Nominet 2. standard telephone number to use, format +31.123456789. Reason: the exports from Nominet don't include the phone number 3. Example call: ``` php convert-nominet-export-into-csv-bulk-transfer.php nominet-domain-export.csv "+31.101234567890" ``` 5. You can tune the resulting output file (nominet-bulk-csv.csv) with the correct telephone numbers, if desired. Also any other fixes to the data can be made. 6. Send us your converted list. Openprovider has tools in place to initiate transfers based on this CSV file. We will confirm you once we have initiated all transfers. At that moment, you should (within 7 days) change the IPS tag of the domains: 1. Log in again to your Nominet account 2. Go to *Web Domain Manager*, choose *Manage Domains* 3. Select all domains on that page 4. Click the *Release* button 5. Enter Openprovider's IPS tag *REGISTRAR-EU* 6. Accept the tag change 7. Go back the the domain list 8. and select the next set of domains Now all domains will be pushed to Openprovider. You will see them being activated over the next minutes. ## Partial take-over This method works best with a full registrar take-over. If it's a partial take-over, the following steps change: - After downloading the CSV file with all domains, remove all domains from that file that should *not* be transferred. - Instead of selecting "all" domains for a tag change, only those domains that are subject to the partial take-over must be checked. # Overview of all available transfer options ## Question Which (bulk)transfer options are available and how to request them? ## Answer A transfer can be started via several channels, like the RCP (Reseller Control Panel / web interface), an API connection or via a plugin like WHMCS, Blesta etc. In this article, we will focus on the 4 options that you will find when using the Openprovider control panel, in the section "[*Transfers*](https://cp.openprovider.eu/web/action/index#/domain/transfer)" ![Screen_Shot_2021-12-14_at_19.57.40.png](https://openprovider.help/uploads/images/gallery/2026-08/embedded-image-azmbfqvg.png) **Regular Domain Transfer** Via the regular domain transfer page you can start a single domain transfer or a batch of domains. Be aware that all domains in this batch will be connected to the same handles and the same nameservers which you will select in later steps. **CSV Transfer** Got a list of domains to transfer? No problem! In that case we advise to use the CSV template from the control panel and insert a maximum of 500 domains per batch. In the CSV file you can indicate per domainname which handles or new contacts and nameservers or nameservergroups can be used. You even have the option to add a transferdate, making this an ideal option when you are migrating your portfolio from a previous provider or are transferring big batches of domains for your clients. We do advise to set the transfer date a few days before the actual expiration of the domain, as some tlds will take a few days to get transferred and always keep the auto renewal enabled at the previous provider to avoid issues. Detailed information can be found [here](https://openprovider.help/books/domains/page/using-the-csv-transfer-option). **Registry Bulk Transfer** Some registries offer the option to migrate a whole portfolio at once. This is ideal if you would like to consolidate your domains in 1 account and want to save money on all the Registry administration fees. In most cases it is only required to sign a form, that it! Openprovider will handle the communication with the Registry and the import of the domains. This is an ideal option when you have your own Registry account or (only when supported by the registry) when you have a large amount of the same TLDs at an other registrar. As most registries will charge an administrative fee, this option is mostly interesting with 100+ domains. See all available registry bulk transfer options [here!](https://openprovider.help/books/domains/page/registry-account-bulk-transfers) **Robot Transfer** Openprovider has developed some Transfer Robots, giving you the option to migrate your domain portfolio from some of the biggest registrars to Openprovider, all fully automated. Openprovider will make sure all transfers will be initiated on time, saving you time, money and effort! Want to know for which Registrars we offer this automated solution? Just get in touch with our [Sales Team](mailto:accounts@openprovider.com), who will provide you with all the information. # Registry account bulk transfers If you are registrar, or if you manage a number of domains in one extension at just one registrar, the transfer of those domains might be possible on registry-registrar level. Such a bulk transfer has many advantages: - It's easy: in most cases, signing a form is sufficient - It's non-interruptive: end users / domain holders do not need to give their explicit approval - It's cheap in registration period: you do not loose registration period - It's cheap in management: completed in one time, no lengthy process, no end user interaction - It's cheap in money / cashflow: often just a one-time fee is required, and not the transfer costs of all domains ## Supported registries Openprovider supports registry bulk transfers for the following registries. The procedures in general are all form-based like the .be and .eu bulk transfers; details will be provided on a case-by-case base. - [SIDN](https://openprovider.help/books/domains/page/sidn-nl-bulkverhuizing-portfolio-overname) (.nl domains) - [DNS Belgium](https://openprovider.help/books/domains/page/dns-belgium-taking-over-complete-or-partial-account) (.be domains) - [EURid](https://openprovider.help/books/domains/page/eurid-taking-over-complete-or-partial-account) (.eu domains) - [Nominet](https://openprovider.help/books/domains/page/nominet-uk-taking-over-complete-or-partial-account) (.uk / .co.uk domains) - **.com, .net, .name, .jobs** (Verisign): 1/12 of a domain's price per domain with a minimum of $5.000 and a maximum of $50.000 per extension per current registrar More information about this process [here](https://www.icann.org/en/system/files/files/verisign-btappa-request-29jul09-en.pdf). - **.fr** (AFNIC): € 2 per domain with a minimum of € 1.000; personalized quotes possible for higher volumes - **.in** (NIXI): minimum number of domains is 50; free of charge up to 10.000 domains; above 10.000 domains the migration fee is INR 10.000. - **.it** (NIC IT): € 0,50 per domain with a minimum of € 250 - **.lt** (Domreg.LT): only available when closing your registrar account (only full portfolio consolidations); free of charge - **.lu** (DNS LU): only available when closing your registrar account (only full portfolio consolidations); free of charge - **.me**: one-time costs around € 1.000 - **.pl** (NASK): PLN 1,00 per domain with a minimum amount of PLN 4.000 and a maximum amount of PLN 50.000 - **.pt** (DNS PT): free of charge - **.us** (Neustar): $0,20 per domain with a minimum of $1.000 - **gTLDs** (other than .com, .net, .name and .jobs): it depends on the registry whether or not bulk transfers are supported; costs are normally starting at $ 5.000 per TLD For any registry that is not listed, please contact support for more information. Openprovider has exhaustive experience in bulk transfers and consolidation and will always be able to find a solution for your specific case. # SIDN (.nl) bulkverhuizing / portfolio-overname This article is in Dutch as it will be primarily used by Dutch people. If you need an English explanation of this process, please contact us. **SIDN overname / bulkverhuizing** SIDN ondersteunt een bulkverhuizing, waarbij de domeinen in 1x direct overgezet worden naar een ander SIDN registrar Account. Het voordeel is dat op deze manier er geen tussenkomst van de registrant nodig is en er geen verhuiscodes nodig zijn. De registrant hoeft geen toestemming te geven en zal geen bericht ontvangen van deze overname. [**Gehele overname (je bent zelf rechtstreeks bij SIDN aangesloten):**](https://openprovider.help/books/domains/page/sidn-overname-bulkverhuizing-gehele-overname) Openprovider kan zeer eenvoudig je gehele SIDN account overnemen middels een account overname. De stappen staan in [dit artikel](https://openprovider.help/books/domains/page/sidn-overname-bulkverhuizing-gehele-overname) beschreven. [**Gedeeltelijke overname (je huidige provider is registrar van SIDN):**](https://openprovider.help/books/domains/page/sidn-overname-bulkverhuizing-gedeeltelijke-overname) Ook als je niet zelf rechtstreeks bij SIDN aangesloten hebt, kan Openprovider zeer eenvoudig je .nl domeinen overnemen middels een gedeeltelijke account overname. De stappen staan in [dit artikel](https://openprovider.help/books/domains/page/sidn-overname-bulkverhuizing-gedeeltelijke-overname) beschreven. # SIDN overname / bulkverhuizing - Gedeeltelijke overname This article is in Dutch as it will be primarily used by Dutch people. If you need an English explanation of this process, please contact us. **Stap 1) Indienen van de formulieren.** Voor een gedeeltelijke account overname moet het volgende formulier ingevuld en ondertekend worden door de **huidige** registrar van SIDN. - [Formulier voor gedeeltelijke overname domeinnamen](https://support.openprovider.eu/hc/article_attachments/115021523088) ([English version](https://support.openprovider.eu/knowledge/articles/216649228/en-us?brand_id=3280526&return_to=%2Fhc%2Fen-us%2Farticles%2F216649228)) Daarnaast hebben we de volgende documenten nodig: \- een lijst met domeinnamen nodig in pdf versie **inclusief een paraaf van de huidige registrar** op iedere pagina **EN** \- de lijst domeinen in digitaal formaat om te kunnen verwerken in het systeem. (dus dezelfde lijst domeinen, maar op 2 manieren aangeleverd, in excel en in pdf) Deze formulieren kunnen verzonden worden naar (Gelieve niet naar de support afdeling) Nadat we de formulieren ontvangen hebben, zullen we het verhuisproces in gang zetten op de door jouw gewenste uitvoerdatum. SIDN rekent hiervoor gemiddeld 2 werkdagen. **Belangrijk**: de ondertekening moet gebeuren door een rechtmatig bevoegde hiertoe. Dit is iemand die zowel in het KvK-register vermeld staat als binnen het DRS-systeem van SIDN opgegeven is als contactpersoon. Als het om een verhuizing van meer dan 10.000 domeinen gaat, dient de ondertekenaar tevens in het KvK tekenbevoegd te zijn voor een bedrag hoger dan €50.000. Mocht het niet duidelijk zijn welke velden er ingevuld moeten worden door de huidige registrar, kijk dan even naar het [voorbeeld](https://support.openprovider.eu/hc/article_attachments/28701223379986). De velden met een pijl dienen ingevuld te worden, de overige velden vullen wij in. **Stap 2) Vervaldata** Er zijn enkele opties hoe we om kunnen gaan met de verlengdata van de domeinen. Hieronder beschrijven we de 2 opties. Graag horen we voor de overname welke optie de voorkeur heeft. Optie 1) Data gelijk laten lopen aan je eigen boekhouding Stel dat jij je klant per jaar factureert. Dan kunnen we bij de import deze datum uit je boekhouding aanhouden. Voorbeeld: Je factureert je klant op 20 april voor een verlenging van een domein. Op 10 januari voeren we de overname uit. De periode tussen 10 januari en 30 maart is reeds door jou betaald bij SIDN, dit zal niet dubbel gefactureerd worden. De periode vanaf het moment dat er bij SIDN niet meer betaald is voor het domein t/m de maand waarin het domein verlengd moet worden (datum die jij aanlevert) zullen we bij de import in rekening brengen. (In dit voorbeeld 1 maand) Daarna gaat de jaarfacturatie in en zullen we ieder jaar op deze datum het domein verlengen. Het enige wat we hiervoor nodig hebben is een excel lijst met je domeinnamen en je gewenste verlengdatums uit je boekhouding. (formaat: yyyy-mm-dd) Optie 2) Alle domeinen worden voor een jaar verlengd op het moment dat er bij SIDN niet meer voor betaald is. Stel dat je op dit moment je account op kwartaalfacturatie hebt staan. Je kiest ervoor om bij de overname alle domeinen in 1x te verlengen voor 1 jaar. Dat betekend dat het moment van importeren er geen registratiekosten gemaakt worden. Als het moment aanbreekt dat het kwartaal over is en de domeinen verlengd moeten worden, dan worden alle domeinen voor 1 jaar verlengd. **Let er echter wel op** dat registrars niet per definitie dezelfde verlengdatum richting u als klant communiceren als dat er bij SIDN bekend is. Het kan zo zijn dat een domeinnaam welke door jullie voor een jaar betaald is, door de registrar per kwartaal verlengd en betaald word aan SIDN. Je kunt bij je huidige provider nagaan tot wanneer zij voor de domeinen bij SIDN betaald hebben. Het kan dus voorkomen dat je bij een verhuizing de registratieperiode die je aan je huidige provider betaalt hebt, verliest. Wij zullen pas kosten in rekening brengen vanaf het moment dat er bij SIDN niet meer voor het domein betaald is. **Ons advies** Bij de eerste optie worden de registratiekosten over het jaar uitgespreid. Bij de tweede optie heb je alle registratriekosten op 1 moment in het jaar. Wij adviseren om de kosten over het jaar te spreiden (optie 1), zodat je cashflow beter verdeeld is en je minder risico loopt dat de domeinen in 1 keer niet verlengd worden wegens onvoldoende saldo, aangezien het bedrag kan oplopen, naarmate de grote van je portfolio. **Stap 3) De import** Bij de import zullen alle klant gegevens 1 op 1 overgenomen worden. Tijdens de import zullen dubbele handels van de import gefilterd worden zodat er per klant slechts 1 nieuwe handle over zal blijven. **Stap 4) Saldo en kosten** Op het moment van verhuizen met optie 1 dient er een saldo op het account te staan. Mocht je met aangeleverde data verhuizen (optie 1), dan kan Openprovider op basis van je aantal domeinen een schatting geven hoeveel saldo er nodig is bij het overzetten. Meestal rekenen we met gemiddeld een half jaartarief per domein; als je een Membership hebt is dat €1,80 exclusief btw. Gaat de voorkeur uit naar verhuizen zonder aangeleverde data (optie 2), dan betaal je de jaarregistratiekosten op het moment dat er voor de domeinen niet meer bij SIDN betaald is. Dit bedrag is zelf eenvoudig uit te rekenen, namelijk volume x registratieprijs. SIDN rekent eenmalig € 64.50 voor een **gedeeltelijke bulk .NL-verhuizing**. Dit bedrag wordt afgeschreven van het tegoed op je Openprovider-account. **Let op:** voor een volledige overname, waarbij een registrar zijn SIDN-accreditatie volledig beëindigt en alle onderliggende .NL-domeinen naar Openprovider migreert, worden geen kosten in rekening gebracht. Kostenvoorbeeld: Indien je 200 domeinen wilt overzetten gaan we uit van een benodigd saldo van: 200 domeinen x maandprijs a 0,31\* x gemiddeld 6 maanden = € 372 Inclusief SIDN administratiekosten en 21% btw kom je op een gemiddeld benodigd saldo van € 512,- \* in geval van een actief membership. **Overige punten:** - Let op, DNSSEC instellingen worden tijdens een verhuizing standaard niet meegenomen. Wil je dit wel, laat het ons dan weten voordat je de verhuizing aanvraagt. Als domeinen eenmaal zonder DNSSEC zijn overgenomen, kunnen we DNSSEC niet eenvoudig meer op een later moment toevoegen. - Domeinen worden, indien mogelijk, automatisch aan een bestaande nameservergroep gekoppeld. Dit gebeurt uiteraard alleen als de nameservers van het domein exact overeenkomen met de nameservers in een bestaande nameservergroep. - Domeinen welke op moment van verhuizen in quarantaine staan, zullen niet meeverhuisd worden. - In de whois zal bij .nl domeinen onze anonieme naam: registrar.eu vermeld worden. Daarnaast is het ook mogelijk om bij .nl domeinen zelf als reseller in de whois vermeld te worden. Voor meer informatie over deze optie en hoe je dit kunt instellen vind je [hier](http://support.openprovider.eu/entries/58791166-Reseller-in-whois). Als je dit direct bij de import wilt aanpassen, stuur ons dan de gewenste handle toe. - Domeinnamen met .nl control nemen wij mee. De .nl control zal actief blijven. De domeinnaamhouder krijgt bij de overname wel bericht van de wijziging. - Domeinnamen met een juridische beperking worden ook meegenomen bij de overname. De domeinnaamhouder krijgt bij de overname geen bericht van de wijziging. - In [uitzonderlijke gevallen](https://openprovider.help/books/domains/page/waarom-ontvangen-mijn-klanten-e-mails-over-houderwijzigingen-van-sidn-na-een-overname) moeten wij een nieuwe handle voor de houder definiëren. Hiervan ontvangt het administratief contact een e-mail van SIDN. - In sommige (oude) gevallen heeft SIDN geen e-mailadres van een contact. Hiervoor zullen we jou vragen om een e-mailadres dat we kunnen gebruiken voor al deze contacten. Wij adviseren een role-based adres zoals support@reseller.nl. # SIDN overname / bulkverhuizing - Gehele overname This article is in Dutch as it will be primarily used by Dutch people. If you need an English explanation of this process, please contact us. **Stap 1) Indienen van de formulieren.** Voor een gehele account overname moeten de volgende 2 formulieren ingevuld en ondertekend worden. - [SIDN formulier overname en sluiten account.pdf](https://support.openprovider.eu/hc/article_attachments/360003139788/SIDN%20formulier%20overname%20en%20sluiten%20account.pdf) ([English version](https://support.openprovider.eu/hc/article_attachments/360028008713/Full_domain_name_takeover_request.pdf)) -
[SIDN formulier Inzage domeinen.pdf](https://support.openprovider.eu/hc/article_attachments/360003220927/SIDN%20formulier%20Inzage%20domeinen.pdf) ([English version](https://support.openprovider.eu/hc/article_attachments/360027163234/Domain_name_report_request.pdf))
**Belangrijk**: de ondertekening moet gebeuren door een rechtmatig bevoegde hiertoe. Dit is iemand die zowel in het KvK-register vermeld staat als binnen het DRS-systeem van SIDN opgegeven is als contactpersoon. Als het om een verhuizing van meer dan 10.000 domeinen gaat, dient de ondertekenaar tevens in het KvK tekenbevoegd te zijn voor een bedrag hoger dan €50.000. Deze formulieren kunnen verzonden worden naar (Gelieve niet naar de support afdeling) Nadat we de formulieren ontvangen hebben, zullen we het verhuisproces in gang zetten op de door jouw gewenste uitvoerdatum. SIDN rekent hiervoor gemiddeld 2 tot 3 werkdagen. **Stap 2) Financiële verplichtingen SIDN** Zorg ervoor dat er geen openstaande financiële verplichtingen meer aan SIDN bestaan. SIDN kan een account niet sluiten zolang er openstaande rekeningen zijn. **Stap 3) Vervaldata** Er zijn 2 opties hoe we om kunnen gaan met de verlengdata van de domeinen. Hieronder beschrijven we de 2 opties. Graag vernemen wij voor de overname welke optie de voorkeur heeft. Optie 1) Data gelijk laten lopen aan je eigen boekhouding Stel dat jij je klant per jaar factureert maar bij SIDN altijd voor kwartaalfacturatie hebt gekozen. Dan lopen de vervaldata van SIDN en jouw eigen systeem niet gelijk aan elkaar. Wij kunnen tijdens de import de domeinen synchroniseren en de datum uit je boekhouding aanhouden. Dit doen we met behulp van tussentijdse maandverlengingen (die onzichtbaar zijn voor jou en je klant). Een voorbeeld ter verduidelijking. Stel je hebt het bepaald domein met de volgende data: - Datum waarop je je klant factureert: 2019-10-23 - Vervaldatum bij SIDN op het moment van de import: 2019-04-18 Wij synchroniseren tot de opgegeven datum, dat is 23 oktober. De huidige vervaldatum is 18 april, dus we verlengen met maandelijkse stappen tot het eerste moment op of na de eerstvolgende 23 oktober. Dat is 18 november 2019, dus we zullen 7x een maandverlenging doen. De uiteindelijke situatie voor dit domein is dan: - Vervaldatum bij SIDN: 2019-11-18 - [Verlengdatum bij Openprovider](https://openprovider.help/books/quick-start/page/renewal-policies-in-openprovider): 2019-11-16 - Datum waarop je je klant factureert: 2019-10-23 - maar uiteraard kan je ervoor kiezen om de datum naar je klant weer met Openprovider te synchroniseren. Op het moment van de import betaal je voor 7 maanden verlenging en de eerstvolgende verlenging die je doet in Openprovider is pas op 16 november. Een aantal opmerkingen hierover: - Als je een datum opgeeft die een jaar in de toekomst ligt, zullen we 12x een maandverlenging doen. Dit is iets duurder dan 1x een jaarverlenging. Daarom adviseren we je om geen data op te geven die meer dan een jaar in de toekomst liggen. - De maandverlengingen betaal je op het moment van de import, maar wij zullen bij SIDN elke maand apart verlengen. Om bij het bovenstaande voorbeeld te blijven: als je al op 10 juli het domein opheft of wegverhuist, dan is de vervaldatum bij SIDN 18 juli 2019. Deze datum neemt de nieuwe registrar over. De periode tussen 18 juli en 18 november (4 maanden) waarvoor je al wel betaald hebt, is dan verloren. Wij geven geen restitutie in dergelijke gevallen. - Het kan zijn dat de dag van de maand die je opgeeft niet overeenkomst met de dag van de maand die SIDN heeft staan (bijvoorbeeld, ervan uitgaande dat we de import in januari doen: je geeft 14 juli op, SIDN heeft 20 maart staan). In dat geval zorgen we ervoor dat het domein *tenminste* tot de opgegeven datum loopt. In dit geval wordt er 4 maanden verlengd tot 20 juli. Als we namelijk voor 20 *juni* hadden gekozen, dan moet het domein verlengd worden voordat jij je klant factureert. Wil je voor deze optie gaan? Het enige wat we hiervoor nodig hebben is een lijst met je domeinnamen en je gewenste verlengdata in het formaat yyyy-mm-dd. Mocht het lastig zijn om deze gegevens uit je eigen systeem te halen, dan kunnen we ook de rapportage van SIDN gebruiken welke we toegezonden krijgen voor de overname. Hieruit gebruiken we dan de "datum in beheer", dit is de datum waarom de domeinnaam ook ooit bij jullie in het beheer is gekomen en komt in veel gevallen overeen met de datum waarom jullie de klant factureren. Optie 2) Alle domeinen worden voor een jaar verlengd op het moment dat er bij SIDN niet meer voor betaald is. Stel dat je op dit moment je account op kwartaalfacturatie hebt staan. Je kiest ervoor om bij de overname alle domeinen in 1x te verlengen voor 1 jaar. Dat betekend dat het moment van importeren er geen registratiekosten gemaakt worden. Als het moment aanbreekt dat het kwartaal over is en de domeinen verlengd moeten worden, dan worden alle domeinen voor 1 jaar verlengd. Ons advies Bij de eerste optie worden de registratiekosten over het jaar uitgespreid. Bij optie 2 heb je alle registratriekosten op 1 moment in het jaar. Wij adviseren om de kosten over het jaar te spreiden (optie 1), zodat je cashflow beter verdeeld is en je minder risico loopt dat de domeinen in 1 keer niet verlengd worden wegens onvoldoende saldo, aangezien het bedrag kan oplopen, naarmate de grootte van je portfolio. **Stap 4) De import** Bij de import zullen alle klant gegevens 1 op 1 overgenomen worden. Tijdens de import zullen dubbele handels van de import gefilterd worden zodat er per klant slechts 1 nieuwe handle over zal blijven. **Stap 5) Saldo en kosten** Op het moment van verhuizen (optie 1 en 2) dient er een saldo op het account te staan. Mocht je met aangeleverde data verhuizen (optie 1), dan kan Openprovider op basis van je aantal domeinen een schatting geven hoeveel saldo er nodig is bij het overzetten. Meestal rekenen we met gemiddeld een half jaartarief per domein; als je een Membership hebt is dat €1,80 exclusief btw. Gaat de voorkeur uit naar verhuizen zonder aangeleverde data (optie 2), dan betaal je de jaarregistratiekosten op het moment dat er voor de domeinen niet meer bij SIDN betaald is. Dit bedrag is zelf eenvoudig uit te rekenen, namelijk volume x registratieprijs. SIDN rekent € 51 administratiekosten voor het overzetten van het account. Deze kosten berekenen wij door middels je tegoed op je Openprovider account. Kostenvoorbeeld: Indien je 200 domeinen wilt overzetten gaan we uit van een benodigd saldo van: 200 domeinen x maandprijs a 0,31\* x gemiddeld 6 maanden = € 372 Inclusief SIDN administratiekosten en 21% btw kom je op een gemiddeld benodigd saldo van € 512,- \* in geval van een actief membership. **Overige punten:** - Let op, DNSSEC instellingen worden tijdens een verhuizing standaard niet meegenomen. Wil je dit wel, laat het ons dan weten voordat je de verhuizing aanvraagt. Als domeinen eenmaal zonder DNSSEC zijn overgenomen, kunnen we DNSSEC niet eenvoudig meer op een later moment toevoegen. - Domeinen worden, indien mogelijk, automatisch aan een bestaande nameservergroep gekoppeld. Dit gebeurt uiteraard alleen als de nameservers van het domein exact overeenkomen met de nameservers in een bestaande nameservergroep. - Domeinen welke op moment van verhuizen in quarantaine staan, zullen niet meeverhuisd worden. - In de whois zal bij .nl domeinen onze anonieme naam: registrar.eu vermeld worden. Daarnaast is het ook mogelijk om bij .nl domeinen zelf als reseller in de whois vermeld te worden. Voor meer informatie over deze optie en hoe je dit kunt instellen vind je [hier](http://support.openprovider.eu/entries/58791166-Reseller-in-whois). Als je dit direct bij de import wilt aanpassen, stuur ons dan de gewenste handle toe. - Domeinnamen met .nl control nemen wij mee. De .nl control zal actief blijven. De domeinnaamhouder krijgt bij de overname wel bericht van de wijziging. - Domeinnamen met een juridische beperking worden ook meegenomen bij de overname. De domeinnaamhouder krijgt bij de overname geen bericht van de wijziging. - In [uitzonderlijke gevallen](https://openprovider.help/books/domains/page/waarom-ontvangen-mijn-klanten-e-mails-over-houderwijzigingen-van-sidn-na-een-overname) moeten wij een nieuwe handle voor de houder definiëren. Hiervan ontvangt het administratief contact een e-mail van SIDN. - In sommige (oude) gevallen heeft SIDN geen e-mailadres van een contact. Hiervoor zullen we jou vragen om een e-mailadres dat we kunnen gebruiken voor al deze contacten. Wij adviseren een role-based adres zoals support@reseller.nl. # Using the CSV transfer option ## Question How to use the CSV transfer option in the control panel? ## Answer The CSV transfer option is very useful when you want to transfer multiple domains with different data or different transfer dates. Just follow the steps in the control panel to get this started! [1. Download the CSV template](#bkmrk-1.-download-the-csv--1) [2. Fill in the CSV template](#bkmrk-2.-fill-in-the-csv-t-1) [3. Upload and parse CSV file](#bkmrk-3.-upload-and-parse--1) [4. Start transfers!](#bkmrk-4.-start-transfers%21-1) - [FAQ](#bkmrk-faq) - [CSV template Details](#bkmrk-csv-template-details) ### 1. Download the CSV template ![image-20210920-151236.png](https://openprovider.help/uploads/images/gallery/2026-08/embedded-image-pvj43nv6.png) Always start with downloading the CSV template from the control panel. Save this as .csv on your computer and make sure not to adjust the file format (no xls, xlsx, ods, txt etc) ### 2. Fill in the CSV template Open the CSV and add the required information. The CSV might look intimidating, but in most cases, the information can be copied and pasted from the current provider, or existing Openprovider handles can be used. Please note that the format of the template may **not be adjusted**. It is not possible to add or remove columns or rows as this will make the file invalid during upload. Not all fields are mandatory to fill in. Click here for [full CSV details](#bkmrk-csv-template-details) for a description of how to fill in the fields. The limit is 500 domain transfers per file. ### 3. Upload and parse the CSV file Once the file is prepared, is time to upload it. Use the upload button or just drag en drop the file in place. The control panel will check if the file is correct. For instance: - File format (for example make sure it’s a CSV and not a PDF) - File structure (making sure no columns are missing from the file) - Values in the file (for example checking that the date format or the phone number format is correct) In case errors are detected in the file , the control panel will show them directly: ![Screenshot_2021-09-20_at_16.19.55.png](https://openprovider.help/uploads/images/gallery/2026-08/embedded-image-zhqbr6ui.png) Please correct the errors in your CSV file and upload the file again. In case an error description is not clear, let us know via and we will explain how to resolve the problem in the file. ### 4. Start Transfers! When the CSV file is correct and successfully uploaded, the control panel will take you to the next page: “Start Transfer”. On this page you can review all the domain transfers from the CSV file and make changes if required, for instance: - Remove a domain transfer from the list - Change an invalid authorization code - Unlock a domain and refresh the status ![Screenshot_2021-11-22_at_17.09.56.png](https://openprovider.help/uploads/images/gallery/2026-08/embedded-image-lvapwcxa.png) Note: `Registry unreachable` → shown when a registry doesn’t respond, in this case, we can’t determine if the domain is locked or available for transfer. Usually occurs when a Registry is unavailable due to maintenance. Once satisfied with the results, click on **“Start the Transfer”** The control panel will create the domain transfers in the system. It might take a few minutes for these domain transfers to appear in the transfer overview. Just have patience, this delay is completely normal because this is a task executed in the background, so you can continue other actions in your control panel. **Note**: ***If you encounter any issues with CSV transfer via RCP, please submit a request to [support](https://openprovider.help/books/quick-start/page/contact-openprovider-support) using the attached [template](https://support.openprovider.eu/hc/article_attachments/18316726438546) and we will process it. There should be no “ - “ in column names. Column “Owner address” should be separated into “Owner street”, “Owner address number” and “Owner suffix”. If the Admin handle needs to be the same as Owner, you don’t need to fill in the contact data, but specify in the “Owner” column value “0”. If the ‘Owner’ column is empty and not all info for the new handle is provided, an error will be returned. Same for Tech handle - “0” if it needs to be the same as Owner.*** ### FAQ Do you have questions after reading the documentation? Please check if your question is already answered in the scenarios below: **Q:** I see a transfer price mentioned in the transfer overview, will this be directly charged when i start the transfer? **A:** No, this is an estimated transfer price for each domain. In case the domain is scheduled with a date in the future, the complete balance does not need to be present in the control panel yet. Prices mentioned at this stage are an estimation and subject to changes, for instance: - When a domain transfer fails or a domain is locked we won’t execute that transfer, therefore it won’t be charged. - Registries can always change their price and that can affect the transfer price at the moment the transfer is executed. **Q:** What happens if my **balance** is not sufficient for the whole amount at the moment I upload the CSV file? **A:** When you upload your CSV file and click on the button “Start the transfer” our system will check for each domain transfer you schedule if you have enough funds. This is not a cumulative check, however. In other words, the check is executed against the single domain transfer price and not against the total sum. In case the transfers are scheduled with a date in the future, there will be no balance reserved yet. This will only be done at the moment the transfer is executed. In case the transfer is started immediately, the transfer will be initiated and the transfer fee will be invoiced. **Q:** What will happen if a domain is currently **locked** or a code is **invalid**, but I continue to transfer them anyway? **A:** In case the transfer date is in the future: The domain transfer will be correctly created in the status “**Scheduled**”. However, when the execution date comes the domain transfer will fail unless the domain was unlocked in the meantime or the code was updated in the scheduled transfer request in the meantime. In case the transfer date is immediately: In this case the transfer is supposed to start immediately, but because of the locked domain or invalid code, there will be an error popping up in the control panel and the transfer will not be created. **Q:** Some extensions require **additional data**, how do I manage this? **A:** Correct, some domain extensions, for instance, the ccTLDs, can require additional data in the handle (like a social security number or VAT number). This data unfortunately cannot be specified in the CSV file. When additional data is required, the easiest workaround is to manually [create the handle](https://cp.openprovider.eu/web/action/index#/customer/new) in the control panel and provide the handle reference in the CSV file. Another option is to import the CSV file first, so our system can create the handle for you. Afterwards, you can add the additional data to the handle via the [handle management menu](https://cp.openprovider.eu/web/action/index#/customer/overview). We always advise you to [get familiar](https://openprovider.help/books/domains/page/what-is-a-domain-transfer-and-how-does-it-work) with the extension requirements and transfer process via our Knowledge Base before starting a transfer. **Q:** I just started a CSV Transfer, however, I got a few notifications for some errors in RCP. Where can I see the full list of errors generated by a CSV Transfer? **A:** Even if you carefully prepared your CSV file something might go wrong. For instance, you don’t have enough funds in your account or you haven’t accepted yet the contract required for a specific domain extension. You will get a notification error in RCP for this and the corresponding domain transfer will not be created. All the errors generated when starting a new CSV transfer can always be seen on the following RCP page: [https://cp.openprovider.eu/web/action/index#/bulk/overview](https://cp.openprovider.eu/web/action/index#/bulk/overview%E2%80%9D "https://cp.openprovider.eu/web/action/index#/bulk/overview%E2%80%9D") **Q:** Can the CSV also be used for internal transfers? (Domains which are currently managed by a different Openprovider reseller) **A:** Yes, you can use CSV Transfer also to schedule an internal transfer. Just make sure you have the right auth code and domain contact data. ### **CSV Template Details**
**Name****Required****Format****Notes**
**Domain name**![:check_mark:](https://pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net/atlassian/check_mark_32.png)domainname.extension
**Nameservers** array of hostnames or IPV4 addresses (separated by ;) - for instance ns1.mydomain.com; ns2.mydomain.comGlue records are not supported
**Nameserver group** Alphanumerical string, for instance dns-openprovider (this will use our default nameserver group)Provide the ns-group name If both the Nameservers and Nameserver group columns are left empty, then the system will use the default Openprovider DNS. If the user specifies both the Nameservers and the Nameserver group columns, then the Nameserver group value will be used. DNS templates are not supported
**Owner – Openprovider handle** AB012345-NL (as it can be found within RCP)
**Owner – internal reference** any alphanumerical string that reseller prefersThis is a unique customer code that the reseller can specify (for example it’s used by their own administration/database). When an Internal Reference is specified, Openprovider will create only one handle for each customer in RCP. If in a domain further below the same code is used, then Openprovider will not create a new handle but re-use the previously created handle and ignore the data in the spreadsheet. If a user specifies both Openprovider handle and Internal reference, then the system will use the Internal reference value.
**Owner – company name** alphanumerical with special characters
**Owner – first name** alphanumerical with special characters
**Owner – last name** alphanumerical with special characters
**Owner – address** alphanumerical with special characters
**Owner – zipcode** depends on the city
**Owner – city** alphanumerical with special characters
**Owner – state/province** alphanumerical with special characters
**Owner – country code** ISO 3166-1 alpha-2 country codesThe complete list of country codes can be found [here](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2):
**Owner – phone country code** Example: +31 / +34 / +91 / +7
**Owner – phone area code** number onlyIs the digit right after the phone country code, for instance: +31 6 2727282 - in this case it would be the 6
**Owner – phone subscriber number** number onlyIs the remaining part of the phone number
**Owner – fax country code** Same logic as the phone number
**Owner – fax area code**
**Owner – fax subscriber number**
**Owner – e-mail** standard email format
**Admin – Openprovider handle** Same logic described for the Owner handle VS Owner internal reference
**Admin – internal reference**
**Admin – company name**
**Admin – first name**
**Admin – last name**
**Admin – address**
**Admin – zipcode',**
**Admin – city**
**Admin – state/province**
**Admin – country code**
**Admin – phone country code**
**Admin – phone area code**
**Admin – phone subscriber number**
**Admin – fax country code**
**Admin – fax area code**
**Admin – fax subscriber number**
**Admin – e-mail**
**Tech – Openprovider handle**
**Tech – internal reference**
**Tech – company name**
**Tech – first name**
**Tech – last name**
**Tech – address**
**Tech – zipcode**
**Tech – city**
**Tech – state/province**
**Tech – country code**
**Tech – phone country code**
**Tech – phone area code**
**Tech – phone subscriber number**
**Tech – fax country code**
**Tech – fax area code**
**Tech – fax subscriber number**
**Tech – e-mail**
**Auth code**![:check_mark:](https://pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net/atlassian/check_mark_32.png) Required for all tld's that require a transfercode for successful transfer. This code can be adjusted later.
**Transfer date**![:check_mark:](https://pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net/atlassian/check_mark_32.png)**yyyy-mm-dd**The transfer date is always required. It can be the same day in case of a transfer scheduled to start immediately.
**Important Note**: *Owner, Admin, and Tech handles are required for the successful transfer of domains. You can either specify an existing handle or provide information (Company name, first name, last name, address, etc.) required to create new handles. If the Admin handle needs to be the same as the Owner, you don’t need to fill in the contact data, but specify in the “Admin” column value “0”. If the ‘Owner’ column is empty and not all info for the new handle is provided, an error will be returned. Likewise for "Tech" - “0” if it needs to be the same as Owner.* # Waarom ontvangen mijn klanten e-mails over houderwijzigingen van SIDN na een overname? Een bulkverhuizing (gehele of gedeeltelijke overname) van .nl-domeinen verloopt in principe zonder dat de domeincontacten hierover meldingen ontvangen. "In principe", want er is één uitzondering: in specifieke gevallen moeten wij de contacten van een domein wijzigen naar een nieuwe handle (met dezelfde gegevens). Als dit van toepassing is op het houder-contact, dan gaat er een e-mail van SIDN naar de admin-c. Een bug in het SIDN-systeem is hier de oorzaak van: zoals je misschien weet, heeft SIDN er bij de introductie van de handles voor gekozen om de handle samen te stellen uit een ID-nummer en een registrar-identifier. Stel dat dat voor de overgenomen registrar ANDER is, en voor ons OPENP. Een handle zal er dan uitzien als ABC000030-ANDER of ABC000030-OPENP. Het gedeelte voor het streepje is uniek in het systeem van SIDN: ABC000030 dus. Als een domein verhuisd wordt van registrar 1 naar registrar 2, dan gaat de handle mee over en wordt de registrar identifier aangepast. Een normale verhuizing van een domein met handle ABC012345-ANDER naar ons toe zou dan een nieuwe handle in ons account opleveren ABC012345-OPENP. Het eerste wat wij na zo’n normale verhuizing doen, is een update sturen. ABC012345-OPENP wordt dan vervangen door een nieuwe handle die jullie hebben opgegeven bij Openprovider. So far, so good. Het probleem is echter dat een SIDN-import read-only is. Wij gaan geen handles overschrijven, want de kracht zit hem er juist in dat jullie niets hoeven aan te leveren! Stel: in het verleden is eens een domein in een bulkimport meegekomen waar ABC000030-(iets) in gebruik was. Dit is ABC000030-OPENP geworden, bijvoorbeeld op naam van “ABC Company B.V.” met e-mailadres info@abccompany.nl. Toen kwam jullie import, met daarin óók domeinen met handle ABC000030-(iets), bijvoorbeeld op naam van “Abcoudense Voetbalvereniging”. In plaats van kopiëren, afbreken of waarschuwen, heeft SIDN gewoon besloten dat deze handle al bij ons bestaat en niet wordt gekloond of iets dergelijks. Het domein dat bij jullie op ABC000030-ANDER stond, heeft na het overnemen opeens het bij jullie onbekende bedrijf “ABC Company B.V.” in de whois staan (maar dit kan ook beperkt zijn tot een ander e-mailadres, telefoonnummer of adres). Om deze reden vangen wij dergelijke conflict-handles af, en vervangen we ze door een nieuwe handle met de gegevens zoals die in jullie SIDN-account bekend waren. Die gegevens halen we uit jullie SIDN-rapportage "Handles Extended". Het is niet mogelijk om van tevoren te bepalen of dit op jullie accountovername van toepassing zal zijn. Uit ervaring kunnen we zeggen dat het meestal om 'enkele' domeinen gaat, ergens tussen 0,1% en 0,5%. Dit hangt echter af van het specifieke portfolio. Op verzoek kunnen we achteraf een lijst sturen voor welke domeinen een houderwijziging is uitgevoerd. # What is a "Transfer Robot" and how does it work? This article will explain the basic principle of the *Transfer Robots*. It will cover the following questions: - [What is the *Transfer* *Robot* service?](#bkmrk-what-is-the-transfer-1) - [What details are required to initiate the transfer robot service?](#bkmrk-what-details-are-req) - [For which registrars do you offer a transfer robot service?](#bkmrk-for-which-registrars) - [Will this also skip any transfer messages towards end-customers and the ICANN contact-verification requirement?](#h_01FJVPZXXJAKB85MKFVH5MV4BQ) ## What is the *Transfer Robot* service? Openprovider developed a series of *transfer robots* for a wide range of external registrars. The process is simple: - You provide us with **access to your account** at the other registrar - We **schedule the transfers and process them** in the background As we have access to your account, we are able to retrieve the required details by API to start the transfer. Our system will create an Openprovider customer handle which completely matches the current details. We will retrieve the nameservers, dns zone (if applicable) and transfer-code. We offer 2 options regarding the transfer-dates of the domains; - We can read the expiration date of a domain via your account, so we schedule it shortly before that date to safeguard your cash flow. You will see the scheduled domains at all times in your control panel, which gives you all the freedom to adjust or remove (via RCP or API) the transfers yourself before they start. - Or transfer the entire portfolio on one given date, which will allow you to close the other registrar account sooner and bundle all possible end-customer communications and questions in 1 moment. ## What details are required to initiate the robot transfer service? In general, Openprovider only needs 2 things; 1\. The credentials of the account. 2\. The list of domains that needs to be transferred. **1 -->** Please make sure that the credentials shared have API access enabled. Some registrars are working with IP whitelisting. In those cases our IP addresses which our robot is using needs to be added to the account. Our sales team can inform you further about the IP addresses which need to be added. **2 -->** To avoid any confusion about current statuses or renewal-settings in the account, we will only import the domains for Robot Transfer, which you will submit to us. (preferable csv format) ### Ready? You can start your request via the control panel. Our sales team will reach out to you as soon as possible with more details. ### ![Screen_Shot_2021-12-14_at_20.55.42.png](https://openprovider.help/uploads/images/gallery/2026-08/embedded-image-vqlt0axw.png) ## For which registrars do you offer a Robot Transfer service? As the list of available Robots keeps on growing, please reach out to to get the latest info about that. ## Will this also skip any transfer messages towards end-customers and the ICANN contact-verification requirement? ### Transfer messages The goals of the transfer robot is to schedule and process the domains in an automated way. There are some notifications from the current registrar which we can not prevent. Therefore we ask to read the information below carefully and inform the end-customer before activation the robot. We offer 2 options regarding the transfer confirmations; - Our robot will receive the FOA2 email, confirming the transfer to achieve the domain to be transferred as soon as possible. To do this, the end-customer will get a notification that the email-address is (temporarily) updated. (Default option) - The end-customer receives the FOA2 email. Approval can speed up the transfer, but in most cases, it is not required as a gTLD transfer will continue after 6 days. With this option the end-customer has the option to reject the transfer. **Our advise** is to use the default option where our robot will receive and handles the transfer related emails. This will reduce the risk of rejected transfers. A notification about a changed email-address might be less intimidating than an email about an outgoing transfer. Our advise is to inform the end-customers about the upcoming notifications regarding the temporary email-address adjustment. After the transfer is completed, the original email-address is placed back. ### ICANN contact-verification One of the ICANN requirements is the *contact verification*: each contact used as owner for a **gTLD** registration is checked against our database. If the e-mail address has not yet been verified, we will send an e-mail to that e-mail address in which we require an affirmative response. If we do not receive one, we are forced to suspend the domain registration, until the email is verified. This verification process must be done by every registrar itself. It is not possible to "re-use" verification done by other / previous registrars. As this requirement is part of our contract with ICANN (as ICANN accredited registrar), we cannot skip this process. We do advise to review our white-label options in [this article](https://openprovider.help/books/domains/page/registrant-email-verification-icann-contact-validation) and create a custom template which your end-customers will recognize. # What is a domain transfer and how does it work? ## Question How to initiate a domain transfer to Openprovider? ## Answer You want to transfer your domains to Openprovider? Great! Before starting the transfer, there are some important things to check. 1 - **Not all extensions will work the same** You might have experienced a domains transfer before. That's great, but keep in mind that not all domains might follow the same procedure. It will depend on the domain extension which transfer steps will be taken. Every Registry can set their own transfer policy and however most of them will follow the same general principle, you might notice a difference between them. Some require a transfer code, some not. Some will be real-time and some will take 5 or 7 days. ![Screen_Shot_2021-08-03_at_13.42.14.png](https://openprovider.help/uploads/images/gallery/2026-08/embedded-image-7yld7nxo.png) We always advise to get familiar with the transfer procedure via the detailed extensions page before starting a transfer. 2 - **Check if your domain is active and not locked** For a successful domain transfer, it is important that your domain is active at a current registrar or provider and that the domain is not locked. You can verify this in the whois and check for the "status" field or at your current provider. In case your domain is already expired or locked, please contact your current provider first to resolve that. Once the domain is active, it is ready to be transferred. 3 - **Get the authorisation code** Most domains transfer will require a transfer code which can be supplied by your current provider. There are some exception however, like .uk or .es domains. In case the transfer code field is not present in the control panel, a code is not required to initiate the transfer. 4 - **Request the transfer** A transfer can be started from a few locations, like the control panel, the [API](https://openprovider.help/books/api-plugins/page/14-domains-api-how-to-transfer-a-domain) or various plugins. Please review [this article](https://openprovider.help/books/domains/page/overview-of-all-available-transfer-options) to discover all transfer options that are provided via the control panel. ![Screen_Shot_2021-12-14_at_19.57.40.png](https://openprovider.help/uploads/images/gallery/2026-08/embedded-image-ba5nglgo.png) 5 - **Have patience** You successfully initiated the transfer request and now what? Well, in most cases after you have initiated the transfer, the transfer is; - processed real-time and the domain is direct active in your control panel! (for example for .nl or .be) - initiated but can take 5 till 7 days before the transfer is successfully finished (for example .com, .org) - initiated and a verification email to the registrant or admin contact has been sent (for example .es, .lu) - initiated but additional documentation is required (for example .ie or .hu) As this process can be different per extension, we advise to check the detailed article about that specific extension and follow the instructions there. In case the transfer should have been finished according to the documentation but stays "requested", please contact our [Support Department](https://openprovider.help/books/quick-start/page/contact-openprovider-support). # Why is my transfer not yet processed ? *This article explains different scenarios why the initiated transfer was not completed or processed successfully.* [Incoming transfer](#bkmrk-incoming-transfer-1) [Outgoing transfer](#bkmrk-outgoing-transfer-1) ## Incoming Transfer A questions that we receive a lot. You have requested a transfer for a domain a few days ago and you still see "REQUESTED" in your control panel and you are not sure why and what you need to do. ### gTLDs (generic TLDs .com, .net, .biz, .email, shop etc) If this is a gTLD domain (an extension with more than 2 characters, like .com, .net, .biz, etc) the procedure goes as follows: \- You request the transfer in Openprovider. (You can see a "Pending Transfer" in the whois) \- The domain stays in pending transfer for 5 days. During those 5 days, the owner / admin contact has the option to accept or decline the transfer via the old provider. In most cases, this can be done via an email (Referred to as "FOA2") that the old provider will send (not via Openprovider) **- IMPORTANT: If nobody responds to the email, the domain will be transferred on day 6 (so 6 days after the request is done in Openprovider).** Can Openprovider speed this up? No, as the domain is not in the management of Openprovider, Openprovider has no control over the domain and can not speed it up. The only option to speed it up, is to explicitly approve the transfer via the old provider. They can inform you how you can do this. (Via email or via a control panel etc) Can Openprovider cancel the incoming transfer? No, Openprovider can not cancel the incoming transfer, this can only be done by the registrant or admin contact via the FOA2 email which was sent by the current registrar. ### ccTLD (country code TLDs, like .fr, .es etc) The transfer procedure and transfer time of ccTLD may vary a lot, as every country may decide on their transfer procedures. For example: .fr transfers can take 8 to 22 days, .es transfer will only succeed when an email is verified in time etc In these cases, we advise to check the Knowledge base article of that specific TLD to see what the transfer procedure and transfer time is. You can search on the TLD in the search bar to find the article. ## Outgoing Transfer In case you are transferring a domain from Openprovider to an other registrar and the transfer is not processed, you can check the transfer procedure at the new provider to check if any remaining actions needs to be taken. After an outgoing transfer is started, the registrant will receive a "FOA2" email to confirm or deny the transfer. Approving the email will speed up the transfer process. In case the reseller and you want to speed it up, there may be an option (if supported for that TLD) to approve the outgoing transfer via your control panel. This option is mainly available for gTLDs. ***Domain management > Request queue transfers and trades > Outgoing transfers*** *Be aware, this is only possible for **active** domains. Once a domain is expired, we can no longer request updates for the domain (besides a restore), so forcing the outgoing transfer is no longer supported.* Openprovider can not **DENY** an outgoing transfer. This is only possible via the "FOA2" email which is sent to the owner / admin contact af the domainname. ## ![Screenshot_2021-03-01_at_11.21.23.png](https://openprovider.help/uploads/images/gallery/2026-08/embedded-image-vywqhbru.png)