It’s a term used for when IT operations teams want to keep the status quo design of their environments when upgrading or modernizing their infrastructure, instead of fixing and securing things while they’re at it. The common excuse is that they will fix issues once migration/upgrade is complete, either because they’re on a tight timeline to do it, they’re afraid of breaking things, or just plain lazy. They will say it’s temporary until things have settled down. And we all know there’s nothing more permanent than a temporary implementation. The result is the same issues and problems exist, just on new infrastructure.
Three words that kill modernization: Lift and shift.
What does that mean?
It’s a term used for when IT operations teams want to keep the status quo design of their environments when upgrading or modernizing their infrastructure, instead of fixing and securing things while they’re at it. The common excuse is that they will fix issues once migration/upgrade is complete, either because they’re on a tight timeline to do it, they’re afraid of breaking things, or just plain lazy. They will say it’s temporary until things have settled down. And we all know there’s nothing more permanent than a temporary implementation. The result is the same issues and problems exist, just on new infrastructure.