Things to keep in mind for migration to Cloud API

HOW TO REQUEST MIGRATION TO CLOUD API?

Partners / Customers can reach out to their local CSMs to initiate this activity for their on-prem apps.

If you do not, Gupshup will be conducting this activity and will ensure that the migration activity runs smoothly.

THINGS TO KEEP IN MIND

There should be certain things you must keep in mind for migration to Cloud API - 

1. Disable / Banned 'on-premise apps : If a Phone number was disabled / banned while on on-premises, the new registration for the same will FAIL on Cloud API.
   
   
2. Default storage region : If a phone number was hosted in India (on-premise), it will be moved to Cloud API - USA region by default. And if a phone number was hosted in Germany (on-premise), it will be moved to Cloud API - EU region by default during migration. In all cases, Gupshup data (such as wallet etc) will remain in India only.
   
   
3. Prepare for /sm endpoints - End of Life : While it may not directly impact migration to Cloud API at the moment, we want partners and businesses to prepare for the /sm endpoints end of life. Read more here
   
   
4. Media Management :
   Outgoing media : Media URL can be continued to be used after migration to Cloud API. For partners using media ID, note that existing media IDs will become invalid once the phone number is moved to Cloud API. Watch this space for further updates on how to manage this. Gupshup team will reach out to you for next steps. Please notify your CSM if you are using Media ID APIs at the earliest
   
   [MIGHT IMPACT] Incoming media : Incoming media received before migration will not be available post-migration.
   
   
5. Number mismatch : If you have any exceptional cases such as number mismatch issues of Brazil and Mexico or any other reason to be taken special care during migration, please notify your local CSM immediately. Watch this space for further updates on how to manage this. Also Gupshup team will reach out to you for next steps. 
   
   

   If you have any exceptional concerns for moving to Cloud API or need special care during migration, please notify us immediately on aig.product@gupshup.io  within 24 hours of receiving a migration notice emailer from Gupshup.

   If any issue is faced after migration, please note that revert back on On-premise will not be possible as it has been sunset by Meta.

    

    

   NEW WABA ONBOARDING ON CLOUD API: 
   Now that On-premise registration has been ended by Meta, please note that even if apps, where 'on-premise' hosting option was selected in the past before July 1, but the 'go live' process was left incomplete, or if they are still able to select 'on-premise' option for a new app, those registrations will fail if done on or after July 01, 2024. If you wish to go-live for the incomplete numbers, you will need to delete the app and go live through a fresh app. If you are not able to see the 'delete' option, please reach out to partner.support@gupshup.io
   Similarly, if a WABA was disable/banned while on on-premises, the new registration for the same will happen on Cloud API only. Please contact support team to help you with the same case.