Cloud Migration in Rwanda

What is cloud migration, and who needs it

It’s a planned project to move specific workloads, such as a file server, a line-of-business application, a database or a website, from local hardware to cloud services, usually Microsoft Azure or Microsoft 365. It suits organisations facing a server replacement, a lease or support renewal, rapid growth, a move to multiple sites, or recurring problems with power and cooling in the server room.

The problem it solves

A migration treated as a simple copy usually fails at the cutover. Applications depend on fixed network paths, file permissions don’t translate, data changes during the copy, and a slow internet link turns a fast local system into a frustrating remote one. Planning each workload, testing it in the cloud before switching and keeping a rollback path turns migration from a risky weekend into a controlled change.

Choosing how each workload moves

Rehost (lift and shift). The server is moved largely as it is to a cloud virtual machine. Fast, but carries existing problems along, and costs can be higher than expected.

Replatform. The workload moves to a managed cloud service, such as file shares to SharePoint or a database to a managed database service, removing server maintenance.

Replace. An old application is retired in favour of a cloud product that does the same job.

Retain. The workload stays on site, because it works better there or isn’t worth moving yet.

Each choice is made per workload, weighing cost, effort, risk and how well it will perform over your internet connection.

Data location and cost

The nearest Azure regions to Rwanda are in South Africa, so moving personal data to Azure stores it outside the country. Rwanda’s Law N° 058/2021 requires storage in Rwanda unless the National Cyber Security Authority’s registration certificate permits otherwise, so this belongs in the migration plan, with your legal adviser. Cost changes too: one-off server purchases become a monthly bill, so we estimate running costs per workload before you commit, and plan ongoing cost management after go-live.

What the work involves

1. Inventory servers, applications, data volumes, dependencies and who uses what.
2. Assess each workload: move method, estimated monthly cost, connectivity needs and data location.
3. Prepare the cloud environment: subscriptions, network, identity, security and backup.
4. Migrate and test each workload, with users checking it before cutover.
5. Cut over in agreed windows, with the old system kept for rollback.
6. Decommission the old system after sign-off, and wipe its data.

What’s included and what’s not

Typical timelines and what drives cost

A single server or file share typically takes one to three weeks including planning, testing and cutover. Larger estates are moved in waves over several months. Cost is driven by the number of workloads, data volume over your available bandwidth, application complexity and vendor support, and how much testing users need.

Equipment typically used

Azure Migrate for assessment and server moves, the SharePoint Migration Tool for file shares, database migration tools where needed, Azure Backup, and a VPN or dedicated connection between your office and Azure for hybrid setups. Reliable internet with failover at each site.

Common mistakes we see

Moving servers as they are and finding the cloud bill higher than the old hardware. No test of application speed over the real internet connection. Hidden dependencies, such as a scanner or accounting add-in, discovered on cutover day. Old servers switched off before users confirmed everything works. No backup configured in the cloud. And data location never considered.