Overview
Switching messaging providers has a reputation for being painful — rewritten integrations, lost sender IDs, a scary big-bang cutover and a support desk that answers in ticket numbers. BroadNet is built to make it the opposite. Because BroadNet speaks the same protocols your current provider does, moving over is mostly a change of endpoint and credentials, run in parallel with your existing route so nothing goes dark. A dedicated engineer plans the cutover with you, watches the delivery receipts, and only helps you switch off the old route once the new one is proven. This page walks through exactly how it works.
Why teams switch to BroadNet
Most teams do not switch provider for one reason — they switch because several things quietly went wrong at once: delivery drifted, a route turned grey, pricing stopped making sense, or support went silent when it mattered. Here is what you move onto.
Reach 200+ countries over 1,000+ direct operator connections. Fewer hops between you and the handset means higher delivery rates, faster first-attempt delivery and honest, real-time DLRs — not a grey route reselling someone else's reselling.
A carrier operator, not just an app layer. SMS and SS7 firewalling, sender-ID protection and anti-fraud controls sit in the network path, backed by ISO 27001, ISO 9001, ISO 22301 and SOC 2 Type II. Your traffic runs on infrastructure built to telecom standards.
Clear per-destination pricing with no mystery surcharges layered on at cutover. You see the route and the rate, so finance can forecast and engineering can trust the numbers you migrate against.
Deep coverage and long-standing operator relationships across the Middle East, North Africa and beyond, with hands-on help navigating sender-ID registration and local regulatory requirements that trip up global-only providers.
A named migration engineer who knows your integration — reachable during the parallel-run window and the cutover itself. When something looks off at 2am, you talk to a telecom engineer, not a bot.
Two decades operating messaging infrastructure for enterprises, banks and carriers. Switching to BroadNet means moving onto a provider that has been running production A2P traffic longer than most of the market has existed.
Migration in 4 steps
The whole migration is a parallel run: your current provider keeps carrying live traffic while BroadNet proves itself next to it, and only takes over when you decide, percentage by percentage. Nothing is a leap of faith.
- 1Request test access & map your payloadsDay 0 — prepare
Request test access — we reply within one business day. Your migration engineer maps your current send payloads, sender IDs and DLR webhooks onto BroadNet's equivalents — usually a field-for-field match. Integration typically takes 2–5 business days.
- 2Point a test sender at BroadNetParallel run
Send live test traffic through BroadNet in parallel with your existing provider. Compare delivery, latency and receipts side by side on real destinations before a single production message moves.
- 3Cut over traffic graduallyGradual cutover
Shift production volume in stages — 5%, then 25%, then the rest — watching live DLR monitoring at each step. If a metric drifts, you roll the percentage straight back. No big-bang risk.
- 4Decommission the old routeDone
Once 100% of traffic runs clean on BroadNet and receipts reconcile, retire the old integration. Your engineer confirms sender IDs, throughput and DLRs are fully settled before you close the account.
Drop-in APIs — you keep your integration
BroadNet speaks the protocols you already build on, so migrating is a swap, not a rewrite:
- REST HTTP API — a simple JSON send endpoint for SMS, OTP, WhatsApp and more, ideal for application-level integrations.
- SMPP v3.4 binds — carrier-grade transceiver binds over TLS for sustained high throughput. If you connect over SMPP today, point your existing bind at BroadNet with new credentials. See the SMPP protocol guide.
- Webhooks & DLRs — real-time delivery receipts posted to your endpoint in a familiar shape, so your reporting and retry logic carry straight over.
A send over the REST API looks like this — one JSON POST with a Bearer token; map your current fields onto senderId, destinationNumber, message and messageType:
curl -X POST https://api.broadnet.me/sms/sendSms \
-H "Authorization: Bearer $BROADNET_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"senderId": "BroadNet",
"destinationNumber": "447700900123",
"message": "Your code is 8123",
"messageType": "TEXT"
}'
# 200 OK — the response body is the message ID, e.g. 2603121407537573731Read the full reference and language examples in the docs and the Developer Hub. Your migration engineer maps each field from your current provider before you send a single test message.
What you can consolidate onto BroadNet
Switching is a chance to collapse a sprawl of vendors into one account, one integration and one bill. Every channel below runs on the same routes and the same credentials — bring them over together, or one at a time.
Move your messaging AI and conversational agents over fast. BroadNet AI wires intelligent, multi-channel automation onto the same routes your alerts and OTPs already run on.
Wangiri-style missed-call OTP: verify a user with an incoming call they never answer, no SMS body required. Faster and cheaper than an SMS PIN on supported numbers.
Run OTP and verification over WhatsApp with official Business API access — a rich, high-trust channel to sit alongside SMS in the same account.
b1.lc is BroadNet's free branded link shortener built for SMS and campaigns — short, trackable, on-brand links that keep messages inside a single segment. Migrate your campaign links with your traffic.
Application-to-person SMS at carrier scale over SMPP or REST — the core of most migrations and the backbone the rest of the channels build on.
Upgrade to rich, branded, verified-sender RCS where carriers support it, with graceful SMS fallback — no second vendor required.
One-time-passcode delivery and verification with smart routing across SMS, voice and WhatsApp for the best delivery on every destination.
Orchestrate SMS, WhatsApp, RCS and voice from one API with channel fallback — consolidate the stack you were juggling across several providers.
Migration support & SLAs
A switch is only low-risk if someone who understands telecom is with you through it. Every migration comes with hands-on engineering support and safety rails.
A named migration engineer who maps your payloads, plans the cutover and is reachable throughout — not a rotating queue.
Both routes live at once for as long as you need, with side-by-side delivery and DLR monitoring before any production traffic moves.
Shift traffic back to the old route instantly at any percentage. A bad metric is a dial you turn, not an incident you report.
Once you are live, the same rigour continues: uptime commitments, monitoring and escalation paths are set out in the support & SLA terms, so the reliability you migrated for is contractual, not aspirational.
Frequently asked questions
How long does migrating to BroadNet take?
For a standard SMS or OTP integration, most teams are running parallel test traffic within a day of getting their API credentials and complete a staged cutover in one to two weeks. The timeline is driven by how gradually you want to shift production volume and any sender-ID registration lead times, not by the integration work itself — the API shape is close enough that code changes are usually minimal.
Will I have downtime during the switch?
No. Migration is designed as a parallel run: BroadNet accepts your traffic alongside your existing provider, so both routes are live at once. You shift production volume gradually while watching live delivery receipts, and you can roll the percentage back instantly at any point. Your old route only gets decommissioned after 100% of traffic runs clean on BroadNet.
Do I have to change my code?
Usually very little. BroadNet speaks the protocols you already use — a REST HTTP API and SMPP v3.4 binds — so in most cases you change an endpoint, credentials and a few field names rather than rewriting your integration. Your migration engineer maps your current send payloads and DLR webhooks to BroadNet's equivalents up front so the change is a swap, not a rebuild.
Can I keep my sender IDs?
In most countries, yes. Alphanumeric sender IDs and short codes are generally portable, subject to each operator's and regulator's registration rules. Your migration engineer handles or guides sender-ID registration on BroadNet's routes before cutover so your recipients keep seeing the same trusted sender throughout the switch.
Do you support SMPP?
Yes. BroadNet operates a carrier-grade SMSC gateway that accepts SMPP v3.4 binds over TLS, with transceiver binds, async windowing for high TPS, full delivery receipts, Unicode and concatenation. If your current provider connects over SMPP, you can point your existing bind at BroadNet with new credentials — see the SMPP guide for the full protocol reference.
What about number and short-link migration with b1.lc?
Campaign short links can move with your traffic. b1.lc is BroadNet's free branded link shortener built for SMS and campaigns, so you can recreate your branded links on b1.lc and swap them into your message templates as you cut over. Your migration engineer helps line up link migration alongside sender IDs so nothing in a live template breaks mid-switch.
Can I consolidate multiple providers onto BroadNet?
That is one of the most common reasons teams switch. SMS, OTP and verify, WhatsApp Business API, RCS, Flash Call voice OTP, omnichannel orchestration and link shortening all live in one account on BroadNet, so you can retire several vendors, one integration and one bill instead of many.
Is there a cost to migrate?
There is no charge for migration support or the parallel-run window — a dedicated migration engineer, payload mapping and the staged cutover come with your account. You only pay for the messages you send, at transparent per-destination rates you can review before you move any production traffic.