SaaS datacenter migration, as SQL SME
Served as subject-matter expert and lead engineer from the SQL team on the datacenter migration for Expesite, supporting production systems across both public and private cloud throughout the transition.
Cloud & Infrastructure Architecture
Senior Systems Engineer — Azure and hybrid cloud architecture, enterprise migration, data platforms, and disaster recovery.
Nineteen-plus years across systems administration, infrastructure engineering, and cloud architecture. I work on the parts of a migration that carry real risk: estate discovery, wave planning, cutover, and recovery that has been tested rather than assumed. Datacenter transitions for production SaaS, SQL Server platform modernization, and DR runbooks written against contractual SLA, RTO, and RPO targets.
What I build
Migrations rarely fail on the technology. They fail on the dependency nobody mapped, the runbook nobody tested, and the cutover window that turned out to be four hours shorter than it needed to be. These are the areas I have spent a career in.
Azure landing zones, hybrid connectivity, and identity integration designed so the foundation is reproducible rather than a set of portal clicks nobody can repeat.
Moving real estates, not lab samples. Dependency mapping, wave planning, rehost-versus-replatform calls, a pilot wave before the fleet, and a rollback path worth using.
SQL Server version upgrades and platform transitions, with performance baselines captured before and after, plus warehouse and analytics work across modern platforms.
DR designed against the SLA, RTO, and RPO actually committed to in customer contracts — with runbooks written so someone other than the author can execute them.
Selected impact
A shortlist of engagements where the outcome was measurable and the failure mode was public.
Served as subject-matter expert and lead engineer from the SQL team on the datacenter migration for Expesite, supporting production systems across both public and private cloud throughout the transition.
Authored the disaster recovery runbook and method of procedure for Expesite, built against the product's actual SLA, RTO, and RPO commitments rather than aspirational targets — then maintained the plan and ran regular tests against it.
Led the version upgrade for SaaS application Lucernex, alongside building and maintaining multi-layered redundant production environments sized to meet committed SLAs.
Designed, integrated, and implemented a Microsoft Azure hybrid cloud solution enterprise-wide at a bank — running alongside core banking platforms from FIS, Fiserv, Finastra, Banker's Toolbox, and Ellie Mae.
Supported Boeing's SLS program at NASA MAF: VPN and network connectivity, certificate, token, and smart card access, and a fleet-wide replacement of VMware ESX 6.0 hosts with 6.5 across the datacenter.
Ran hosting infrastructure at a peak of roughly 300 domains, 150 websites, and 6,000 mailboxes — and virtualized every last physical server on the network.
Professional experience
From Tier 2 network support to senior escalation engineering for Microsoft Premier customers — with datacenter, banking, aerospace, and SaaS environments in between.
St. Louis, MO · Remote
St. Louis, MO · Remote
New Orleans, LA · Hybrid
Greater New Orleans Area
New Orleans, LA
Concurrent contract engagement alongside the Fidelity Bank role above.
Hattiesburg, MS
Hattiesburg, MS
Hattiesburg, MS
Hattiesburg, MS
Hattiesburg, MS
Hattiesburg, MS
Labs & projects
Production experience is the record. These are the environments I stand up on my own time to keep the reference architectures current — and to have something to point at rather than describe.
Placeholder content. These four tracks are scaffolding while the lab environments are being built out. Each card will be replaced with the real build: architecture diagram, infrastructure-as-code repository, and a written summary of what was proven.
A reference enterprise-scale landing zone built entirely from infrastructure-as-code: management group hierarchy, subscription design, hub-and-spoke networking, policy and governance guardrails, and cost tagging that survives contact with a real subscription.
An on-premises forest synchronized to a tenant, exercising the scenarios that actually cause trouble: sync error remediation, conditional access design, privileged access review, and a tenant-to-tenant consolidation of the kind that follows an acquisition.
A SQL Server estate carried through the modernization route end to end — compatibility assessment, performance baselines captured before and after, migration to a managed platform, and ingestion into a warehouse and analytics layer on top.
Replication and backup architecture designed against a stated RTO and RPO, a recovery runbook written for someone other than its author, and a documented failover test that demonstrates the numbers hold. Most DR plans have never been run.
Technical depth
Education & honors
Franklin University · 2017
Jones County Junior College · 2007
Get in touch
If you are planning a migration, modernizing a data platform, or trying to find out whether your disaster recovery plan would survive being run — that is the conversation I am good at. Reply time is within one business day, in writing.