Hosting type Change

This document describes how to change hosting from On-premise to Cloud API.

On October 23, 2025, the final supported version of the On-Premise API client expired.

Refer to Meta's official On-Premise sunset document for more information.

Note: When you migrate to Cloud API it is not possible to migrate back to On-Premise.

Preparation Checklist

• Number Registration and Hosting

  • Confirm that the phone number is registered and using On-premise hosting. If the number is unregistered, re-register it before initiating the hosting type change.

  • The hosting type change does not require re-registration (OTP), but if triggered on a disconnected number, the process will fail

• Access to 360dialog Hub

  • The migration is managed through the 360Dialog Hub.

  • Login to the 360Dialog Hub and to ensure you can trigger the migration.

• API Key Readiness

  • In Cloud, only the most recent API Key will remain valid.

• Downtime Preparation

  • The migration process can take between 5 and 60 minutes. Plan for downtime during this period.

• No reversal

  • When you migrate to Cloud API it is not possible to migrate back to On-Premise.

How to migrate to Cloud API

1

Locate the phone number you want to migrate and navigate to > Manage WhatsApp Business Account

2

Scroll down to Hosting Platform Type

3

Launch the Cloud migration assistant > Continue

4

Once the migration is in progress, you can either leave the pop-up open or close it. A notification will appear in your Notification Center once the migration is completed.

5

You will receive a confirmation message once the number has been successfully migrated to Cloud API.

6

You can verify that the number is on Cloud API by checking the Hosting Platform Type in the Details page. It will display as Cloud API hosted by Meta.

Hosting Platform Type after Cloud API migration

Post-Migration

After the migration:

• Ensure you are calling the correct endpoint: https://waba-v2.360dialog.io/messages

• Use the most recently generated API Key, as old keys will not work with Cloud API. We recommend that you generate a new API Key after migration. See Cloud API Authorization Errors for more information.

• See our specific documentation for setting up the phone number webhook.