SMSGlobal migration

Move from SMSGlobal to MonsterSMS.ai and keep group data intact

This page is tuned for SMSGlobal migrations. It pulls contacts group by group, preserves opt-outs where exposed, and prepares the payload for MonsterSMS.ai import.

Preview before import Shared backend in App Engine Preloaded for SMSGlobal

What this SMSGlobal page is set up for

Group-based contacts
Opt-out preservation
Signed MAC auth on the backend

Provider pages

Each migration source gets its own landing page

This page is focused on SMSGlobal, but the same migration engine also powers the rest of the supported provider set.

ClickSend → MonsterSMS.ai Textmagic → MonsterSMS.ai Cellcast → MonsterSMS.ai Podium → MonsterSMS.ai MessageMedia → MonsterSMS.ai BurstSMS → MonsterSMS.ai SMSGlobal → MonsterSMS.ai

Why this page exists

A cleaner migration page for SMSGlobal

People searching for a SMSGlobal migration tool should land on a page that actually speaks to that move, not a generic import screen.

Compliance-aware

Opt-outs matter. This flow keeps them visible during preview and import.

Group recreation

SMSGlobal groups can be recreated as MonsterSMS.ai lists.

Backend signing

The HMAC signing happens on the server side, not in the browser.

Use the tool

Run the SMSGlobal migration flow

This form is already preloaded for SMSGlobal. Run a preview first, then import into MonsterSMS.ai once the sample looks right.

Source platform

Enter the SMSGlobal credentials, check the preview, then add your MonsterSMS.ai API key to run the import.

Current provider

This page is tuned for SMSGlobal.

Privacy note: The username and API keys you enter here are used only to run the live preview or import. They are not saved.

MonsterSMS.ai API key

Used only for the MonsterSMS.ai import call. It is not required for preview.

Create matching lists in MonsterSMS.ai and attach imported contacts to them. Import templates where the source API exposes them. Unsupported providers will skip this automatically.

Result

You’ll see counts and warnings before you import anything.

Ready. Pick a provider and run a preview.

0Contacts

0Lists

0Templates

Questions people actually ask

SMSGlobal migration FAQ

Short answers, no fluff.

What does the SMSGlobal page import?

Group contacts and opt-outs, with list recreation where possible.

Do I need to generate signed requests myself?

No. The backend handles MAC signing.

What if some contacts are not in groups?

Those may still need a manual CSV path after the API migration pass.