Skip to content

Microsoft 365 & Cloud

Cloud Migration

We plan and deliver cloud migration starting from what should not move. We inventory applications, data and dependencies, decide what goes to Microsoft 365 or Azure and what stays on premises, then deliver in phases with each cutover outside working hours and a rollback path.

Who it is for

  • Businesses with an ageing server nearing end of life
  • Companies with teams across locations sharing the same files
  • Organisations wanting predictable cost instead of capital expenditure
  • Sites where remote work became permanent and on-premises is now awkward

When we are NOT the right choice

  • If an application requires on-premises infrastructure and cannot change
  • If internet connectivity is inadequate and no upgrade is planned
  • If moving everything is requested without a cost analysis

PROCESS

The process

Indicative times from signature of the proposal, subject to hardware availability. Every project is shaped to the size and the needs of the client.

  1. 01Application and data inventory

    We record what runs today, who uses it and what it talks to. Dependencies are what derails migration plans.Time: 2-5 working daysDeliverable: Application register with dependencies

  2. 02Deciding what goes where

    We define what moves to Microsoft 365 or Azure, what stays on premises and why. Migration is not an end in itself.Time: Alongside the studyDeliverable: Plan with a justification per system

  3. 03Running cost estimate

    We present the running cost after migration, so the decision is made against numbers rather than assumption.Time: With the quotationDeliverable: Current versus future running cost

  4. 04Phased delivery

    We migrate group by group and system by system, each cutover outside working hours and verified before the next begins.Time: 1-3 weeks for up to 50 usersDeliverable: Migration per group with verification

  5. 05Handover and decommissioning

    We hand over documentation and a decommissioning plan. The old server is not wiped until nothing is shown to need it.Time: On completionDeliverable: Documentation and decommissioning plan

What is includedWhat is not included
Inventory of applications, data and dependenciesCloud licence and subscription costs
Migration plan with justification per systemDevelopment or modification of third party applications
Running cost estimate after migrationInternet circuit upgrades
Data migration and permission configurationERP support from its vendor
Out of hours cutover with a rollback plan
Documentation and decommissioning plan

Technology and equipment

  • Microsoft 365
  • Microsoft Azure
  • SharePoint
  • OneDrive
  • Exchange Online
  • Veeam
  • Synology

From practice

The question usually arrives as "what does moving to the cloud cost". The useful answer starts from the other end: which systems should not move, because they have local dependencies, because their file volume makes them more expensive there, or because they simply work and relocating them adds nothing.

The underrated part is the dependency register. There is almost always one application nobody remembered was reading files from the old server, and it surfaces on the first Monday after cutover.

Prerequisites

  • Access to existing systems for the inventory
  • Adequate internet connectivity, or a planned upgrade
  • A decision on systems that remain on premises
  • Out of hours work windows per phase

Cost

Quoted by phase, with the study, data migration and cutover itemised separately. We always present the estimated monthly running cost after migration as well, because that is where the decision is actually settled.

We do not publish a price list. Every proposal follows a site survey and separates hardware from labour.

What moves the cost

  • Number of users and data volume
  • Number of systems and dependency complexity
  • Whether hybrid operation is needed for a long period
  • Whether old and new environments must run in parallel

Frequently asked questions

Does everything have to move to the cloud?

No, and assuming otherwise is the most common mistake. Applications with local dependencies or very large file volumes often cost more in the cloud. The plan states explicitly what stays on premises and why.

Will work stop during migration?

Migration runs in phases, group by group, with each cutover outside working hours. For up to 50 users, a typical Microsoft 365 migration completes in 1 to 3 weeks.

Will cost go down?

It usually changes shape more than it drops: from capital expenditure to a predictable monthly figure. We present the estimate before migration so there are no surprises afterwards.

What about backups after migration?

They are needed separately and are one of the most common gaps. A cloud provider guarantees service availability, not recovery of your data after deletion or encryption.

NEXT STEP

Plan your migration against numbers

We inventory applications and dependencies and deliver a plan covering what goes where, with delivery cost and running cost.

GET IN TOUCH

Tell us what you need

Four fields. An engineer replies, not a sales desk.

Fields marked * are required.

By sending this form you accept the processing of your details under our Privacy Policy.