Cloud Migration Services in Rwanda — Assessment to Cutover

Why organisations move to EGreed Cloud

• Single-digit millisecond latency inside Rwanda instead of 120–250 ms via offshore regions
• Data residency under Law N° 058/2021 — regulated data stays in Rwandan data centres
• Billing in RWF with MTN MoMo, Airtel Money, bank transfer or card, no forex surprises
• Local engineers you can call, and physical access to your own equipment
• Ageing on-premise hardware retired without a capital replacement cycle

See the EGreed footprint: eight Rwandan data centres with paired availability zones, plus global edge presence for international users.

Phase 1 — Migration assessment

1. Inventory every server, database, application, integration and scheduled job
2. Map dependencies, including the undocumented ones that break cutovers
3. Profile performance, storage growth and peak load to size the target correctly
4. Classify data by sensitivity and residency requirement
5. Score each workload against the 6R framework
6. Produce a costed target architecture, migration wave plan and risk register

The 6R decision framework

Strategy	When it fits	Typical effort
Rehost (lift and shift)	Stable workload, hardware end-of-life, deadline pressure	Low — days per server
Replatform	Managed database or container runtime gives immediate savings	Medium — 1–3 weeks
Refactor	Application is a growth constraint or costs too much to run	High — project scale
Repurchase	A SaaS product replaces the workload entirely	Medium — data migration only
Retain	Regulatory, licensing or latency reason to stay put	None, revisit later
Retire	Nobody has used it in a year	None — decommission and save

Phase 2 — Rehearsal and execution

1. Landing zone built: networking, identity via EGREED ID, backup and monitoring baked in
2. Pilot wave migrated — lowest-risk workloads first, to prove the process
3. Continuous replication established for databases and file systems
4. Full rehearsal cutover in staging, timed end to end and documented
5. Go/no-go review against agreed acceptance criteria
6. Production cutover in the agreed window with a tested rollback plan
7. Hypercare: heightened NOC watch and daily reviews for two weeks

How EGreed keeps downtime near zero

• Database replication runs live until cutover; only the final delta is applied
• DNS TTLs are lowered days in advance so the switch propagates in minutes
• Read traffic is moved first, writes second, with a documented reversal point
• The old environment stays warm for a defined rollback window after cutover
• Cutovers are scheduled for the lowest-traffic window and rehearsed at least once

Phase 3 — Optimisation after landing

• Right-sizing based on 30 days of real usage rather than the old hardware spec
• Reserved capacity applied to steady workloads for lower unit cost
• Autoscaling for the workloads with genuine peaks
• Backup verified against the 3-2-1-1-0 standard with a tested restore
• Security baseline applied: MFA, least privilege, log shipping, patch SLA
• Monthly cost and performance report with concrete optimisation actions

Typical timelines

Environment	Assessment	Migration	Total
5–10 servers, single site	1 week	2–3 weeks	~1 month
25–50 servers, multi-app	2–3 weeks	6–10 weeks	2–3 months
100+ servers, regulated sector	4–6 weeks	4–8 months in waves	6–10 months

Request this service

Use the service request form at the bottom of this page. It routes your request to the owning EGreed team, confirms a first-response time and lists exactly what happens next. You can also email support@egreedtech.org or call +250 795 822 290.

Delivery is backed by 1 Kigali headquarters, 8 Rwandan data centres and 3 branch service centres, with servers in 10 African countries and presence in 70 countries worldwide.

Official EGreed links

• EGreed Technology — egreedtech.org
• All EGreed services
• Request a quote or site survey
• EGreed Cloud
• EGREED ID

See also the services hub, the FAQ hub and the locations and infrastructure map.