Notice: There is no legacy documentation available for this item, so you are seeing the current documentation.
You can move your iOS and Android app push subscribers from OneSignal to PushEngage by reusing the same Apple and Firebase credentials your app already uses. Because device tokens are issued by Apple and Google rather than by OneSignal, keeping those credentials lets your tokens keep working after the switch. This guide explains how the migration works and the steps to set it up. Migration is a backend process handled together with our team.
Before You Start
- Create an account with PushEngage.
- Have your Apple push credentials ready, specifically your App Push ID and the p12 certificate from your Apple Developer account, the same ones used in OneSignal.
- Have your Android Firebase Sender ID, the same one used in OneSignal.
- Have access to your OneSignal account to export subscriber data.
How App Migration Works
Device tokens for app push come from Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM), not from OneSignal. If you configure PushEngage with the same APNs and FCM credentials, your tokens stay valid and the migration happens on the backend. Notification permission also carries over, so a user who already granted permission does not need to grant it again.
Steps to Migrate
Step 1: Export your subscribers from OneSignal
Export your subscriber data using either method:
- API export, using your OneSignal App ID and App API Key.
- CSV export, with a file that includes
identifier,device_type,language, and any other relevant fields.
Step 2: Configure Android FCM in PushEngage
- Log in to the PushEngage dashboard.
- Go to Settings » Installation » Android SDK.
- Configure the Google Android FCM settings using the same Firebase Sender ID you used in OneSignal.
Step 3: Configure iOS APNs in PushEngage
- Go to Settings » Installation » iOS SDK.
- Configure the Apple iOS APNs settings using the same App Push ID from your OneSignal setup.
- Upload the p12 certificate from your Apple Developer account, the same one you used in OneSignal.
[Screenshot: the Android SDK and iOS SDK configuration under Settings » Installation.]
Important Notes on the App Version Cutover
App push migration depends on which version of your app a subscriber is running, so plan your release cutover carefully.
- Older app versions with the OneSignal SDK. After migration, subscribers still on older app versions will not receive notifications sent from PushEngage, because the PushEngage payload cannot be decoded by the OneSignal SDK.
- New app versions with the PushEngage SDK. If you send from the OneSignal dashboard after migration, those notifications will not appear on new app versions, because the OneSignal payload cannot be decoded by the PushEngage SDK.
Send from PushEngage for users on the new app version, and expect users who have not updated to move over as they upgrade the app.
Frequently Asked Questions
Do my app users have to grant notification permission again?
No. If permission was already granted in your app, it carries over and does not need to be granted again after migration.
Will every subscriber receive notifications right after migration?
Users on the new app version with the PushEngage SDK will. Users still on an older app version with the OneSignal SDK will not receive PushEngage notifications until they update the app.
Why do I reuse the same APNs and Firebase credentials?
Because device tokens are tied to those credentials. Reusing the same App Push ID, p12 certificate, and Firebase Sender ID keeps your existing tokens valid, which is what makes the migration possible without asking users to re-register.
What data do I need to export from OneSignal?
Either an API export using your OneSignal App ID and App API Key, or a CSV that includes at least identifier, device_type, and language, plus any other relevant fields.
If you run into any issues, please feel free to contact us by clicking here. Our support team will be able to help you.
