<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Migrations on Corrupted Glitch</title>
		<link>https://corruptedglitch.netlify.app/categories/migrations/</link>
		<description>Recent content in Migrations on Corrupted Glitch</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 18 Jul 2026 23:13:02 -0400</lastBuildDate>
		
			<atom:link href="https://corruptedglitch.netlify.app/categories/migrations/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Automating the Great Escape: Cloud Migration Pipelines with an AI Copilot in the Loop</title>
				<link>https://corruptedglitch.netlify.app/posts/sample-devops-migration/</link>
				<pubDate>Tue, 14 Jul 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/posts/sample-devops-migration/</guid>
				<description>&lt;p&gt;Every datacenter exit starts the same way: someone opens a spreadsheet with 1,400 rows, and someone else says &amp;ldquo;we&amp;rsquo;ll just lift and shift.&amp;rdquo; Eighteen months later, half the estate is still on-prem and the spreadsheet has become sentient.&lt;/p&gt;&#xA;&lt;p&gt;This is a field report from a migration that didn&amp;rsquo;t go that way — 140 production workloads moved in 11 months, zero rollback events. The difference wasn&amp;rsquo;t heroics. It was treating the migration as a &lt;strong&gt;factory&lt;/strong&gt;, not a project, and putting an AI copilot inside the loop where humans were the bottleneck.&lt;/p&gt;</description>
			</item>
			<item>
				<title>MSP Migrations by the Numbers: What 200 Client Moves Taught Us</title>
				<link>https://corruptedglitch.netlify.app/posts/msp-migrations-by-the-numbers/</link>
				<pubDate>Tue, 30 Jun 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/posts/msp-migrations-by-the-numbers/</guid>
				<description>&lt;p&gt;Managed service providers migrate other people&amp;rsquo;s infrastructure for a living, which means the dataset is bigger and more honest than any single enterprise&amp;rsquo;s war story. This post aggregates anonymized data from &lt;strong&gt;214 client migrations&lt;/strong&gt; executed between 2021 and 2026 — SMB to mid-market, 20 to 2,000 seats.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Project 01: Datacenter Exit &amp; Identity Transformation</title>
				<link>https://corruptedglitch.netlify.app/projects/project-01-datacenter-exit/</link>
				<pubDate>Sat, 20 Jun 2026 09:00:00 -0500</pubDate>
				<guid>https://corruptedglitch.netlify.app/projects/project-01-datacenter-exit/</guid>
				<description>&lt;p&gt;The mission: exit a physical datacenter completely, retire on-prem Active Directory, and land every workload and identity in a cloud-native model. Outcome: 20% opex reduction, 27 apps consolidated under SSO, zero business interruption.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
