This is not uncommon. Two things come to mind that might help: 1) Decide if you really care if this migration is on hold for several months. Your stuff presumab

This is not uncommon. Two things come to mind that might help: 1) Decide if you really care if this migration is on hold for several months. Your stuff presumably works fine still, right? If so, why do you care that the migration is delayed? Really take time to think it through. In the meantime, just report the delay back to whoever told you to do the migration and, if they have a problem with it, they can go fight battles for you while you do something else. 2) Recognize that $LARGE_CORP values != startup values. This can be really hard - you likely came from an environment in which getting things done quickly, efficiently, and sometimes really creatively, was highly valued, almost above all else. Those are good things, but now you are in an environment in which things like stability and predictability are possibly even more important, and a plodding, "inefficient" bureaucracy can actually work in favor of those values. I found the above helpful while I endured a commitment to stay for a certain amount of time after the acquisition, but ultimately I missed the startup environment and returned as soon as I could. :)