Cloud Migration in Sri Lanka: Strategy, Cost & AWS/Azure/GCP Guide
At a Glance - Cloud Migration Sri Lanka (2026)
- Assessment + strategy: LKR 400K–800K · 2–4 weeks · workload inventory, 6-R assignment, TCO model
- Lift-and-shift (rehost): LKR 800K–2.5M · 6–12 weeks · VMs to AWS/Azure/GCP Singapore region
- Replatform + managed services: LKR 1.5M–4M · 10–16 weeks · RDS, S3, CDN, fewer servers to patch
- Nearest region: AWS ap-southeast-1 (Singapore) · Azure Southeast Asia · GCP asia-southeast1 (~25–40ms from Colombo)
- Data residency: PDPA cross-border rules pending commencement - plan encryption + DPA with provider now
- Downtime target: Pilot apps 2–4 hr window · critical apps blue-green with <15 min cutover
Introduction
Cloud migration Sri Lanka is moving workloads from on-premises servers, local data centres, or ageing shared hosting to AWS, Azure, or Google Cloud - with a deliberate cloud migration strategy per application, not a one-size-fits-all lift.
This guide covers workload assessment, the six standard migration strategies, AWS vs Azure vs GCP for Sri Lankan buyers, an honest cost model in LKR, security and data-residency considerations, downtime planning, a 12-week roadmap, and a before-and-after case from a Hashtag Coders project. Whether you need AWS migration services Sri Lanka or Azure migration Sri Lanka, the decision framework is the same - assess first, migrate in waves, optimize after cutover.
Why Migrate - Without Overselling Savings
Cloud is not automatically cheaper. It shifts capital expenditure (servers every 3–5 years) to operational expenditure (monthly bills). You gain elasticity, managed backups, faster provisioning, and access to global regions - but bills spike if you over-provision or leave dev environments running 24/7.
- Scale on demand: Handle campaign traffic or seasonal peaks without buying hardware for peak-only load
- Resilience: Multi-AZ databases, automated snapshots, cross-region backup - if configured deliberately
- Speed: New environments in hours; no procurement lead times
- Managed services: Offload patching, backups, and scaling for databases and object storage
- Remote work: Staff access systems without VPN into a Colombo server room
Run your own TCO model before committing. Savings depend on how efficiently you were running on-premises and how well you right-size cloud resources post-migration. See also our cloud cost optimization guide for post-migration tuning.
Workload Assessment Template
Complete this inventory before choosing a provider or strategy. One row per application or workload - not per server.
| Field | What to capture | Why it matters |
|---|---|---|
| Application name | ERP, website, booking engine, file server | Migration unit - not individual VMs |
| Business owner | Department head, sign-off authority | Change management and UAT |
| Criticality | Tier 1 (revenue) / 2 / 3 | Downtime tolerance, wave order |
| Users & peak load | Daily active users, concurrent peak | Sizing and load-test targets |
| Data sensitivity | PII, payments, health, public | Encryption, region, access controls |
| Dependencies | Upstream/downstream systems, APIs | Migration order, integration risk |
| Current stack | OS, DB, language, hosting location | Rehost vs replatform vs refactor |
| Data volume | DB size, file storage, growth rate | Transfer time, Snowball vs online sync |
| RTO / RPO | Max downtime · max data loss | Backup architecture, cutover method |
| Migration strategy (6 R) | Rehost / Replatform / etc. | Effort, timeline, risk |
| Wave & target date | Pilot / Wave 1 / 2 / 3 | Programme scheduling |
Tip: During discovery, expect 10–20% of applications to be unused (candidates for Retire). That alone reduces migration scope and cost.
Six Cloud Migration Strategies (The 6 Rs)
Assign one strategy per workload. Most portfolios mix approaches - do not default everything to lift-and-shift.
| Strategy | What it means | Best for | Typical timeline | Risk |
|---|---|---|---|---|
| 1. Rehost Lift and shift |
Move VMs to EC2 / Azure VM with minimal changes | Legacy apps, tight deadlines, unknown dependencies | 4–12 weeks | Low |
| 2. Replatform Lift, tinker, shift |
Swap components for managed services - RDS, S3, Azure SQL, Cloud CDN | Apps where DB admin is the main pain; websites with static assets | 8–16 weeks | Medium |
| 3. Repurchase Drop and shop |
Replace custom/on-prem app with SaaS - M365, Salesforce, Xero | Email, CRM, accounting, HR - non-differentiating functions | 4–12 weeks | Medium |
| 4. Refactor Re-architect |
Rebuild cloud-native - containers, serverless, microservices | Strategic apps needing scale, performance, or rapid feature delivery | 3–12 months | High |
| 5. Retire | Decommission unused or duplicate systems | Zero logins in 90 days, superseded tools, shadow IT | 1–2 weeks | Low |
| 6. Retain Revisit later |
Keep on-premises for now - hybrid posture | Latency-sensitive PLCs, recent hardware buy, regulatory hold, EOL in <12 months | N/A | Low |
Typical portfolio mix: majority Rehost/Replatform for quick wins, selective Refactor for revenue-critical apps, Retire the dead weight, Retain only with documented rationale reviewed annually.
AWS vs Azure vs GCP - Sri Lanka Buyer Guide
All three operate Singapore-region data centres - the practical choice for low latency to Sri Lankan users. Use provider calculators with your actual workload; figures below are illustrative for a small e-commerce or business app (~5,000 daily users).
| Provider | Choose when | Singapore region | Illustrative monthly (LKR)* |
|---|---|---|---|
| AWS | Broadest service catalog, startups, e-commerce, AWS migration services Sri Lanka talent pool | ap-southeast-1 | ~75K–85K (2× t3.medium, RDS, S3, CDN) |
| Azure | Windows/SQL/.NET shop, hybrid AD, enterprise support - Azure migration Sri Lanka | Southeast Asia | ~72K–80K (comparable VM + managed MySQL) |
| GCP | Data analytics, BigQuery, Kubernetes-native, ML workloads | asia-southeast1 | ~65K–75K (often competitive on compute) |
*At ~LKR 320/USD. Verify with AWS Pricing Calculator, Azure Pricing Calculator, or GCP Pricing Calculator before budgeting.
Cost Model - On-Premises vs Cloud (LKR)
Compare 3-year TCO, not month-one cloud bill vs sunk hardware. Include migration project cost in year one.
| Cost line | On-premises (50-person SME) | Cloud (replatformed) |
|---|---|---|
| Year 1 capital | LKR 4M–7M (servers, SAN, UPS, licences) | LKR 0 capex |
| Annual opex | LKR 2.5M–4M (staff, power, internet, maintenance) | LKR 1.8M–3.2M (compute + DB + storage + transfer) |
| IT headcount | Often 2 sysadmins | Often 1 cloud engineer (different skill set) |
| Year 1 migration | - | LKR 800K–2.5M (assessment + execution) |
| Hardware refresh | Every 4–5 years (~LKR 3M+) | None - provider handles hardware |
| 3-year TCO band | LKR 14M–22M | LKR 10M–18M (if right-sized) |
When cloud costs more:
- Lift-and-shift without right-sizing - peak-capacity VMs running 24/7
- Dev/test environments left on overnight and weekends
- High cross-region data transfer or egress to on-prem
- Recently purchased on-prem hardware still within depreciation
Migration project costs (Sri Lanka)
- Assessment & roadmap: LKR 400K–800K
- Pilot (2–3 apps): LKR 600K–1.2M
- Production waves (10–30 apps): LKR 1.5M–5M
- Managed cloud ops: LKR 150K–500K/month
Security, Compliance & Data Residency
Cloud uses a shared responsibility model - the provider secures the data centre; you secure identities, network rules, encryption, and application code.
| Topic | Practical action |
|---|---|
| PDPA Sri Lanka | Substantive processing rules await Gazette commencement - but encrypt PII, document processors, and plan cross-border transfers. See PDPA compliance guide. |
| Data residency | No Sri Lanka AWS/Azure/GCP region today - Singapore is standard. EU customer data → EU region. Document legal basis for offshore storage. |
| IAM & MFA | Unique accounts, MFA on all admins, least-privilege roles, no shared root keys |
| Encryption | TLS 1.2+ in transit · AES-256 at rest on RDS/S3/Blob · KMS or Key Vault for keys |
| Network | Private subnets for databases · security groups deny-by-default · WAF on public endpoints |
| Logging | CloudTrail / Activity Log enabled · 90-day minimum retention · alerts on root login and large exports |
| Backups | Automated DB snapshots · cross-region copy · quarterly restore drill |
Downtime Planning
Define RTO/RPO per workload before scheduling cutover. Match technique to tolerance.
| Tier | RTO target | Cutover method | Rollback trigger |
|---|---|---|---|
| Tier 3 - dev / internal tools | 4–8 hours | Stop-start migration weekend | Any critical functional failure |
| Tier 2 - business apps | 1–2 hours | DB replication + DNS cutover · maintenance window announced 2 weeks ahead | Error rate >5% or p95 latency 2× baseline for 15 min |
| Tier 1 - revenue / customer-facing | <15 minutes | Blue-green · parallel run 1–2 weeks · phased traffic 10% → 50% → 100% | Automated health check fail · instant DNS revert to blue |
Pre-cutover checklist: full backup verified · rollback runbook tested · load test at 150% expected peak · stakeholders notified · help desk staffed · on-prem environment kept warm 30 days post-cutover.
12-Week Migration Roadmap
| Phase | Weeks | Deliverables |
|---|---|---|
| Discover | 1–3 | Workload inventory, 6-R matrix, provider choice, landing zone (VPC, IAM, billing alerts) |
| Pilot | 4–6 | Migrate 2–3 low-risk apps · validate runbooks · cost baseline |
| Wave 1 | 7–9 | Production apps (tier 2) · weekend cutovers · user comms |
| Wave 2 | 10–11 | Tier 1 apps · blue-green · extended parallel run |
| Optimize | 12+ | Right-size instances · reserved capacity · retire on-prem · DR drill |
Case Study: Ravanaa News - Before & After Cloud Hosting
Client: Ravanaa News (news
portal) · Built by: Hashtag Coders
Challenge: Slow page loads and hosting that could not keep up with traffic spikes
- hurting reader experience and search visibility.
| Metric | Before | After (cloud-hosted Next.js) |
|---|---|---|
| Architecture | Legacy/slow hosting, monolithic delivery | Next.js + custom CMS on edge/CDN cloud platform |
| LCP (mobile) | 4.8s | 1.6s |
| Lighthouse performance | 52 | 91 |
| Traffic handling | Struggled under daily news spikes | CDN + auto-scaling handles high daily traffic |
| Business outcome | Limited organic reach | ~4× organic traffic growth (client testimonial) |
Migration approach: Refactor + replatform - not a VM lift-and-shift. The team rebuilt on a cloud-native stack with global CDN, then cut over DNS during a planned maintenance window. Same pattern applies to e-commerce and booking platforms moving off shared hosting.
Common Mistakes to Avoid
- Lift-and-shift without sizing review - replicate peak-capacity VMs 24/7; first bill shocks finance
- Skipping load tests - pilot with 10 users, production gets 1,000; connection pools exhaust
- Ignoring latency - chatty apps with 50 DB round-trips feel slow in cloud vs LAN
- Security as phase 2 - public S3 buckets and open security groups at go-live
- No rollback plan - cutover without tested revert path
- Underestimating data migration - encoding issues, orphaned records, validation gaps
- Forgetting backups in cloud - provider offers tools; you must configure and test restores
Conclusion
Cloud migration Sri Lanka succeeds when you assess workloads honestly, assign the right 6-R strategy per app, pick AWS/Azure/GCP for fit not hype, plan downtime and rollback, and optimize after cutover - not before.
Hashtag Coders delivers assessment, migration execution, and managed cloud ops through cloud solutions and web development. Request a migration assessment.
Frequently Asked Questions
How long does cloud migration take in Sri Lanka?
Pilot (2–3 apps): 4–6 weeks. SME portfolio (10–20 apps): 3–6 months. Enterprise with compliance and hybrid requirements: 6–18 months. Timelines depend more on data quality and dependencies than cloud provider choice.
AWS or Azure for a Sri Lankan business?
AWS if you need the widest service catalog and local partner ecosystem. Azure if you run Windows Server, SQL Server, Active Directory, or .NET. GCP if analytics, BigQuery, or GKE are central. Many SMEs start with one provider in Singapore region.
Where is my data stored if I use AWS from Sri Lanka?
Typically ap-southeast-1 (Singapore) unless you choose another region. There is no AWS region in Sri Lanka today. Document this in privacy policies and vendor DPAs - especially ahead of PDPA substantive commencement.
Will cloud migration reduce costs?
Sometimes - especially if you were over-provisioning on-prem hardware or facing a refresh cycle. Sometimes not - if you replicate peak capacity in cloud 24/7. Model your specific workloads; treat optimization as an ongoing discipline after migration.
Can we migrate with near-zero downtime?
Tier 1 apps: yes, with blue-green deployment, database replication, and phased DNS cutover - budget extra time and cost. Tier 2/3 apps: planned maintenance windows of 1–4 hours are normal and acceptable.
Do we need a consultant or can IT do it in-house?
Simple rehost of a few VMs: in-house is feasible with training. First migration, regulated data, or tier-1 apps: external AWS migration services Sri Lanka or Azure specialists reduce risk and accelerate landing-zone setup. Hybrid models - consultant designs, internal team operates - work well.
Plan Your Cloud Migration
Workload assessment · AWS/Azure/GCP · landing zone · wave migration · post-migration optimization.
Get Migration Assessment Cloud Solutions