Cloud

Cloud Migration for Philippine SMEs: A Practical Planning Guide

June 5, 2026 · 7min read · The Technica Stack

Cloud migration means different things to different organisations. For a Philippine SME with an on-premise email server, migration might mean simply moving to Microsoft 365. For a manufacturing company with a legacy ERP running on Windows Server 2012, it means lift-and-shift of virtual machines to Azure. For a startup that never had on-premise infrastructure, it means choosing the right SaaS stack from day one.

The planning question is always the same: which workloads should move, to what platform, in what order, and how do we handle the transition without disrupting the business?

This guide covers the planning framework, the common migration patterns, and the mistakes that cause Philippine SME cloud migrations to fail or cost more than expected.

Step 1 — Workload Inventory and Classification

Before planning any migration, document what you currently have. A workload inventory covers:

Workload	Current Location	Users/Dept	Business Criticality	Data Sensitivity
Email (Exchange)	On-prem server	All staff	Critical	High (contains client data)
File server (shared drives)	On-prem NAS	All staff	High	High
Accounting system (QuickBooks, Xero)	On-prem or cloud?	Finance	Critical	High
ERP (SAP B1, Odoo)	On-prem server	Operations	Critical	High
HR/payroll	On-prem or outsourced?	HR	High	High (employee data)
Website and e-commerce	Shared hosting	Marketing	Medium	Medium
CCTV/security footage	NVR on-premise	Security	Low	Medium

Classify each workload by:

Criticality: what happens to the business if this is unavailable for 1 hour? 1 day? 1 week?
Complexity: how many integrations does it have? How customised is it?
Data sensitivity: does it hold personal data (NPC relevance), financial data (BSP relevance), or proprietary business data?
Cloud readiness: does a SaaS equivalent exist? Is it already cloud-hosted?

Step 2 — Choose the Migration Strategy Per Workload

The "6 Rs" framework (originally from AWS, applicable universally) describes the migration strategy for each workload:

Retire

Some workloads have no active users or the function is already covered elsewhere. Decommission them rather than migrate. Common in Philippine SMEs: legacy file servers with years of accumulated files nobody accesses.

Retain

Some workloads should not be migrated yet — too complex, too risky, or not enough business case. Retain on-premise until a later phase.

Rehost (Lift and Shift)

Move the workload to cloud infrastructure with minimal changes. An on-premise Windows Server VM becomes an Azure VM. Same operating system, same applications, different underlying hardware.

When to rehost: legacy applications that cannot be modified, tight migration timelines, temporary step before re-platforming. Not the most cost-optimised long-term but the lowest-risk short-term.

Replatform

Move to the cloud with some modifications — typically replacing the underlying database or runtime. Example: migrate a PHP application from on-premise Linux to Azure App Service, switching from MySQL on a VM to Azure Database for MySQL (managed service).

When to replatform: the application is worth keeping but the operational overhead of managing VMs and databases is not. Managed PaaS services reduce maintenance burden significantly.

Repurchase (SaaS Replacement)

Replace the on-premise application with a SaaS equivalent. On-premise Exchange → Microsoft 365. On-premise file server → SharePoint + OneDrive. On-premise HR system → cloud HRIS.

When to repurchase: a mature SaaS product covers the functional requirements and the on-premise version is a maintenance burden. This is the most common and highest-ROI migration for Philippine SMEs.

Refactor / Re-architect

Redesign the application to be cloud-native. Typically for custom-developed applications. Highest effort, highest long-term benefit. Not the starting point for most Philippine SMEs.

Step 3 — Platform Selection

For Philippine SMEs the practical choice is between Microsoft Azure and Google Cloud, depending on your existing software ecosystem.

Choose Azure if:

Your team uses Microsoft 365 (identity is already in Entra ID)
Your ERP or core application is Microsoft-based (SQL Server, .NET)
You have on-premise Active Directory to sync with Entra ID
You need Azure Virtual Desktop for remote workers

Choose Google Cloud if:

Your team uses Google Workspace
Your workloads are Linux and open-source based
You need BigQuery for data analytics
You prefer Gemini AI integration with your data

For most Philippine SMEs that have started with Microsoft 365 for productivity, Azure is the natural extension — identity, security, compliance, and compute all share the same ecosystem.

Step 4 — Migration Order and Sequence

Migrate in order of lowest risk first:

Phase 1 — Quick wins (lowest risk, highest visible ROI)

Email (Exchange → M365 or on-premise → Google Workspace)
File sharing (file server → SharePoint/OneDrive or Google Drive)
Productivity tools (Office → M365 or Google Workspace)

Email and file sharing migrations are well-understood, have mature tooling (Microsoft Migration Manager, Google Workspace Migration for Microsoft Exchange), and deliver immediate user benefit. They also establish cloud identity (Entra ID or Google identity) as the foundation for subsequent migrations.

Phase 2 — Infrastructure (medium complexity)

Virtualised workloads to Azure/Google Cloud VMs (lift and shift)
Backup and DR replication to cloud
Development and test environments

Phase 3 — Core business applications (higher complexity, higher risk)

ERP migration (on-premise Odoo → Odoo Cloud, on-premise SAP B1 → SAP B1 Cloud)
CRM migration (on-premise → Salesforce, HubSpot, or Dynamics 365)
Custom applications — re-platform or refactor

Step 5 — Cost Estimation

Cloud cost estimation for Philippine SMEs frequently goes wrong in two ways: underestimating cloud costs (no capacity planning) or overestimating savings (forgetting about licensing changes).

What to estimate

Compute: Azure VM or Google Cloud VM costs depend on CPU, RAM, and storage. Use Azure Pricing Calculator (azure.com/pricing/calculator) or Google Cloud Pricing Calculator for estimates. Always model reserved instances (1-year commitment reduces cost 30–40% vs. pay-as-you-go).

Storage: Azure Blob Storage or Google Cloud Storage for backups and cold data. Factor in egress costs — data leaving the cloud region is charged; data entering is free.

Licensing: Moving to M365 or Google Workspace changes your licence model. Calculate the per-user per-month cost against current on-premise server hardware, OS licences, and maintenance costs.

Network: Dedicated internet connectivity or SD-WAN if migrating multiple sites. Ensure Philippine internet connectivity can support cloud-dependent workloads — assess bandwidth and reliability before declaring cloud dependencies.

Common cost surprises

Oversized VMs: Lift-and-shift migrations often replicate on-premise VM sizing without right-sizing for cloud. Use Azure Advisor or Google Cloud Recommender to identify right-sizing opportunities after 30 days of cloud operation.
Egress costs: large data transfers out of cloud (backup restoration, reporting) generate egress charges that were not in the original estimate.
Idle environments: development and test environments left running 24/7 instead of only during working hours.

Common Philippine SME Migration Mistakes

Migrating before establishing cloud identity. Every subsequent service depends on identity (Entra ID or Google Workspace identity). Migrate identity foundation first — everything else connects to it.

Moving the problem instead of solving it. A poorly managed on-premise file server with no permissions structure, mixed old and new files, and no backup becomes a poorly managed cloud file server with the same problems. Fix governance issues before or during migration, not after.

No rollback plan. Define the rollback procedure before migration, not during an incident. Coexistence periods — running both on-premise and cloud simultaneously for 2–4 weeks — allow fallback if issues arise.

No connectivity redundancy. Cloud-dependent workloads require reliable internet. A single PLDT or Globe connection with frequent outages creates worse availability than the on-premise server it replaced. Plan for redundant internet connectivity (dual ISP or mobile failover) for cloud-critical workloads.

Skipping training. Users who do not understand OneDrive/SharePoint or Google Drive sharing models create data governance problems immediately after migration. Include user training in the migration project, not as an afterthought.

If you are planning a cloud migration for your Philippine office — from email and file sharing through to full infrastructure — get in touch.

Talk to our Cloud & I.T. team →