Tech Migration Best Practices

Over the weekend, I read Google's paper on how they use AI for internal code migrations—and it’s packed with insights on how to approach legacy system modernization. I’ve attached the paper for those interested, but here’s how I believe some of these strategies can help us tackle complex modernization challenges: 🔎 1. Accelerating Legacy System Modernization Google leverages Large Language Models (LLMs) to automate large-scale code migrations, significantly reducing manual effort and speeding up projects. Applying similar AI-driven approaches can streamline the modernization of legacy systems, cutting through complexity and outdated code. 🔎 2. Combining AI with Proven Engineering Tools By blending LLMs with Abstract Syntax Tree (AST)-based tools, the ensure accuracy and scalability in their code transformations. This hybrid method shows how AI and traditional engineering techniques can work together to deliver safe and reliable modernization. 🔎 3. Reusable Migration Workflows Google created modular, reusable workflows that make onboarding and executing new migration tasks faster and more efficient. Developing similar toolkits for legacy systems could simplify recurring modernization steps and adapt to complex scenarios. 🔎 4. Measuring Success by Business Impact Google focuses on measurable outcomes, like a 50% reduction in project time, rather than just the volume of AI-generated code. This business-aligned metric highlights the importance of demonstrating clear ROI in technology transformation projects. 🔎 5. Safe and Scalable Rollouts Their phased deployment strategy ensures AI-driven changes are rolled out safely, minimizing disruption. Adopting a controlled rollout approach can help manage risks and ensure stability when modernizing critical systems. 🔎 6. Strategic Use of AI Models Google balances using custom fine-tuned models and general-purpose tools depending on the task. This approach offers valuable insight into when to invest in specialized AI solutions versus using adaptable off-the-shelf models. 📌 The Big Picture: Legacy system modernization is about combining AI-driven efficiency with engineering best practices to deliver faster, safer, and more impactful business transformations. 📎 I’ve attached the paper if you’d like to explore it further! #LegacyModernization #GenAI #BusinessInnovation — Enjoyed this post? Like 👍, comment 💭, or repost ♻️ to share with others.

I constantly hear shocking stories of cloud migration mistakes that spiral into unexpected, skyrocketing costs beyond what anyone ever imagined. Most companies underestimate the complexity. Skip dependency mapping. Pay the price. Cloud migrations go beyond moving workloads - they require knowing what to move, when, and how it affects the rest of your environment. Without a solid plan, you risk unplanned downtime, security gaps, and overspending on misconfigured cloud resources. Here’s how to migrate without chaos: 1. Start with full visibility. Map every application, service, and dependency before migration. Unknown connections lead to downtime, security risks, and hidden costs. Many organizations don’t realize how interconnected their systems are until something breaks. 2. Assess workloads before moving them. Not everything belongs in the cloud. Classify applications by criticality, complexity, and cloud readiness. Legacy systems often need refactoring or special configurations, while certain workloads may be better off staying on-premises. 3. Move in phases, not all at once. A "lift and shift" migration can break critical systems. Migrate in controlled stages, test thoroughly, and adjust before moving forward. Pilot test with non-critical workloads first, gather insights, then move mission-critical systems. 4. Optimize before the migration. Unused resources drain your budget. Right-size workloads, eliminate redundant services, and continuously monitor costs. Cloud sprawl - where forgotten instances keep running - can waste thousands per month. 5. Avoid compliance blind spots. Migrating nodes without visibility can lead to regulatory violations and security gaps. Ensure sensitive workloads follow security best practices before, during, and after migration. The hard truth? You can’t migrate what you don’t know about. Map -> Plan -> Migrate. NO SHORTCUTS.

NEW MIGRATION GUIDANCE - Cloud migrations can be complex, but they don’t have to be uncertain, whether you're moving from on-premises environments or other clouds. To help bring more clarity, we published new Cloud Migration guidance in Microsoft’s Cloud Adoption Framework. This guidance offers a structured roadmap for migrating workloads to Azure from both on-premises and other cloud platforms. It’s the result of close collaboration with Microsoft experts and Microsoft MVPs. It reflects lessons learned from thousands of real-world migrations. The goal is to support teams at any stage of their cloud journey with clear, actionable steps.   Migration Process Overview: 1️⃣ Plan Your Migration 1. Assess readiness and team skills 2. Choose data migration paths 3. Define migration sequencing and rollback plans 4. Engage stakeholders 2️⃣ Prepare Workloads for the Cloud 1. Fix compatibility issues 2. Validate workloads' functionality 3. Build reusable infrastructure 4. Document deployment steps 3️⃣ Execute Migration to the Cloud 1. Prepare stakeholders and freeze changes 2. Finalize production environment 3. Execute cutover and validate success 4. Provide stabilization support 4️⃣Optimize Workloads After Migration 1. Fine-tune configurations in the cloud 2. Collect and act on user feedback 3. Review workloads regularly 4. Optimize hybrid and multicloud dependencies 5️⃣Decommission Source Workloads 1. Confirm decommissioning with stakeholders 2. Reclaim or reassign licenses 3. Preserve data for compliance 4. Update documentation and architecture records 🔗 Explore the new migration guidance here: https://lnkd.in/e2VgCU8m If you're navigating a cloud migration or supporting those who are, I hope this provides the guidance you need. 📣 Acknowledgments: This work reflects the contributions of many across the Microsoft community:   Microsoft MVPs: Stéphane Eyskens, Michael Stephenson, Danny McDermott, Stanislav Zhelyazkov, Joe Carlyle, Scott Corio, Simon Wåhlin, Bert Wolters, Elton Bordim, Haiko Hertes, Robert Hogg, Vladimir Stefanović, Andrew Wilson   Microsoft colleagues: Daniel Söderholm, Ivan Bondy, Rob Rinear, Brody Schulke, Philip Sills, Sandra Patricia Sánchez Martínez, Jack Tracey, Sunil Seth, Timo Salomäki, Michael Lemire, Tomas Kovarik, Larz Stridh, Konstantinos Pantos, Ryan Pfalz, Oscar Zamora, Courtney Taylor, PMP, Kevin Bell, John Lunn, Mannan Mohammed, Mark Piggott, Phani Kumar Teluguti, Yudhbir Singh, Alvaro Guadamillas Herranz CAF Engineering Lead: Jason Bouska Luke Nyswonger, Martin Ekuan, Hans Yang

We migrated 60+ microservices to Kubernetes in 4 weeks. And we threw half the “best practices” out the window. Here’s what actually worked (and what didn’t): 1. 𝐃𝐨𝐧’𝐭 𝐨𝐯𝐞𝐫-𝐚𝐛𝐬𝐭𝐫𝐚𝐜𝐭. We ditched Helm for some services. Why? The templates were bloated. Debugging was a nightmare. For core infra services, raw YAML + Kustomize gave us more control, less magic. 2. 𝐒𝐤𝐢𝐩 𝐭𝐡𝐞 𝐂𝐈/𝐂𝐃 𝐩𝐞𝐫𝐟𝐞𝐜𝐭𝐢𝐨𝐧 𝐭𝐫𝐚𝐩. We didn’t build fancy pipelines upfront. We used kubectl apply with Git-backed manifests for the first two weeks. Speed > Purity. Once stable, we baked in GitOps flows via ArgoCD. 3. 𝐅𝐨𝐫𝐠𝐞𝐭 𝐟𝐮𝐥𝐥-𝐬𝐜𝐚𝐥𝐞 𝐦𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠 (𝐢𝐧𝐢𝐭𝐢𝐚𝐥𝐥𝐲.) We didn’t set up all dashboards on Day 1. Just kubectl top, resource limits, and simple health probes. Only after stabilizing did we plug in Prometheus, Grafana, Loki. 4. 𝐍𝐚𝐦𝐞𝐬𝐩𝐚𝐜𝐞𝐬 > 𝐜𝐥𝐮𝐬𝐭𝐞𝐫𝐬. Everyone says “multi-cluster” is the way. We found namespaces + strong RBAC + network policies was faster, safer, and cheaper to ship fast. 5. 𝐃𝐞𝐟𝐚𝐮𝐥𝐭 𝐥𝐢𝐦𝐢𝐭𝐬 𝐰𝐢𝐥𝐥 𝐡𝐮𝐫𝐭 𝐲𝐨𝐮. We got bitten by K8s defaults. Some pods OOMed. Others ran wild. Set memory/cpu requests+limits for every service. Don’t assume your team will remember. 6. 𝐎𝐧𝐞 𝐭𝐞𝐚𝐦, 𝐨𝐧𝐞 𝐩𝐥𝐚𝐲𝐛𝐨𝐨𝐤. We wrote a 12-page internal doc on service onboarding. No Slack chaos. No tribal knowledge. Everyone knew how to get from local → dev → prod. 7. 𝐌𝐨𝐯𝐞 𝐟𝐚𝐬𝐭, 𝐛𝐮𝐭 𝐛𝐚𝐜𝐤 𝐢𝐭 𝐮𝐩. We snapshot’d etcd + backed up persistent volumes daily. We never needed them. But they let us sleep. 𝐌𝐨𝐬𝐭 𝐊8𝐬 𝐦𝐢𝐠𝐫𝐚𝐭𝐢𝐨𝐧𝐬 𝐟𝐚𝐢𝐥 𝐛𝐞𝐜𝐚𝐮𝐬𝐞 𝐭𝐞𝐚𝐦𝐬 𝐨𝐛𝐬𝐞𝐬𝐬 𝐨𝐯𝐞𝐫 𝐭𝐨𝐨𝐥𝐢𝐧𝐠 𝐚𝐧𝐝 𝐢𝐠𝐧𝐨𝐫𝐞 𝐭𝐞𝐚𝐦 𝐚𝐥𝐢𝐠𝐧𝐦𝐞𝐧𝐭. We shipped in 4 weeks not because we followed the rules. But because we knew exactly which ones to break. If you’re planning a K8s migration, I’ll happily share our internal playbook. Just comment “K8s” and I’ll DM it.

The next few years are going to be tough. Many legacy applications finally need to be modernized.  10 actions to survive. 1. Focus: Not every functionality needs to be migrated. Strict scope management based on real customer needs is crucial. What's your approach to scope prioritization? 2. Outcome-driven: Delivered functionality isn't the main success criterion - improved business value is. In my last project, we delivered 18% more revenue with just 60% of the migrated functionality. What metrics matter most in your modernization efforts? 3. Data-driven: Validate the value of each delivered feature through A/B testing. Combine quantitative data with user stories to paint the complete picture. 4. Incremental and iterative: From month one, deploy continuously to production through a robust delivery pipeline. Daily releases should be your minimum target. Agile and DevOps work. 5. Fail fast: Build and validate technically risky and commercially important functionalities first. Minimize basic functionality. Effectiveness before efficiency. 6. Experience-based: Don't reinvent the wheel. Learn from others who've succeeded. Shamelessly adopt state-of-the-art practices that work. 7. Human-centric: Your employees are critical to success. They understand customer needs, business processes, and legacy systems. Blend their experience with external expertise and invest in change management. 8. Be adaptable: We plan, God laughs. Observe, reflect, and adapt regularly at every organizational level. Stay self-critical and embrace change. 9. Cost-aware: Modernization isn't just about technology - it's about business value. Track and communicate both investment and returns. Create transparency about technical debt reduction and new revenue opportunities. 10. Future-proof: Design for change, not just today's requirements. Choose modern, maintainable architectures and build technical excellence into your culture. Microservices aren't dead. Which of these measures resonates most with your experience? What would you add to this list? Share your thoughts in the comments!

One mistake I see in cloud migrations over and over is that teams lift-and-shift apps into cloud VMs and then wonder why costs and security get worse. Here's what actually matters. In many cases, people do just a lift-and-shift. They pick up an application, figure out a way to run it in a VM, move it over into the cloud, and forget it. But unless they do a business impact assessment and a technology architecture review, they’re probably going to end up with higher costs, worse security, and an application that may not meet current business needs. I’ve done it myself. When I was CIO at Microsoft, my goal was to get out of our data centers and move as much as I could to Microsoft Azure. Some apps we re-architected. Others, we just parked in VMs and said, “We’ll get to it next year.” That wasn’t optimal, but at the time, it let us vacate data centers and retire old equipment. The problem isn’t that lift-and-shift is generally wrong, but when leaders treat it as the default strategy, instead of a short-term fix with a plan behind it. Here’s how I’ve learned to approach it: 1. Inventory and prioritize your apps. Not everything is mission-critical, but not everything should be punted either. 2. Do a business-impact assessment and a technology architecture review. Without these, you risk higher costs and worse outcomes. 3. Use specialists, not generalists. Moving apps is like redoing plumbing. You can ask me to figure it out, but it’ll take me three times as long, and it won’t look good. And, if not properly performed, can lead to disaster. It’s worth it to have people who know the craft. 4. Allow temporary “parking” in VMs* but set a clear timeline to revisit, and then force a decision to terminate or optimize for cloud. Short-term convenience without discipline creates long-term debt. Costs rise, risks increase, and you may be burdened with apps that don’t do what the business needs.

𝐋𝐞𝐬𝐬𝐨𝐧𝐬 𝐈’𝐯𝐞 𝐥𝐞𝐚𝐫𝐧𝐞𝐝 𝐟𝐫𝐨𝐦 𝐬𝐭𝐚𝐥𝐥𝐞𝐝 𝐂𝐥𝐨𝐮𝐝 𝐌𝐢𝐠𝐫𝐚𝐭𝐢𝐨𝐧 𝐏𝐫𝐨𝐨𝐟 𝐨𝐟 𝐂𝐨𝐧𝐜𝐞𝐩𝐭𝐬? I was talking to a colleague earlier in the week about his upcoming cloud migration proof of concept his team was running leading, and we started comparing one cloud provider to another. What began as a technical discussion quickly became familiar. Most migrations do not struggle because of the cloud platform. They struggle because of what happens before anyone moves a workload. As we talked, I sketched out migration options with time, cost, and complexity in mind. The data center lease was expiring in nine months, which forced an honest question, what could they retire instead of migrating? That conversation took me back to a lesson I learned the hard way early in my career. Migration success is not driven by diagrams or speed. It is driven by the Assess phase. This is where the AWS Cloud Adoption Framework really clicked for me. AWS, Azure, and GCP all approach this differently, but the objectives are the same. Slow down. Get clear. Set direction. 𝐀𝐬𝐬𝐞𝐬𝐬 𝐬𝐭𝐚𝐫𝐭𝐬 𝐰𝐢𝐭𝐡 𝐰𝐡𝐲. Cost optimization. Security posture. Agility. Regulatory alignment. When teams cannot articulate this, migrations become reactive instead of strategic, and it shows up later in 𝐃𝐚𝐲 𝟐 𝐨𝐩𝐞𝐫𝐚𝐭𝐢𝐨𝐧𝐬. I have seen teams lift years of technical debt into the cloud and wonder why nothing feels simpler. Starting with small proofs of concept, partnering early with network and platform teams, and application portfolio discovery changes that outcome. Deciding whether to rehost, replatform, refactor, repurchase, retire, or retain forces honest conversations about value and risk. Cost modeling was another turning point for me. Cloud does not magically reduce spend or reduce risk. Accurate inventory, right sizing, and realistic TCO modeling are what build trust with finance and leadership. And finally, the people. No migration I have been part of succeeded without alignment and clear communication. End users want to understand impact. Leaders want clarity on risk and return. Over the last five years, I've grown to think of the Assess phase like drafting a blueprint before building a house. Survey the land. Align on the vision. Agree on the budget. Then build. After a three hour discussion, we both walked away with renewed energy and a shared belief that early engagement with stakeholders is what enables strong collaboration and successful migrations. 𝑰𝒇 𝒚𝒐𝒖 𝒉𝒂𝒗𝒆 𝒃𝒆𝒆𝒏 𝒕𝒉𝒓𝒐𝒖𝒈𝒉 𝒂 𝒄𝒍𝒐𝒖𝒅 𝒎𝒊𝒈𝒓𝒂𝒕𝒊𝒐𝒏, 𝒘𝒉𝒂𝒕 𝒅𝒐 𝒚𝒐𝒖 𝒘𝒊𝒔𝒉 𝒚𝒐𝒖 𝒉𝒂𝒅 𝒔𝒑𝒆𝒏𝒕 𝒎𝒐𝒓𝒆 𝒕𝒊𝒎𝒆 𝒂𝒔𝒔𝒆𝒔𝒔𝒊𝒏𝒈 𝒖𝒑 𝒇𝒓𝒐𝒏𝒕?

In the early days, I wrote scripts to migrate 50,000 SAP tables by hand. Today, tools do it in minutes. But if you don’t understand what’s under the hood, you’re one error away from failure. Back then, we didn’t have automation platforms. If you wanted to migrate 30 SAP systems, you wrote custom scripts. Dozens of them. Sometimes hundreds. I built them to break big databases into chunks — to move data in parallel, keep runtimes low, and hit the downtime window. Eventually, some of those techniques became tools. But here’s the problem I see now: Most teams depend on the tool — and forget the process. And when the tool breaks? They’re stuck. Here’s what I learned building migrations from the ground up: 1. Scripts are brittle — systems are resilient Custom scripts solve one problem well. But if your environment changes, they crack. Platforms adapt. 2. Visibility matters more than clever code You can’t fix what you can’t see. Good systems surface the status of every step, every dependency, every failure point. 3. You need both abstraction and expertise It’s fine to use higher-level tools. But someone on your team still needs to understand how the migration logic works underneath. 4. Error handling is more important than execution speed Fast is useless if it fails silently. Mature platforms log, notify, and auto-recover when things go sideways. 5. The real value is orchestration, not just movement It’s not just about moving data — it’s about coordinating steps, managing downtime, validating results, and aligning with the business window. Most migration failures I see today don’t happen because the tech is bad. They happen because nobody knows what to do when the automation stops. So yes — use the best tools you can. But don’t forget the discipline behind them. That’s why I built IT-Conductor Inc. to solve: Repeatable, reliable migrations — with orchestration baked in.

Analytics Migration: More Than Lift-and-Shift We’ve talked about #dataplatforms as the foundation. We’ve talked about #analyticsstrategy as the bridge to outcomes. Now comes the step that makes both actually work: Migrating analytics at scale — without losing value along the way. Too often, migrations are treated like a moving day: 📦 Box up all your dashboards. 🚚 Move them to the new platform. ✅ Call it done. But here’s the truth — a migration is a transformation moment. Done well, it declutters, standardizes, and positions analytics to fuel AI at scale. Done poorly, it drags old problems into your new world. From my experience and research, the most successful migrations follow a clear framework: 1. Rationalize what exists (and retire the noise) 2. Prioritize high-value analytics 3. Execute with domain-aligned teams 4. Enable adoption with training and champions 5. Measure usage and iterate 6. Modernize instead of replicating the past I’ve broken this down into a 6-step visual framework in the carousel below 👇 — designed to help leaders turn migrations into a competitive advantage, not just a tech upgrade. If you’ve been through an analytics migration: What’s the one thing you’d do differently next time? #AnalyticsStrategy #DataPlatform #AnalyticsMigration #AIEnablement #ChangeManagement #InsightsToAction

Server migrations can feel like walking a tightrope. One wrong step and suddenly no one can log in, apps break, and panic sets in. Why this matters: Migrations aren’t “lift and shift.” They’re precision moves where sequence and preparation make all the difference between smooth sailing and chaos. Here’s how I approach server migrations: 1. Build Domain Controllers Fresh • Never “migrate” a DC—always set it up from scratch. • Verify replication, FSMO role transfers, and DNS health before touching the old one. 2. Document Dependencies Early • Inventory apps, databases, and shares tied to the old server. • Confirm with users instead of assuming what’s “not used anymore.” 3. Stage Data the Right Way • Pre-seed large file shares so cutover day isn’t a bandwidth nightmare. • Always check NTFS + share permissions, not just one or the other. 4. Control the Cutover Window • Pick a downtime window that fits the business, not just IT convenience. • Communicate what’s happening, when, and what to expect after. 5. Validate Before Retiring • Test authentication, apps, and mapped drives from multiple user machines. • Only decommission old servers once you’ve triple-checked success. Server migrations aren’t just technical—they’re about protecting the business from disruption. What’s your golden rule for a smooth migration? #TechTips #ITSupport #ServerMigration #ActiveDirectory #SysAdmin #SystemEngineer #MSPLife #DocumentationMatters #InfrastructureHygiene