Cloud Migration for Berlin SMBs: A Practical Guide to Moving from On-Premise to Azure

Moving your IT infrastructure from on-premise servers to the cloud is one of the highest-leverage investments a Berlin SMB can make — but only when done with a clear plan. Done wrong, cloud migration creates cost overruns, security gaps, and operational disruption. Done right, it eliminates the capital expense of ageing hardware, improves resilience, and gives your team the flexibility to work from anywhere.

This guide covers the practical steps for migrating a typical Berlin small business from on-premise infrastructure to Microsoft Azure and Microsoft 365 — the most common path for SMBs in Germany.

Why Berlin SMBs Are Moving to the Cloud Now

The drivers are consistent across sectors:

• Ageing hardware refresh cycles. Server hardware typically has a 5-7 year lifespan. When it’s time to replace, the cloud is often cheaper over a 3-year TCO than buying new on-premise hardware.
• Remote and hybrid work. If your team works from home or across multiple offices, cloud-hosted resources eliminate VPN dependency and improve performance.
• Compliance requirements. DSGVO and NIS2 create strong incentives to move data to certified cloud infrastructure with documented security controls.
• Reduced IT management overhead. Cloud platforms handle hardware maintenance, patching, and physical security — removing significant operational burden.

Phase 1: Assessment and Planning (Weeks 1-2)

A cloud migration without an inventory is a migration that fails. Before touching anything, document:

Infrastructure Inventory

• All physical servers — role, OS version, CPU/RAM/storage, age, and current utilisation
• All line-of-business applications — vendor, version, licensing model, and cloud readiness (SaaS available? Runs on Azure? Requires physical hardware?)
• Network topology — internet bandwidth, firewall/router hardware, VPN configuration
• Backup systems — what’s backed up, where, retention period, last tested restore
• Active Directory / identity — number of users, groups, GPO complexity

Application Cloud Readiness Classification

Classify each application into one of four categories:

• Replace with SaaS: If a cloud-native alternative exists (e.g., replace on-premise Exchange with Microsoft 365, replace on-premise file server with SharePoint/OneDrive). This is the fastest path to value.
• Lift and shift to Azure VM: Applications that run on Windows Server but have no SaaS alternative. Move the VM to Azure with minimal modification.
• Retain on-premise: Applications that require physical hardware (manufacturing control systems, specific line-of-business software with hardware dependencies, very latency-sensitive workloads).
• Retire: Applications no longer actively used. Don’t migrate dead weight to the cloud.

Phase 2: Microsoft 365 First (Weeks 3-6)

For most Berlin SMBs, Microsoft 365 is the right starting point. Migrating email, files, and identity to M365 delivers immediate value and removes your two highest-risk on-premise dependencies: Exchange Server and file servers.

Email Migration (Exchange to M365)

• Run the Microsoft 365 Mail Migration Advisor to generate a migration plan
• For mailboxes under 20GB: cutover migration (single-phase, all mailboxes at once) works well for businesses under 150 users
• For larger organisations: staged migration or hybrid configuration
• DNS cutover: update MX records during low-traffic window (weekend)
• Validate: send/receive test from all client types (Outlook desktop, mobile, web)

File Server Migration (SharePoint / OneDrive)

• Use SharePoint Migration Tool (SPMT) for bulk content migration
• Map existing shared drive structure to SharePoint document libraries
• Migrate personal/home drives to OneDrive for Business
• Deploy OneDrive sync client to all endpoints via Intune or GPO
• Run parallel access for 2-4 weeks before decommissioning file server

Identity: Hybrid Azure AD / Entra ID

• Deploy Azure AD Connect to sync on-premise Active Directory to Entra ID
• Enable Password Hash Synchronisation (PHS) for seamless SSO
• Once cloud workloads are fully migrated, evaluate transitioning to cloud-only identity (Entra ID Join) — eliminates on-premise AD dependency entirely

Phase 3: Server Workloads to Azure (Weeks 6-12)

After email and files are in M365, migrate remaining server workloads to Azure.

Azure VM Sizing

Right-sizing is critical. Many organisations over-provision cloud VMs and overspend. Use Azure Migrate to assess on-premise VMs and generate Azure VM size recommendations based on actual CPU and memory utilisation — not theoretical peaks.

Workload	Typical Azure SKU	Cost Optimisation
Small file server / DC	B2s (2 vCPU, 4GB)	Reserved instance (1-year)
Line-of-business app server	D4s_v5 (4 vCPU, 16GB)	Auto-shutdown during off-hours
SQL Server	Azure SQL Managed Instance or E4s_v5	Azure Hybrid Benefit (existing SQL licence)
Remote Desktop / AVD	Azure Virtual Desktop pooled host pool	Autoscale host pool to zero after hours

Azure Cost Controls

• Azure Cost Management + Billing — set budget alerts at 80% and 100% of monthly budget. Don’t discover overspend at month-end.
• Reserved Instances — for VMs running 24/7, 1-year reserved instances save 30-40% vs. pay-as-you-go.
• Auto-shutdown — development/test VMs should auto-shutdown at 18:00 and auto-start at 08:00. This alone cuts non-production VM costs by 60%.
• Azure Hybrid Benefit — if you have existing Windows Server or SQL Server licences with Software Assurance, use AHB to avoid paying for the OS licence again in Azure.

Phase 4: Security and Compliance Hardening

Cloud migration is not complete until the security baseline is set. Minimum requirements for a Berlin SMB on Azure/M365:

• MFA enforced via Conditional Access for all users — no exceptions, no legacy auth
• Microsoft Defender for Business enabled on all endpoints
• Azure Backup configured for all VMs (policy: daily backup, 30-day retention minimum)
• Microsoft Secure Score reviewed and actioned — target 70+ for SMB baseline
• Privileged Identity Management (PIM) for admin accounts if using Entra ID P2
• Audit logs retained (Entra ID sign-in logs, Azure Activity log) — minimum 30 days, 90 days preferred for DSGVO incident response capability

Common Migration Mistakes to Avoid

• Migrating without a rollback plan. For every workload, define what triggers a rollback and how long it takes to restore on-premise service. Test the rollback before the production cutover.
• Underestimating bandwidth requirements. OneDrive initial sync for 200 users with 50GB each is 10TB of data movement. Plan for it — stage the rollout or use Azure Data Box for large datasets.
• Skipping user training. The biggest migration failures are adoption failures. Train users on SharePoint/OneDrive before cutover, not after.
• Over-provisioning and not revisiting. Review Azure VM utilisation at 30 and 90 days post-migration. Downsize anything running below 20% CPU average.
• Forgetting third-party MX records and email filtering. If you use a third-party spam filter (Mimecast, Proofpoint), update its relay configuration when migrating to M365.

Typical Timeline and Cost Expectations

For a Berlin SMB with 10-50 users:

• Assessment and planning: 1-2 weeks
• M365 migration (email + files): 2-4 weeks
• Server workload migration: 4-8 weeks (varies by application complexity)
• Total project duration: 2-3 months for a straightforward environment
• Monthly Azure/M365 run cost: typically EUR 50-120 per user per month depending on licences and VM workloads — compare this against your current hardware depreciation, maintenance contracts, and power costs

Next Steps

If you’re considering a cloud migration and want to understand the scope and cost for your specific environment, the right starting point is an IT infrastructure assessment. This gives you an inventory of your current environment, a cloud readiness classification for each workload, and a realistic migration timeline and budget — before you commit to anything.