Skip to main content

Migrating SMPP traffic to Bandwidth's next-generation messaging platform

Updated over 2 weeks ago

This article applies only to customers who have received an official communication from Bandwidth regarding their Short Message Peer-to-Peer (SMPP) migration. If you haven't received such communication from Bandwidth, no action is needed.

Note: As of September 3, 2025, Bandwidth has resolved a previous issue for migrating customers who are only able to connect to a single SMSC (namely, customers leveraging Metaswitch as their SMPP client). These customers are free to resume migrations and are expected to complete them by the September 30 deadline mentioned below. Customers can continue to leverage the SMPP Integration guide while choosing one of the two US regions to integrate with.

Bandwidth has built a next-generation messaging platform to replace our existing legacy Short Message Service Center (SMSC) connections. To migrate your SMPP traffic to our new platform, please complete the following steps by September 30, 2025:

  1. Once you receive the migration communication from Bandwidth, submit a ticket to begin the process.

  2. Bandwidth will send you the SMPP integration guide containing the details on how to connect to our new platform and configure your account accordingly. At this stage, you may continue to connect and send via the legacy SMSC. Bandwidth will first attempt to leverage available connections to the new platform for any inbound/MO traffic. If there are no available connections on the new platform, we will attempt a fallback to any legacy connections you have. All delivery receipts will be returned on the connection where the original message was sent.

  3. Optional: Establish connectivity from a non-production environment for testing purposes before moving your live connections and traffic. If this is not feasible, you may continue to step 4.

  4. Migrate your production connections as you see fit and update your ticket to inform Bandwidth once you're done. While no disruption is expected during migration, we recommend that this happen during off-peak hours to mitigate risk. Once complete, you should have no connections or traffic remaining on the legacy SMSC.

  5. Bandwidth will mark your migration as “complete”. At this stage, we will no longer attempt to fall back to our legacy platform.

smpp-traffic-migation-steps.png
Did this answer your question?