If you notice any of these things during planning, be alert.

Discovery is revealing things that were never in scope, not because scope was wrong but because the initial assessment of the environment wasn’t thorough. If dependencies are still being discovered two weeks prior to cutover, then the plan may not be ready.

The rollback strategy is vague – phrases like “we will restore from backups if needed” are not accompanied by a timeline or a tested procedure, which means that nobody has really thought about what rollback under pressure looks like.
Stakeholder communication is one-way. For example, if IT sends updates but doesn’t get meaningful input from business, this gap will be apparent during or after a cutover.

None of these guarantees failure. All of them should be addressed before the cutover window is opened.

#Migration #IT #CloudMigration