Track A. Progressive takeover
Install EngageNudge alongside your current provider. Returning visitors with existing browser permission re-register silently, no new prompt. Typical timeline: 1 to 6 months depending on repeat traffic.
Bring your audience with you, where the technology allows it.
I have switched providers. It is messy. I will not tell you the list comes over clean before anyone has looked at keys, the service worker, and what you can actually export.
Talk about migrationWe inspect before we promise.
Migration is an implementation issue, not a slogan. We never promise zero subscriber loss before technical discovery.
How migration works
Discovery
Review your current web push origin, service worker scope, VAPID keys and subscriber export options.
Recommendation
Choose direct import, staged handover or gradual re-subscription based on what your stack actually supports.
Validation
Test on a subset, verify delivery and engagement signals, then cut over with export paths documented.
Two migration paths
Track B. Day-1 import
When you can export your VAPID key pair and subscriber endpoints from your previous provider, EngageNudge can import them so you can send from day one. Requires matching keys. We validate before accepting.
Provider playbooks
Each stack differs. These are technical starting points, not guarantees. We confirm feasibility during discovery.
OneSignal
- Export
- CSV export via REST API with extra fields web_auth and web_p256 (identifier column holds the push endpoint).
- VAPID
- Request your site's VAPID public and private keys from OneSignal support for day-1 import.
- Service worker
- OneSignalSDKWorker.js, OneSignalSDKUpdaterWorker.js. Unregister during cutover.
- Timeline
- Progressive: repeat visitors migrate silently once EngageNudge SDK is live. Day-1: only when keys + endpoints are supplied and validated.
PushEngage
- Export
- Contact support for subscriber export format on your plan.
- VAPID
- Verify whether your account uses customer-owned or platform VAPID keys before promising day-1 import.
- Service worker
- Provider service worker path varies. Inspect active registrations before cutover.
- Timeline
- Progressive takeover on return traffic is the default realistic path.
iZooto
- Export
- VAPID endpoint export available for supported accounts; CSV/API fields include endpoint, auth, p256dh.
- VAPID
- Import path documented by iZooto when you supply keys from OneSignal or prior provider.
- Service worker
- Replace provider SDK; returning subscribers migrate as service worker updates.
- Timeline
- High repeat-traffic sites may see meaningful migration in weeks; long tail can take months.
PushAlert
- Export
- Verify export availability with your account team.
- VAPID
- Confirm key ownership model before day-1 import.
- Service worker
- Inspect push-related service worker registrations on your origin.
- Timeline
- Plan for progressive takeover unless discovery confirms full export.
Honest about constraints
Customer-specific VAPID keys, audience export, and documented migration paths are part of the product, not a sales footnote. Some providers cannot move every subscriber; we say so upfront.
Your audience stays yours. We help you move without pretending every stack is identical.
Start in the dashboard
Use the Migration tab under Integrations in app.engagenudge.com for guided setup, CSV import, and progress by source.
Know when to nudge.
Know when a notification is worth sending.
The useful question is who should not get this one.