> Markdown version of [/videos/100164-the-migration-cookbook?t=1663](https://www.wearedevelopers.com/videos/100164-the-migration-cookbook?t=1663). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# The Migration Cookbook

Software migrations fail for the same social reasons historical empires collapse. Discover why aligning team incentives is the real secret to a painless technical transition.

- **Speakers:** [Robert Lehmann](https://www.wearedevelopers.com/@robert-lehmann)
- **Event:** World Congress 2026 Europe
- **Published:** July 9, 2026
- **Duration:** 30:16
- **URL:** https://www.wearedevelopers.com/videos/100164-the-migration-cookbook

## Summary

The narrative arc traces the lifecycle of an enterprise software migration, drawing a parallel to the overly aggressive and poorly communicated reforms of Emperor Joseph II to highlight why change management is primarily a social challenge rather than a technical one. Successful migrations require a staged, empathetic approach rather than an abrupt "big bang." The process must begin with rigorous requirements engineering to uncover the actual business goals users achieve with the legacy system, leveraging logs and analytics to objectively challenge assumptions about strict "snowflake" use cases.

To execute the transition efficiently, it is crucial to "stop the bleeding" early by halting new signups or API token generation for the legacy platform. A core insight is to enforce aligned incentives: the same team must own both the legacy and the replacement products. This shared burden encourages the driving team to shoulder at least 80% of the migration effort, significantly lowering the transition cost for end-users through robust automation. Throughout the process, over-communication is vital. Tailoring the messaging—providing tactical guidance to individual contributors while offering tailored business impact data to senior leadership—ensures organizational alignment. Furthermore, identifying a "common enemy," such as a deprecated upstream dependency, contextualizes the change and prevents the migration team from serving as the bad cop.

As the migration progresses, segmenting rollouts allows for smaller, reversible steps, while employing techniques like the dual write pattern ensures data migrations aren't bottlenecked by slow adopters. Because documentation is rarely sufficient on its own, equipping support teams with an evolving bank of canned responses helps seamlessly manage edge cases. Wrapping up the transition involves preserving backward compatibility via lightweight URL redirectors, issuing a playful threat to hand over the legacy pager to uncooperative stragglers to motivate final adoption, and celebrating early wins to empower migration champions for future phases.

**Keywords:** enterprise software migrations, change management, requirements engineering, legacy system deprecation, dual write pattern, backward compatibility shim, stakeholder management, segmented deployment rollouts, migration automation tooling, legacy product ownership, straggler transition strategy, internal platform adoption, api token deprecation, canned support responses

## Chapters

1. **Learning from historical change management failures** (00:25) — How top-down forced changes without stakeholder input lead to massive rollbacks.
1. **Analyzing legacy product use cases before starting** (07:49) — Determining what goals users actually accomplish with a legacy tool rather than mapping exact features.
1. **Stopping new usage of the legacy product** (11:32) — How to halt the creation of new users or access tokens to stop the legacy user base from growing.
1. **Staffing and incentivizing internal migration teams** (12:39) — Assigning the same team to own both the legacy and new systems aligns incentives for completing the transfer.
1. **Communicating migration plans clearly and specifically** (15:41) — Using repeated messaging, designated figureheads, and tailored impact reports for leadership helps ease user transitions.
1. **Executing targeted segment migrations over big bangs** (20:24) — Breaking rollouts into small groups allows for independent rollbacks and continuous partial successes.
1. **Preparing canned support responses for edge cases** (22:36) — Equipping support teams with prepared answers for edge cases proves more effective than relying on documentation alone.
1. **Maintaining backward compatibility using simple shims** (23:47) — Preserving legacy URLs through simple rewrite components avoids frustrating users with broken internal links.
1. **Handling straggler teams that avoid migrating** (25:58) — Threatening to transfer legacy product ownership and pager duty effectively motivates the final holdout clients.
1. **Celebrating milestones to build migration champions** (26:47) — Highlighting successful segments builds trust and creates champions for subsequent rollout phases.
1. **Recognizing the social realities of technical migrations** (27:43) — Why clear communication and stakeholder management often outweigh purely technical execution challenges.
1. **Prioritizing difficult migration segments using objective scoring** (28:47) — Using numeric scoring based on complexity or blockers helps schedule the rollout of deeply complex migration phases.

## Related Moments

- [Executing massive cloud network migrations while maintaining live systems](https://www.wearedevelopers.com/videos/100128-the-golden-age-of-email-owning-the-inbox-in-the-age-of-ai) (from "The Golden Age of Email: Owning the Inbox in the Age of AI")
- [Addressing runtime migration specifics and future open source framework ambitions](https://www.wearedevelopers.com/videos/100311-swapping-a-data-warehouse-at-runtime-zero-downtime-migration-without-changing-a-single-client) (from "Swapping a Data Warehouse at Runtime: Zero-Downtime Migration Without Changing a Single Client")
- [Overcoming the perceived expense of major system migrations](https://www.wearedevelopers.com/videos/218-seven-myths-three-reasons-one-goal) (from "Seven Myths, Three Reasons, One Goal")
- [Acknowledging the inevitability of software evolution and technology migrations](https://www.wearedevelopers.com/videos/100006-you-will-migrate-eventually-a-developer-approach-to-technology-adoption) (from "You Will Migrate Eventually: A developer approach to technology adoption")
- [Transforming legacy platforms to cloud native patterns](https://www.wearedevelopers.com/videos/463-let-developers-develop-again) (from "Let developers develop again")
- [Summary of migration steps and building team consensus](https://www.wearedevelopers.com/videos/646-4-steps-from-javascript-to-typescript) (from "4 Steps from JavaScript to TypeScript")

## Related Articles

- [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift)
- [MLops – Deploying, Maintaining And Evolving Machine Learning Models in Production](https://www.wearedevelopers.com/magazine/115-mlops-deploying-maintaining-and-evolving-machine-learning-models-in-production)
- [Dev Digest 138 - Are you secure about this?](https://www.wearedevelopers.com/magazine/486-dev-digest-138-are-you-secure-about-this)
- [MLOps – What’s the deal behind it?](https://www.wearedevelopers.com/magazine/125-mlops-what-s-the-deal-behind-it)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [SENIOR SOFTWARE ENGINEER - DATA MIGRATION & INTEGRATION](https://www.wearedevelopers.com/jobs/ext/930187-senior-software-engineer-data-migration-integration) at **Wilken GmbH**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub**
- [Staff Solutions Architect, Contract LifeCycle Management](https://www.wearedevelopers.com/jobs/ext/541145-staff-solutions-architect-contract-lifecycle-management) at **Twilio**
- [Java Softwareentwickler Migrationsprojekte (m/w/d)](https://www.wearedevelopers.com/jobs/48138-java-softwareentwickler-migrationsprojekte-m-w-d) at **Finanz Informatik**