From what I can see at
it’s impossible for a 3rd-party service, including Travis, to know when a repository is moved because there’s no notification for that.
Neither is it possible to automatically set up integration at the repo’s new location because Travis needs a brand new permission grant for the new organization to be able to do anything on its behalf.
So, set up the integration anew as per below.
It’s possible that this won’t be needed if Github was smart enough to update webhooks appropriately when moving – then you will see that the integration is already enabled after registering at Travis with the new organization. (Still, it won’t hurt to reset everything just in case.)