Overview with affiliate links. We receive a commission if you click through via us. Read how
Compare

Cloud migration for a small business: plan and pitfalls

A practical step-by-step plan for moving files or systems to the cloud, with the pitfalls that small businesses often run into.

Door de redactie van ClouwinoGepubliceerd Laatst bijgewerkt

Short answer

A cloud migration proceeds in steps: take stock of what you have, choose the target and provider, run a trial migration, transfer at a quiet moment and check. Only switch off the old system after you have checked that everything is accessible and can be restored.

Who is it for: Small businesses and freelancers who want to move files, applications or servers to a cloud service.

What are you actually moving?

First, the question of which cloud you mean. Are you moving files and collaboration, such as a file server to an online file service, or are you moving infrastructure, such as an application server to a cloud service? The steps are similar, but the risks differ. With files it is about permissions, folder structure and synchronisation. With infrastructure it is about dependencies, configuration and availability.

Which steps do you follow?

Work in a fixed order and record who is responsible for each step.

  1. Take stock of what you have: data, applications, users, integrations and who is allowed access.
  2. Clear out what you no longer need, so that you move less.
  3. Set the target and criteria, such as costs, data location and exit options.
  4. Test with a small part and measure whether permissions, speed and integrations work.
  5. Plan the actual move in a quiet period and inform users beforehand.
  6. Check afterwards and keep the old system until you have practised a restore.

Which pitfalls often occur?

The most common mistake is taking too little stock. Invisible dependencies, such as an old script that needs a folder or a printer that scans to a network drive, only surface after the move. Also ask users what they use every day.

A second pitfall is shutting down the old system too quickly. Without a fallback, you discover errors when it is too late. A third is an underestimated lead time: uploading large amounts of data depends on your internet connection, and can take days.

What do you arrange for security and privacy?

Turn on MFA for administrators and users, give people access only to what they need and record where data will be stored. If it contains personal data, the GDPR rules apply and a data processing agreement is often needed. Have this checked legally.

What do you check per phase?

A short checklist per phase of the migration.
PhaseWhat you checkRisk if skipped
PreparationOverview of data, users and integrationsUnexpected dependencies
TrialPermissions, speed, working of integrationsProblems only found during the full move
TransferPlanning and communication with usersDisruption to work
CheckCompleteness and restore from backupUnnoticed loss of data
Closing downOld system off only after approvalNo fallback

Who is this less suitable for?

Frequently asked questions

How long does a migration take?

That varies a lot: it depends on the amount of data, your internet connection and the complexity. A trial gives a better estimate than a general figure.

Do I have to stop working during the move?

Sometimes a short interruption is needed, for example during the final synchronisation. Plan it outside office hours and let users know.

What do I do if the trial fails?

Then that is exactly what the trial is for. Adjust the approach or choose another service, without your production having been affected.

Ask us
Compare Get in touch

Are you sure?