Migrating existing resources
If you're moving to Infobip from another messaging provider, this page will guide you through what to expect during the migration process.
This page is a work in progress. Detailed migration guides for specific providers and channels are coming soon. In the meantime, contact your account manager or Infobip Support for migration assistance.
What migration involves
Moving from another provider to Infobip typically means:
- Remapping API calls — Your existing API requests will need to be updated to match Infobip's endpoint paths, authentication methods, and request/response schemas.
- Migrating sender IDs and numbers — Phone numbers, short codes, and sender IDs registered with your current provider may need to be ported or re-registered on the Infobip platform.
- Reconfiguring webhooks — Delivery report callbacks and inbound message webhooks will need to point to your updated endpoints using Infobip's webhook format.
- Testing in a sandbox environment — Infobip provides a test environment to validate your integration before going live.
Get in touch
Migration timelines and complexity vary depending on your current provider, the channels you use, and your integration's scale. Reach out to your account manager or Infobip Support to plan your migration with:
- Your current provider and the channels you use (SMS, WhatsApp, Voice, etc.)
- Your approximate monthly message volume
- Your target go-live date