How to migrate legacy apps without creating a blip on the customer’s radar?
1 min read
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.
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.