Black Forest Systems LLC
Cloud migration and platform engineering

Private to public cloud migration for small IT teams that need an experienced architect.

I'm Andrew Watson. After 29 years running infrastructure at a Colorado liberal arts college, including designing its strategy for moving from on-premises systems to Azure, I take on a small number of engagements: migration planning, platform upgrades, and assessments for teams that don't have a cloud architect on staff.

Get in touch
29 yearsin one IT department, from help desk to systems engineer
3 yearsleading a college's phased move to Azure
300 → 230on-premises VMware VMs after migrations
About halfthe licensed server CPU cores, after Broadcom's pricing change

How I approach migration

Move each workload when its application is due for an upgrade.

A go-slow plan avoids big-bang cutovers and avoids paying twice for the same work. For each workload I pick the lowest-effort route that fits.

Move to SaaS

When the application is replaced anyway, a hosted product often beats running it yourself.

Re-platform to Azure web apps

Websites move to native Azure App Service, so there is no server to patch.

Lift and shift to Azure VMs

When there is no time to change the app, move the whole VM and fix it up later.

What I do

Cloud migration first, with the platform work around it.

Private to public cloud migration

Strategy and architecture for moving on-premises workloads to Azure: workload assessment, landing zone and network design, identity and hybrid connectivity, cost modeling, migration sequencing, and a clear answer on what should stay on-premises. I favor a gradual approach: move each workload when its application is due for an upgrade, and choose SaaS, a native Azure service, or lift and shift case by case.

VMware strategy: upgrade, move, or exit

vSphere 8 to VCF or VVF 9, core counts and licensing under the new model, hardware refreshes, and a straight comparison with moving the workload to the cloud or to another platform.

Identity and endpoint

Microsoft Entra, Intune, and Active Directory upgrades, plus Global Secure Access Private Access to replace legacy VPN.

Automation

Ansible Automation Platform migrations, playbooks, and the runbooks your team needs to keep using them.

Remote access and certificates

Horizon, Unified Access Gateways, load balancers, and certificate renewals that don't break anything.

Short engagements

Assessments, documentation, and on-call help for a few hours or a few weeks. Retainers are available.

Recent work

What I've done lately.

  • Architected a college's cloud migration and led its first three years. Workloads moved gradually, timed to each application's upgrade cycle: to SaaS, re-platformed as Azure web apps, or lifted and shifted to Azure VMs.
  • Reduced on-premises VMware VMs from about 300 to about 230 and cut licensed server CPU cores by roughly half, which helped keep a steep increase in VMware licensing costs after Broadcom's changes manageable.
  • Upgraded a vSphere 8 environment to 9.1 with VCF Operations, including a colocation hardware refresh.
  • Ran a rolling Active Directory domain controller upgrade to Windows Server 2022.
  • Planned the move of Ansible Automation Platform from 2.4 on-premises to a 2.6 containerized deployment in Azure.

About

One department, 29 years, and the habit of writing things down.

I started on a help desk in 1997 and spent the rest of my career in one IT department, moving from support to systems administration to systems engineer. I owned the virtualization, identity, and automation stack, and I was the architect of the college's cloud migration strategy: what moves, in what order, and what stays on-premises.

I work in higher education, nonprofits, and small organizations, where one engineer often covers everything and a specialist is hard to justify full time. I write things down, and I leave your team able to run what I built.

Tell me what you're working on.

Send a short description of the project and your timeline. I reply within one business day.