This document describes how to migrate to Iterable from another push notification provider.
In this article
Migrating push notifications to iterable
To migrate from a different push notification provider to Iterable, install Iterable's mobile SDKs in your apps and send the historical device token to Iterable.
NOTE
It's possible to configure your app to receive push notifications simultaneously from Iterable and another provider. Push notifications are handled by frameworks provided by Apple and Google, and multiple providers can exist in the same app at the same time.
Installing Iterable's mobile SDKs
For more information, read:
Configuring your apps to support push notifications from Iterable
For more information, read:
Transfering tokens
To transfer user device tokens from a previous provider to Iterable, use the
POST /api/users/registerDeviceToken
API.
NOTES
- Transferring tokens is not mandatory. You can wait until your users update to a version of your app that includes the Iterable SDK.
- To create an Iterable profile for a new user, use the
POST /api/users/updateAPI.
Migrating channel preferences
To migrate push preferences from a historical push provider to Iterable, use
the POST /api/users/bulkUpdateSubscriptions
API.
Slow migration
To slowly migrate from another push notification provider to Iterable, add Iterable's mobile SDKs to your apps and slowly transition your campaigns to Iterable. Use Iterable's segmentation tool to see which users have updated to the newest version of your app.
Selectively targeting users
Iterable can also selectively target users based on which version of the app they're running. Once a sufficient number of your users have updated, you can remove the old push notification provider's SDK.