Migrating from Zipwhip to Plivo is a seamless and painless process. The two companies’ API structures, implementation mechanisms, SMS message processing, and MMS message processing are similar. We wrote this technical comparison between Zipwhip and Plivo APIs so that you can scope the changes for a seamless migration.
Most of the APIs and features that are available on Zipwhip are also available on Plivo, and the steps involved are almost identical. This table gives a side-by-side comparison of the two companies’ features and APIs. An added advantage with Plivo is that not only can you code using the old familiar API method, you can also implement your use cases using PHLO (Plivo High Level Objects), a visual workflow builder that lets you create workflows by dragging and dropping components onto a canvas — no coding required.
Features and APIs | Zipwhip | Plivo | Similarities | Implementation Interface |
SMS API: Send SMS messages | ✅ | ✅ | Request and response variables’ structure |
API PHLO |
MMS API: Send MMS messages | ✅ | ✅ | Request and response variables’ structure |
API PHLO |
10DLC: 10-digit long code (10DLC) phone numbers | ✅ | ✅ | Registration process and usage | Console |
Managed number pool for US/CA Messaging | NA | Powerpack | Feature parity |
API Console |
Phone number management | ✅ | ✅ | Feature parity |
API Console |
HTTP callbacks | ✅ | ✅ | Feature parity |
API XML PHLO |
Start by signing up for a free trial account that you can use to experiment with and learn about our services. The free trial account comes with free credits, and you can add more as you go along. You can also add a phone number to your account to start testing the full range of our voice and SMS features. A page in our support portal walks you through the signup process.
You can also port your numbers from Zipwhip to Plivo, as we explain in this guide.
You can migrate your existing application from Zipwhip to Plivo by refactoring the code, or you can try our intuitive visual workflow builder PHLO. To continue working with the APIs, use one of the quickstart guides to set up a development environment for your preferred language. Plivo offers server SDKs in seven languages: PHP, Node.js, .NET, Java, Python, Ruby, and Go. For another alternative that lets you evaluate Plivo’s SMS APIs and their request and response structure, use our Postman collections.
Let’s take a look at the process of refactoring the code to migrate your app from Zipwhip to Plivo to set up a simple cURL application to send an SMS message by changing just a few lines of code.
Zipwhip | Plivo |
|
|
Alternatively, you can implement the same functionality using one of our PHLO templates. For example, if you want to send an SMS message, your PHLO would look like this.
Let’s take a look at the process of refactoring the code to migrate another application from Zipwhip to Plivo — a simple cURL application to send an MMS message — by changing just a few lines of code.
Zipwhip | Plivo |
|
|
Alternatively, you can implement the same functionality using one of our PHLO templates. For example, if you want to send an MMS message, your PHLO would look like this.
You can migrate applications for other use cases too:
If you want to continue using your phone numbers from Zipwhip, you can port the numbers to Plivo painlessly without having any downtime on your services for your customers. Our number porting guide shows you how to initiate the process.
You can buy new phone numbers on the Plivo platform for your migrated applications as well. Plivo provides a self-serve console to buy new numbers and to manage them. You can also use the Phone Numbers API for number management. You can check this guide to learn more.