Avoidable Mistake #2

Background

Migrating application capabilities might seem compartmentalized by product. This is a misconception. Trying to isolate and migrate a vendor product is not recommended.

Mistake #2 - Migrating By Vendor Product

You have cloned and spun up a shiny, new replacement for an existing vendor product. How do you go about migrating? Unless you have taken a rigorous and disciplined approach, you are most assured to bump up against everything you didn’t know could go wrong. There is another way,

Your method will yield a more organized and managed rollout when you organize around the seams. By this, we mean that your intended replacement code should start small and compartmentalized. Then spin up a clone of your current environment in your future state environment. While the legacy system is live, maintain a realtime clone. Identify your integration points and deploy a test version of your future software integrated into the clone and then sit back and see what happens. You will learn a lot that will inform the future of your migration.