I'm facing the same issue. It seems that there is no easy way out of this. The only clean way is to create a custom domain, associate it with the new routes and the old routes, and communicate it out to clients for use instead of using the migrated domain.