Dynamic Cloud Server: Migrate Server Data to a Cloud Server

The Dynamic Cloud Server no longer meets the current technical requirements of IONOS and has reached the end of its life cycle. Therefore, this product will be discontinued.

To ensure the security and stability of your data, a manual migration of your server data and email accounts and a manual transfer of your domain(s) is necessary. This article explains what you need to be aware of when moving your server data and what steps are required for a server migration. 

To ensure the complete transfer of your server data is successful, we recommend that you thoroughly plan the server migration and clarify important general conditions in advance.

The recommended procedure is briefly described below. Then, the necessary steps are further explained.

  • Prepare the migration.

  • Create the Cloud Server.

  • Optional: Create a local backup of the data to be migrated. You can use this backup to migrate your server data to your Cloud Server.

  • Install the required applications and configure the necessary services, firewall settings, roles and rights on the server. If necessary, make any additional individual settings changes that may be required.

  • Copy the data to be migrated to your Cloud Server. If you are using Plesk, you can use the Plesk Migration & Transfer Manager to migrate your hosting data to your Cloud Server.

  • Configure the applications you have migrated to the Cloud Server. Make sure that the required SSL certificates are included. You may have to include them manually.

  • Test all projects and services with a subdomain or another top-level domain whose country code is not frequently used (e.g. info). In addition, make sure that your applications and scripts are working correctly.

  • Connect your domain, which is still in your Dynamic Cloud Server contract, to the static IP address of your Cloud Server. For this purpose you have to configure the A record in the DNS settings of your domain. This is also necessary if your domain is associated with another customer number, another contract or hosted with another provider.

  • Transfer your domain(s) to your Cloud Server contract.

Additional Information

This is only necessary if your domain(s) are in your Dynamic Cloud Server contract.

Please Note

When you move the emails and folders of an email mailbox to IONOS as part of a domain transfer from another provider, you must set up a destination mailbox for each source mailbox in IONOS before moving the domain.

  • Perform an email migration for your Mail Basic, Mail Business or Microsoft Exchange mailboxes.

  • Check the DNS settings of your domain in your Cloud Server contract.

  • Shut down the Dynamic Cloud Server.

Preparing Migration

To reduce the effort and minimise the required resources, we recommend that you clean up the currently used server in advance. To do this, remove unnecessary or outdated pages, backups, email accounts and files that you no longer need. In this way, you reduce the amount of data transferred to the new server, which can significantly shorten the effort and duration of the migration.

Then, create a list of the domains, websites, databases, applications, and files that need to be migrated. In addition, note all domains and email accounts you want to move as part of the server migration.

Also determine what resources are needed. This includes the number of CPUs and cores, the required RAM, the hard disk space and the number of required IP addresses. Please also note the license costs, which are calculated according to the number of cores or CPUs used for your operating system or applications.

Check your individual configuration and make a note of all settings that need to be configured on your Cloud Server. This includes, for example, the roles and rights created, firewall policies and rules, and reverse mappings that you have configured in IONOS or in your server's operating system.

Please Note

After creating the Cloud Server, you need to configure these settings manually either in the Cloud Panel or in the operating system of your new server.

If your Dynamic Cloud Server is connected to external databases, external cache servers or proxy servers, you should also note the required settings, as these may also have to be manually configured in your Cloud Server. 

Check if your existing applications can be migrated. Make sure they are compatible with the operating system you are installing on the Cloud Server.

For an overview of the Plesk versions that allow migration of hosting data using the Plesk Migration & Transfer Manager, please see the following article:

Migration Guide

Please Note

When you order a Cloud Server, it will be assigned a new IP address. The IP address assigned to your Dynamic Cloud Server cannot be assigned to another server.

Create a Cloud Server

Create a Cloud Server. You can order it on the following page:

https://www.ionos.co.uk/cloud/cloud-servers

Create a Backup of the Data to Be Migrated

Create a backup of the data to be migrated. You can use this backup to migrate your server data to your Cloud Server.

How to save a backup of your server data on your local computer is explained in the following articles:
 

Local Computers with the Microsoft Windows 10 Operating System

Transfer Files Using Remote Desktop


Local Computers with the Linux Operating System

Store Backups on a Local Computer (Server with Linux)

Creating a Backup with Tar: How the Archiving Works

Install Applications on the Cloud Server and Configure the Server

Install the required applications on the Cloud Server and configure the required services, firewall settings, roles and rights. If necessary, perform any other required settings.

If you are using the operating system Linux, check in the bash history of your Dynamic Cloud Server for all packages you have installed. Then log on to the Cloud Server and search for the updated versions or equivalents of these packages using the package manager.

Copy Backups to the Cloud Server

Copy the data to be migrated to your Cloud Server.

Copy Data from a Local Computer Running the Linux Operating System to a Cloud Server Running the Linux Operating System

Use the following command to copy a directory located on your local computer to your Cloud Server:

scp -r /LOCAL/DIRECTORY remote_username@SERVERIP:/DIRECTORY_ON_THE_SERVER
Example:

[root@localhost ~]# scp -r /home/backup root@217.160.44.208:/home
To copy a single file, enter the following command:

[root@localhost ~]# scp -r /DIRECTORY/FILENAME remote_username@SERVERIP:/DIRECTORY_ON_THE_Server
Example:

[root@localhost ~]# scp -r /home/test.txt remote_username@217.160.44:/home

Note

If scp is not found, you can install the program with the following command:

CentOS

[root@localhost ~]# yum install openssh-clients
Debian/Ubuntu

[root@localhost ~]# apt -y install openssh-server

If you have backed up your data with tar, you can copy the files to your Cloud Server with an FTP program. Then, you can unpack the archives.

For more information about tar, see the following article:

Creating a Backup with Tar: How the Archiving Works


Copy Data from a Local Computer Running the Microsoft Windows Operating System to a Cloud Server Running the Linux Operating System

If you use a local computer with a Microsoft Windows operating system, you can transfer the files easily and conveniently using the WinSCP program. WinSCP is a graphical open-source SFTP and FTP client for Windows.

You can download WinSCP from the following URL:

https://winscp.net/eng/download.php


Copy Data from a Local Computer Running the Microsoft Windows Operating System to a Cloud Server Running Windows Server 2012, Windows Server 2016 or Windows Server 2019

For instructions on how to use Remote Desktop to copy files between your local Windows 10-based computer and your Cloud Server, see the following article:

Transfer Files Using Remote Desktop

Migrate Hosting Data to Your Cloud Server with the Plesk Migration & Transfer Manager

If you have Plesk installed on your Dynamic Cloud Server, you can use the Plesk Migration & Transfer Manager to migrate your hosting data from one server to another server. For example, service packages, accounts or subscriptions with content is considered as hosting data.

The following data is not migrated by Plesk Migration & Transfer Manager:

  • the list of connected database servers and their settings

  • the settings of the Apache modules

  • backup settings

  • backup files and FTP storage settings

  • Plesk extensions

  • third-party software and services, such as Google services

Notes
  • Administrators and customers have to manually configure these settings and add missing objects.

  • Transfer between Plesk for Linux and Plesk for Windows is not supported.

  • For instructions on how to back up and restore Plesk system databases, please see the following article:

    How to Back Up/Restore Plesk System Databases

    For more information on importing and exporting databases, see the following article:

    Backing Up and Restoring Databases

For an overview of the Plesk versions that allow migration of hosting data using the Plesk Migration & Transfer Manager, please see the following article:

Migration Guide

You can find instructions on how to migrate a Dynamic Cloud Server to a Cloud Server using the Plesk Migration and Transfer Manager in the article

Migrating a Server with Plesk to Cloud Server (Linux)

Configure Applications on the Cloud Server

After transferring your domain and configuring the DNS settings, you can configure your applications. Make sure that the required SSL certificates are included. You may have to include them manually.

Please Note

If you have purchased an SSL Certificate for your domain through your Dynamic Cloud Server contract, you cannot renew it. Therefore, make sure that a new certificate is set up and included before the expiry date.

If your server requires custom connections to external databases, external cache servers, or proxy servers, you must manually configure these settings in your Cloud Server.

Note

If you have used the Plesk Migration & Transfer Manager to migrate your hosting data to a Cloud Server, please refer to the notes in the following articles:

What Data Are Transferred

Known Issues and Limitations

Test Your Applications, Projects and Services

Test all projects and services with a subdomain or another top-level domain whose country code is not frequently used (e.g. info). In addition, make sure that your applications and scripts are working correctly.

Configure the DNS Settings of Your Domain(s)

Connect your domain, which is still in your Dynamic Cloud Server contract, to the static IP address of your Cloud Server. For this purpose you have to configure the A record in the DNS settings of your domain. This is also necessary if your domain is associated with another customer number, another contract or hosted with another provider.

Make further DNS settings changes if necessary.

For more information on configuring the DNS settings, click here:

Changing a Domain's IPv4/IPv6 Address (A/AAAA Record)

Edit DNS Settings

Transfer Your Domain(s) into Your Cloud Server Contract

If your domain is part of a Dynamic Cloud Server contract, you will need to move it to your Cloud Server contract. 

The domain transfer will affect settings and connected products:

  • Your domain's destination is reset.

  • Connections to email clients are broken until the email addresses are recreated in the destination contract.


You can transfer your domain to another contract with the same customer number in a few minutes. This has the following benefits:

  • There are no long wait times, which often occur when transferring domains to another provider.

  • The private registration and domain transfer lock settings are automatically carried over. You do not have to make any adjustments during the domain transfer.

Please Note

When you move the emails and folders of an email mailbox to IONOS with the IONOS Email Migration Service powered by audriga as part of a domain transfer from another provider, you must set up a destination mailbox for each source mailbox in IONOS before moving the domain.

For more information about moving email and folders, see the following article:

Domain Transfer to IONOS: Moving Emails and Folders to an IONOS Email Account


Further information on transferring domains can be found here:

Transfer Domain to another IONOS Contract (same customer number)

Transfer of Domain to another IONOS Contract (different customer number)

Mail Basic, Mail Business or Microsoft Exchange: Performing an Email Migration

When you transfer a domain to IONOS or transfer your domain to another IONOS contract or customer number, only the domain itself is transferred during the domain transfer. Associated email addresses are not moved.

If you have set up Mail Basic, Mail Business or Microsoft Exchange mailboxes in your contract, you can use the IONOS Email Migration powered by audriga to move the emails and folders of these mailboxes.

Depending on the respective product, you can migrate additional data such as contacts or calendar entries as part of the email migration.

Within the scope of the migration, only data that is stored on the server of the source provider is transferred. You can see that data in the Webmailer for example. We do not have access to data that is stored exclusively in an email program that is located on your device.

Further information about the IONOS Email Migration powered by audriga can be found here:

Using the IONOS Email Migration Service

Domain Transfer to IONOS: Migrate Emails and Folders to an IONOS Email Account

Check the DNS Settings of the Domain in the Cloud Server Contract

Check the DNS settings of your domain in your Cloud Server contract.

Shut down the Dynamic Cloud Server

Before you shut down the Dynamic Cloud Server, you should perform some tests to ensure that the websites and applications on your Cloud Server are working correctly.

Test the websites you migrated with different browsers. You should also open the websites on different devices to detect possible display problems.

Furthermore, check whether the DNS settings have been applied. For information about the time that is required until the changes to DNS settings for IONOS take effect, see the following article:

Time Required for DNS Changes

In addition, make sure that the installed applications are configured correctly and working.

If the migration of your sites fails, check them and repeat afterwards the migration of these files.

Additional Information

Further information about the Cloud Server can be found here:

Cloud Server: First Steps

Assistance to help you set up and manage your Cloud Server