Migrating from another push provider

If you are integrating the Xtremepush SDKs into your apps to replace another push provider, then it is important to consider how the transition between the two push providers is performed. The following describes the best practice on how to handle moving from another push provider to Xtremepush.

No token data should be copied over from your old push provider, any messages that need to be sent to legacy devices should be sent from your old push provider and any messages for the latest version of the app can be sent from Xtremepush.

This is the recommended approach as it reduces the opportunity for errors or duplicate messages. The transition method is as follows:

Install the Xtremepush SDK in the app and remove your old push provider SDK
Release this updated version of the app
Messages can continue to be sent to users with older versions of the app using your old push provider
- On Android: These will be ignored in the Xtremepush SDK so no duplicates will be shown
- On iOS: You should run your own tests to ensure that duplicate messages are not shown when sending with the old push provider to the old version of the app, and also to the same device after it has upgraded to the new app version
Messages can be sent to users with the latest version of the app using the Xtremepush platform
- These will not be received in apps that do not contain the Xtremepush SDK, so no duplicates will be shown

Things to note:

To see how many users have migrated over to using the latest version of the app you can compare the number of devices between Xtremepush and the old push provider
Your old push provider will remain the source of analytics for messages sent to legacy devices
Any callbacks that your old push provider has in the legacy version of your app will still be handled as before

Related Topics