How a migration works
Every move has the same four parts.
- Scan. In the console, under Numbers, the importer reads your current account with credentials you paste. The requests are read-only, and the credentials are used once and not stored.
- Review. You get a plan: which numbers will be ported, which sender pools will be recreated, and which webhook URLs were found. Nothing is created until you confirm, and you can deselect any line.
- Port. Confirming files a port request for each number. Porting is a carrier process that takes days, tracked in the console; your current service keeps working until each port completes.
- Cut over. Change the send call, replace the webhook handler with one that verifies SimpleSMS events, and load your existing opt-outs.
What is the same in every guide
- Base URL
https://api.joinsimplesms.com/v1, one bearer API key, JSON in and out. - Test keys are free and instant, and every endpoint works in the sandbox, webhooks included. A migration can be built and verified before a live message is sent.
- Live sending needs a short live-access review and an approved A2P 10DLC registration for US local numbers.
- SimpleSMS is SMS only, in the United States and Canada.
If your provider is not listed
Port numbers with Number porting (one at a time or from a CSV), then map your calls by hand: the API is small, and the API reference documents every endpoint. Start with the quickstart and the error reference.
Moving phone verification? See Migrate from Twilio Verify.