Inventory what you run, map what depends on what, decide what moves and what retires, sort out identity, then migrate in phases with a rollback plan for each. Most Azure migrations that go wrong in Philippine SMEs do not fail on Azure. They fail on the accounting system nobody mentioned, the database on a different server, or the staff login that stopped working on Monday morning. This checklist covers the work before, during and after the move.
Treat the migration as three separate projects. Before: assessment, dependency mapping and identity. During: phased workload moves with real-user testing. After: cost control, security hardening and decommissioning the old hardware.
Organisations that skip the first phase pay for it in the second. Organisations that skip the third end up paying Azure and the electricity bill for the old server room at the same time.
Servers, virtual machines, shared drives, databases, and the applications that depend on them. Include the ones only Finance uses, the ones only one person knows the password to, and the ones that were supposed to be retired two years ago. Those are the workloads that break migrations, because nobody planned for them.
A payroll application may rely on a SQL database on a separate server, which authenticates against an on-premises Active Directory, which is also the DNS server for the office. Move one piece without the others and you have an outage. Draw the map before you decide the order.
Not every workload should be lifted into Azure as-is. A legacy file share is often better placed in SharePoint or Azure Files. An ageing application server may be replaced outright by a SaaS product. A test server nobody has logged into since 2023 should simply be switched off. Retiring a workload is a valid migration outcome, and usually the cheapest one.
If you already run Microsoft 365, Microsoft Entra ID hybrid identity keeps your on-premises Active Directory and cloud identities in sync during the transition. This is the piece that decides whether staff sign in the same way on the first day of the new environment. Plan it early, because everything else authenticates through it.
Under the Microsoft Cloud Solution Provider programme, Azure consumption, Microsoft 365 and support can sit under one partner and one peso invoice with an official receipt. Confirm this before signing anything, particularly if you are currently paying an overseas provider by credit card and reconciling in dollars. CSP licensing also affects whether existing Microsoft 365 seats already entitle your users to Azure Virtual Desktop at no extra per-user cost.
Low-risk workloads first: file shares, test environments, anything that can be rolled back in an hour. Then the systems people cannot work without. Every phase needs a rollback plan that has actually been rehearsed, not just written down.
If the move includes a change of Microsoft 365 tenant, a tenant-to-tenant migration is its own phase with its own cutover window. Do not bundle it with a server move.
The migration is not done when the virtual machine boots. It is done when the accountant can open the ledger, the sales team can find the pricing folder, and the branch office can print. Involve the people who use the systems in acceptance testing, and give them a checklist of the things they do every day.
Azure Virtual Desktop gives every employee a secure, managed Windows desktop reachable from any device. Data stays in Azure rather than on a personal laptop in a coffee shop. For teams spread across provinces, it is often the reason an SME looks at Azure in the first place. If you are weighing it against Windows 365, our comparison of the two covers the pricing models and licensing prerequisites.
Azure lets you scale, which means it also lets you overspend. Set cost alerts on day one, review virtual machine sizes after the first full month, and schedule automatic shutdown for anything that does not need to run overnight or at weekends. Reserved instances for steady workloads can cut compute cost substantially, but only commit once you know the real usage pattern.
Multi-factor authentication on every account, conditional access policies enforced rather than left in report-only mode, backups configured and restore-tested, and endpoint protection on every device that connects. A migration is the natural moment to fix the security debt that accumulated with the old setup, because you are already touching everything.
Wipe it, document what was on it, and stop paying for the power, the UPS batteries and the air-conditioning that kept it alive. Hardware that stays plugged in "just in case" becomes a security liability within months, and a cost you have forgotten you are paying.
It depends on the number of workloads and how tangled the dependencies are. A straightforward file server and a handful of applications can move in a few weeks once assessment is complete. An environment with legacy line-of-business systems and an on-premises domain typically takes longer, and most of the extra time is in the assessment and identity work rather than the migration itself.
No. Hybrid environments are common and often sensible. Some workloads stay on-premises for latency, licensing or regulatory reasons while the rest move. The assessment phase is where that decision gets made, workload by workload.
Not if identity is handled properly. With hybrid identity in place, users keep the same username and password, and the same sign-in experience, whether the resource they are opening is still on-premises or already in Azure.
Yes, through a Philippine Cloud Solution Provider. Azure consumption is invoiced locally in Philippine pesos with an official receipt, rather than charged in dollars to a credit card.
Once workloads are confirmed running in Azure and the rollback window has passed, the old hardware should be securely wiped and decommissioned. Keeping it powered on indefinitely is both a cost and a security risk.
Onprem2Cloud IT Solutions Co. is a Microsoft Cloud Solution Provider based in Muntinlupa City, serving businesses and government agencies across the Philippines. We handle Azure migrations end to end: assessment and dependency mapping, hybrid identity, tenant-to-tenant and server migration, Azure Virtual Desktop deployment, and ongoing licensing and cost management. Everything is billed in Philippine pesos with official receipts. Get in touch to arrange an assessment of your environment.
Our latest news and trending topics