Migrate a WhatsApp Business On-Premises API deployment to the Cloud API before final shutdown
domain: developers.facebook.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the full timeline at developers.facebook.com/docs/whatsapp/on-premises/sunset: after v2.53, On-Premises API got bug/security fixes only (new features Cloud-API-only) starting January 9, 2024
Note new number registrations on On-Premises stopped being allowed as of July 1, 2024 — attempting to register a new number on-prem after that date returns error code 1005
Plan full migration before October 23, 2025, when the final On-Premises version (v2.63) expired entirely
Confirm no numbers remain registered to an On-Premises deployment past October 23, 2025, since messages to/from those numbers simply fail to deliver with no grace period
Migrate to the Cloud API (available since 2022) using Meta's official Cloud API migration documentation rather than treating this as a simple endpoint swap
Known gotchas
There is no grace period after October 23, 2025 — messages just stop delivering, they don't queue or error gracefully
The distinct "sunset" doc page is separate from the general On-Premises API docs page and easy to miss when researching current status
Anyone still on On-Premises has effectively been on a winding-down track since 2022 when Cloud API launched — treat this as long overdue, not a new surprise
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?