All your hosting migrated,
fully taken care of
Shift has one goal: migrate all your hosting without issues - while taking as much work off your hands as possible.
With Shift, you get a dedicated team with fixed people and years of migration experience. Your team knows your migration process inside out - guaranteeing a smooth migration.
First, we make a migration plan together - so everyone knows exactly what to do and when.
You can reach your dedicated team 24/7. Their help is always excellent - they are fully aware of your migration.
'Rresources' are objects to migrate. Including websites, web applications, DNS zones, domains, hosting plans, servers, and more.
'Stakeholders' are people on whose behalf you host websites or applications. For example, your customers.
Example migration plan
Determine resources to migrate
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.
Delete unused resources
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.
Determine which domains have external DNS
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.
Determine available access
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.
Agree on quote
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).
Set migration date(s) and time(s)
We set the date(s) and time(s) to migrate on. This can be at any time you prefer, within or outside office hours.
During these moments, you should be available for questions or problems. For example, if we have questions during the migration. Or, if you host websites or applications on behalf of customers, if your customers need help.
Depending on the amount of resources to migrate, we might split up the migration. For example, if you have 100 resources to migrate, we might migrate 20 resources every week, for a period of 5 weeks. If problems arise, the impact will be limited to a smaller number of resources.
Set up online page
To keep stakeholders up to date, we recommend setting up an online page - as email might not work reliably during the migration.
Inform stakeholders about 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").
Create new resources at Cyberfusion
For every environment to migrate, we create a new, empty environment on the Cyberfusion platform.
Create backup
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).
Migrate resources to Cyberfusion
Your dedicated migration team migrates the agreed resources on the agreed dates and times.
You are kept up to date via the platform.
Inform stakeholders that migration ended
Update your online page (from the previous step "Set up online page").
Shutdown old resources
Once the migration is complete, turn off the old resources. Don't cancel them yet.
In the unlikely case that something is still running on the old environment, which was missed while making the migration plan, you quickly discover that it no longer works. That part will then be migrated after the fact.
Cancel old environment(s)
After several weeks, cancel old resources.
At this point, it is extremely unlikely that anything is still running on the old environment, and you save double costs.
Delete backup
The backup that was made before the migration started (step "Create backup") is deleted.