Migrate everything,
do a little

First, we determine what we're going to migrate. This could be mailboxes, websites, applications, DNS zones, domains, entire servers, and more.

After this step, we have a list with all resources, and where to find them (e.g. on which server). This list will be used during the migration.

In many cases, the previous step identifies unused resources. For example, for customers that cancelled.

To save on the time needed to migrate, delete these beforehand.

In some cases, domains don't use nameservers that you can access. in this case, whoever manages DNS must point DNS records to Cyberfusion.

To be able to inform these people in a later step, we make a list of which domains use external DNS.

To migrate resources, we need to access them. For hosting/servers, think of (S)FTP and control panels (such as cPanel, Plesk or DirectAdmin). For domains, think of registrar panels.

The type of access determines how fast the migration goes. Root SSH access is most efficient, but not always available.

Not sure what kind of access you have? Cyberfusion can help you ask the right questions to the current provider.

Based on the amount of resources to migrate, and the type of access, we make a quote.

To give you an idea:

- Migrating 3 DirectAdmin servers with 330 users costs € 2.880 on average (with root SSH access, outside office hours).
- Migrating a single Plesk server with 40 websites costs € 960 on average (with root SSH access, within office hours).

The migration dates and times are planned in consultation. During the migrations, you are available for questions or problems.

Depending on the amount of websites/applications to migrate, we recommend migrating a number of them every week, for a period of several weeks. In the unlikely event that problems arise, the impact will be limited to a smaller number of websites/applications.

To keep stakeholders up to date, we recommend setting up an online page - as email might not work reliably during the migration.

Send an email to stakeholders, informing them about:

- When their resources will be migrated.
- What they should do.
- The URL to your online page for updates (from the previous step).

In these cases, you should inform stakeholders additionally:

- If the stakeholder has mailboxes, users must change mail server settings in their mail clients (such as Thunderbird and Outlook). Stakeholders should be informed of this before the migration, as they won't receive emails between the migration and changing their settings. The new mail server settings (host, username and password) can be found on the platform.
- If the stakeholder has domains with external DNS (inventarised in the previous step "Determine which domains have external DNS").

For every environment to migrate, we create a new, empty environment on the Cyberfusion platform.

Before migrating, we create a backup. If anything goes wrong during the migration, we can restore the original situation from this backup.

The backup can be made on the original server, or on cloud storage that you supply (such as SFTP or S3).

Your dedicated migration team migrates the agreed resources on the agreed dates and times.

You are kept up to date via the platform.

Update your online page (from the previous step "Set up online page").

When the migration is complete, we recommend turning off the old environment(s), but not canceling them yet.

If something is still running on the old environment, the 'forgotten' data can easily be retrieved from the old environment.

After several weeks, cancel the old environments.

At this point, it is extremely unlikely that anything is still running on the old environment, and you will save double costs.

The backup that was made before the migration started (step "Create backup") is deleted.