Migrate from Tropo to Nexmo

In case you have not seen it, please review our migration program post, which includes 10% off your monthly usage fee for the first three months

As of October 2018, Tropo have started a phased shutdown of their services. This means that you're looking for another communications provider the SMS and Voice functionality within your applications. This guide will help you with that migration.


Get Started

Get started with the Nexmo platform in four steps:

  1. Register for a Nexmo account

Sign up for a Nexmo account. Once you've signed up you'll receive €2 free credit which is enough to get started. We're offering a migration package to Tropo customers, including 10% off your monthly usage fee for the first three months and free migration support from our renowned customer support team. See our migration blog post for more information

  1. Purchase a phone number

Head over to the Nexmo dashboard and purchase a virtual number to use for your application. You may not need it if you're in a country that supports alpha senders - search for your destination country on the knowledge base for more information.

If you've already got a US or Canadian number and would like to keep it, you can port the number to Nexmo using the Nexmo dashboard. To check the feasibility of porting numbers outside of US and Canada, please contact api.support@vonage.com

  1. Install the Nexmo Client Library

Nexmo provides client libraries in six different languages! Whether you write Javascript, PHP, Python, Java, .NET or Ruby, we've got you covered. Head over to the tools page to learn more about what's available.

  1. Develop your application

Finally, it's time to build your application! We've put together some examples for common tasks involving SMS and voice calls based on the Tropo documentation.


FAQ

Nexmo vs Tropo - Main differences

Tropo Nexmo

The Tropo scripting API allows you to store code inside a Tropo application and trigger that code via a web request

Code runs on your own server, talking directly to the Nexmo platform

Any metadata available is stored in the session metadata

Nexmo sends metadata as GET parameters to your webhook endpoint. Common parameters include to, msisdn and text


Do you have a question?

We're always here to help. Check out our support FAQs, contact our super helpful support team or get in touch on Stack Overflow.
Your data will be treated in accordance with our Privacy Policy, which sets out the rights you have in respect of your data.