Keep source identifiers
The old provider ID stays traceable
HoneyNotify records the original provider and source device ID. UUID source IDs carry forward as the HoneyNotify Device ID; other formats receive a stable HoneyNotify UUID.
Move without starting over
Switch provider. Keep your device identity.
Move subscribed iOS and Android devices from OneSignal or 15 other push providers with a purpose-built CSV importer. Bring current APNs and FCM tokens, user links, tags, and device context into HoneyNotify without forcing everyone to opt in again.
16 supported sources
Bring your audience from the platform you use today.
Choose your provider in the HoneyNotify dashboard, download its normalised template, and stage the export for token matching.
OneSignal Airship Amazon SNS Azure Notification Hubs
Batch Braze CleverTap Customer.io
Expo Firebase Iterable Klaviyo
Kumulos Pusher Beams Pushwoosh WonderPush
Continuity by design
Your audience should not become a blank slate.
A provider move should change the delivery platform, not break the identifiers and device relationships your product already relies on.
Match push tokens
Recognise the active APNs or FCM destination
The importer hashes each current token for matching. When the HoneyNotify SDK supplies that token, the device is claimed without requiring the user to grant notification permission again.
Avoid duplicates
Recognise devices when the SDK arrives
When your updated app later registers the same token, HoneyNotify matches the imported record and returns its assigned Device ID instead of creating a second device.
A simple migration tool
From export to handover in four clear steps.
No custom migration script and no requirement to place old provider IDs in your application code.
Connect your providersConfigure the same APNs app and environment or Firebase project that your existing tokens belong to.
Export your devicesExport subscribed iOS and Android device data from your current provider.
Upload one CSVMap the export to the guided provider template; native OneSignal exports can be uploaded directly.
Release graduallyAdd the HoneyNotify SDK to your next app release so staged records become active as matching devices register.
Built for a controlled handover: imports validate the complete file before committing changes, skip unsubscribed or invalid rows, enforce your device allowance, and record both an audit event and import history.
Why preserving identity matters
Keep the value you have already built.
Less disruption
No forced re-permission journey
Your users keep their existing operating-system notification permission. You can change the platform behind your app without asking the whole audience to opt in from zero.
Cleaner data
Maintain a stable device relationship
Preserved IDs and token matching reduce duplicate registrations and make it easier to reconcile migrated devices with your own records.
Phased rollout
Migrate on your release schedule
Import first, then introduce the HoneyNotify SDK through normal app releases. Devices can be recognised as users update rather than requiring one disruptive cutover.
Useful context
Bring more than a token
Import external user IDs, tags, app and OS versions, device models, locales, and timezones when those fields are present in your export.
Purpose-built and protected
A migration path that treats device data carefully.
The importer is available to company owners and is designed to keep sensitive push destinations out of normal dashboard and API responses.
Transactional
All valid, or no partial import
A validation or ownership conflict rolls back the file, avoiding an uncertain half-migrated audience.
Auditable
A record of every handover
Import history records the file, owner, row totals, imported devices, updated devices, and skipped rows.
Private
Tokens stay out of view
The import stores token hashes for matching, not raw exported tokens. The current token supplied by the SDK remains hidden from normal dashboard and API responses.
Good to know: token matching depends on the token still being current and on HoneyNotify using the same APNs or Firebase application. If a token rotates before the first HoneyNotify registration, that installation is safely registered as a new device.
Common questions
Plan the move with confidence.
Do users need to allow notifications again?
No. Changing the service that orchestrates delivery does not itself reset the notification permission granted to your iOS or Android app.
Do we need to add old provider IDs to our app?
No. HoneyNotify matches later SDK registrations using the APNs or FCM token and returns the assigned HoneyNotify Device ID automatically.
Can we upload a provider export directly?
Native OneSignal exports are recognised directly. For every supported provider, HoneyNotify supplies a normalised CSV template and accepts common aliases for device IDs, push tokens, platforms, user IDs, subscription state, and device metadata.
What happens to unsubscribed or invalid devices?
They are skipped. A migration should preserve valid reachability, not silently reactivate people who are no longer subscribed.
Ready for a smoother handover?
Create your HoneyNotify app, connect the matching push credentials, and use the built-in importer to bring your active audience with you.