Pitfalls of updating default bubble url to custom domain for a live application

I have an production app on bubble. It has few external wf api, integration with razorpay.
Is there a checklist that i can head to to avoid impact of this migration.
eg. If you change your URL, your encapsulated app using zerocode stops working and you have to request the team to update the URL.

I know that a lot if these urls get auto redirected from bubbbleapps.io url to the custom domain url. I would still be publishing the new url to all these stakeholders.

I am also compiling a list of these to my knowledge. If any of you has a use case that i have missed, please add that in the comments and maybe this can serve as a documentation of the same.

  1. Any team that is using bubble’s WF API’s endpoint to interact with users. (For newbies: If you use backend workflows API and enable it for public access, you get to access that application using a URL with you application’s domain name in it.)
  2. If you use are plugin or third party application that needs you to provide a callback URL, that callback url needs to be updated to the new url. (a callback url is usually url of one of your bubble application’s page)