Bulk transfer domains

Login to the portal and go to Account > Bulk jobs > Transfer domains

Scroll down and download the CSV example file, the template file will be used to request the transfers with the current registrar through our portal.

Once the download is completed, open the template file. Once opened, you'll notice example.com is pre-filled in the CSV file to serve as an example on how to submit the required data for a transfer. The domainName, registrant, privacyprotect, authcode, autoRenew, ns, admin, billing & tech fields are required for a transfer.


Take note that contacts you provide in the CSV file have to be existent in your Realtime Register account. In case the contacts submitted in the CSV are non-existent in your account, the bulk transfer request will run into an error indicating the relevant contact(s) cannot be found and transfers will not be requested at all.

We'll go over the available fields in the CSV template and what information in what format needs to be submitted where one by one. Keep in mind that not all fields require input.


Required fields

The domainName, registrant, privacyprotect, authcode, autoRenew, ns, admin, billing & tech fields are required for a transfer. You can submit only these fields as our bulk tool provides the option to add/update the data provided in the CSV once the CSV has been uploaded into the bulk tool.

Multiple values

Multiple fields
To use, add a number to the column name and increment for multiple values. For example, you can have columns ns1, ns2 etc.

Field seperator
Use one of the following field separators to indicate multiple values in a field:            | , \n 


Submit the domain to be transferred here in the format domain.tld, in the template CSV-file an example domain is provided; 'example.com'


Submit the registrant contacthandle here. In the template CSV-file an example contacthandle is provided; 'handle-001'


Submit the privacy protect setting here. It's advised to use privacyProtect true for gTLD's, this will skip the step in which the registrant has to confirm her/his contactdetails before the transfer can be requested with the managing registry. Keep in mind not all ccTLD's support privacyProtect, for more information on whether a TLD supports privacy protect or not, check our TLD-metadata


Define the transfer period with which you wish to transfer in a domain. gTLD's default to a transfer period of 12 months if left undefined, ccTLD's will keep their setting as is when requested in a bulk transfer job. For more information of the supported transfer periods per TLD, check our TLD-metadata


Submit the authcode here, for TLD's that do not require an authcode, you can leave the authcode field empty. For more information on which TLD's require an authcode, you can check our TLD-metadata. In the template CSV-file an example authcode is provided; 'au-th88-code-12'


Authcodes are in some cases formatted to start with an '=' or '+' character, Excel defaults this into a formula which deems the field invalid in our bulk tool. To prevent invalid authcode fields during the bulk transfer request, specify the authcode column as plain text.


In case you're transferring a IDN-domain, you can specify the language code here. For more information on the supported language codes per TLD, you can check our TLD-metadata


Submit the autorenew setting you wish to set after completing the transfer here. For autorenew ON, submit true. For autorenew OFF, submit false


Submit the nameservers you wish to set once the transfer is completed. In case you leave the ns field empty, you can select the option to keep existing nameservers in the bulk job overview page once you've uploaded the CSV.


If active for your Realtime Register account, choose whether to skip validation or not


Submit the DNS-template to use in order to use our free to use nameservers once the transfer has been done.


Choose the link or unlinked setting when using a DNS-template for the transfer. Linked means the domain's zone is dynamic with the DNS-template, changes made to the DNS-template will be processed to the domain's zone upon updating the DNS-template. Unlinked means the domain's zone is static, changes made to a DNS-template will not be processed to the domain's zone when a DNS-template is updated. To link the DNS template upon completion of the transfer, submit true. To not link a template on completion of the transfer, submit false


Submit the admin contacthandle here


Submit the billing contacthandle here


Submit the tech contacthandle here


Submit the billable product here if applicable


Submit the billable action here if applicable


Submit the billable quantity here if applicable


Submit the dnssecProtocol here in case you wish to transfer in a domain with DNSSEC.


Submit the dnssecFlag here


Submit the dnssec algorithem here


Submit the dnssecPublicKey here. You can select the option to keep existing Publickey's in the bulk job overview page once you've uploaded the CSV.

Once you've submitted all the values you wish to define, your template file should look similar like the example below;

Name the bulk transfer job, upload the CSV template in the bulk transfer tool and click next

On the bulk transfer overview page, you can map the data that was provided in the CSV before creating the bulk transfer job. Map the transfer data as required and click Create job to create the bulk transfer job


In case you have defined multiple values for fields in your CSV, you need to map the multiple values according to the used method in your CSV, otherwise the bulk transfer tool will not recognize the values. Below you'll find an example on how to map multiple fields (ns1, ns2 etc.) and how to map a field separator ( | , \n )

Using multiple fields

When using multiple fields, you need to map the multiple fields in order for the bulk transfer tool to recognize the multiple fields in the CSV you've uploaded. In the example below, two nameserver fields were provided in the CSV file and mapped to be recognized as ns1 and ns2.

Using a field separator

Select the fields separator used in your CSV. In the example below, a pipe was used to separate the nameser values in the nameserver field of the CSV.

On the job detail page, an overview of all the jobs is available and changes can still be made. In case all the data is mapped correctly, you can run all tasks. In case you wish to run a few separate tasks prior to running all tasks, you can make a selection of tasks you wish to run and run them first instead of running all tasks in one go in your first attempt. An option to delete tasks is available as well

Once the tasks have completed/failed, they will be detailed on the job detail overview. By clicking on the completed/failed tiles, you'll be able to check the detail overview of the tasks that have completed/failed


In case you run into any failed tasks, just click the failed task tile and you can edit any failed transfers on screen and retry them. For example, some registries do not allow transfers < 60 days after the creation date. In case you run into such an error;
Just leave the failed task open and wait for the 60 days to pass. Once the 60 days have passed, you can easily re-try the transfer from the failed tasks overview and complete it.

You've now successfully ran a bulk transfer request in our portal. In case you run into any errors you're not able to resolve yourself, be sure to contact our support department, provide the domain(s) you're having issues with and we'll provide assistance to complete transfers that have failed or remain in a suspended state.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us