<p>As a new engineer on a team - how to contribute to system modernization by migrating legacy apps without creating a blip on the customer’s radar?</p>
<p>The answer is use-case dependent and very contextual.</p>
<p>But here are a few generic tips.</p>
<h2 id="heading-perform-the-migration-in-stages">Perform the migration in stages.</h2>
<p>Rather than attempting to migrate all of the legacy applications at once, break the process down into smaller chunks.</p>
<p>One service at a time?</p>
<p>Benefits - every stage can be tested thoroughly. Rollback is easier.</p>
<h2 id="heading-blue-green-deployment">Blue-Green deployment</h2>
<p>If this is already not a practice, recommend and establish one.</p>
<p>This involves creating a copy of the legacy app and its associated infra, and then directing traffic to the new version once it is ready.</p>
<p>Benefit - zero downtime</p>
<h2 id="heading-transparent-communication-with-stakeholderscustomer">Transparent communication with stakeholders/customer</h2>
<p>Provide regular updates, build and ensure that your customers feel confident in your ability to handle the migration smoothly</p>
<h2 id="heading-finally-test-like-your-life-depends-on-it">Finally - test like your life depends on it</h2>
<p>I learn and share content to build great Digital Experiences for our stakeholders.</p>
<p>If you liked my content, do kindly like and share it with other students in your network. And don't forget to subscribe to the newsletter to NEVER miss an article. I also tweet <a target="_blank" href="https://twitter.com/zahiruddin_t"><strong>here</strong></a>.</p>


As a new engineer on a team - how to contribute to system modernization by migrating legacy apps without creating a blip on the customer’s radar?

The answer is use-case dependent and very contextual.

But here are a few generic tips.

## Perform the migration in stages.

Rather than attempting to migrate all of the legacy applications at once, break the process down into smaller chunks.

One service at a time?

Benefits - every stage can be tested thoroughly. Rollback is easier.

## Blue-Green deployment

If this is already not a practice, recommend and establish one.

This involves creating a copy of the legacy app and its associated infra, and then directing traffic to the new version once it is ready.

Benefit - zero downtime

## Transparent communication with stakeholders/customer

Provide regular updates, build and ensure that your customers feel confident in your ability to handle the migration smoothly

## Finally - test like your life depends on it

I learn and share content to build great Digital Experiences for our stakeholders.

If you liked my content, do kindly like and share it with other students in your network. And don't forget to subscribe to the newsletter to NEVER miss an article. I also tweet [**here**](https://twitter.com/zahiruddin_t).

As a new engineer on a team - how to contribute to system modernization by migrating legacy apps without creating a blip on the customer’s radar?

How to migrate legacy apps without impacting customers

How to migrate legacy apps without creating a blip on the customer’s radar?

I am Zahiruddin Tavargere (Zahere). A firm believer in social learning, I owe my dev career to all the tech content creators I have learned from - this is my contribution back to the community.
