Skip to main content
You cannot port (transfer) a phone number from Plivo to Vobiz. There is no number-porting process. Your Plivo numbers stay on Plivo. To run on Vobiz, buy new Vobiz numbers and update your call flows and caller IDs to use them.
When you migrate from Plivo, treat phone numbers as a fresh provision on Vobiz, not a transfer. Buy the numbers you need from Vobiz inventory, route them, cut your traffic over, and then release the old numbers on Plivo once you no longer need them.

​
Buy new Vobiz numbers

Buying a number on Vobiz is a two-step flow: browse inventory, then purchase by E.164. For the full walkthrough (console and API, fees, India series, and routing), see Buy a phone number.

​
1. Browse inventory

cURL - browse inventory
Inspect setup_fee and monthly_fee (in the listed currency) on each result before you buy - these amounts are debited at purchase. See List Inventory Numbers.

​
2. Purchase by E.164

Python - purchase from inventory
After purchase the number is owned by your account but not yet routed. Attach it to an application, assign it to a trunk, or hand it to a sub-account to start receiving calls. See Purchase from Inventory for the response shape and error cases.
India numbers follow series and compliance rules - 140 for promotional, 160 for transactional (BFSI), 1800 for toll-free, and so on. Pick the right series and review India compliance before you purchase.
Because the numbers change, plan the switch so callers are never dropped:
1

Buy Vobiz numbers and route them

Provision new Vobiz numbers and wire them to your applications/trunks.
2

Update where your number is published

Point your app, CRM, website, IVR prompts, and outbound caller ID at the new Vobiz numbers.
3

Run both in parallel

Keep the Plivo numbers live during cutover so anyone using the old digits still connects while you validate Vobiz.
4

Cut over, then decommission Plivo

Once traffic is flowing on Vobiz, release the Plivo numbers on Plivo’s side.

​
Watch the 15-day DID cool-off

When you move a DID back to the parent pool by unassigning it from a sub-account, Vobiz enforces a 15-day cool-off on recently active numbers. If the DID had a call within the last 15 days, the unassignment is rejected with 409 did_cool_off_in_effect (the response includes cool_off_until and cool_off_remaining_seconds). A DID that was never used moves back immediately. Admins can override with ?force=true, which writes an audit record.

​
Next steps

Buy a phone number

The complete step-by-step guide to provisioning a Vobiz number.

Cutover checklist

The full step-by-step plan for switching production traffic to Vobiz.