You can move your web push subscribers from Webpushr to PushEngage. Because web push subscriptions are tied to your domain and encrypted, they cannot simply be copied over and used right away, so this guide explains the path that works and what to expect afterward. Migration is handled together with our team.
Before You Start
- Create an account with PushEngage and complete installation from Site Settings » Installation.
- Have access to your Webpushr account.
- Know roughly how many subscribers you have, so we can confirm the right path for your account.
- After migration, plan to upgrade your PushEngage plan to fit your subscriber count before you start sending.
How Web Push Migration Works
There are two possible paths, depending on what your current provider can give you.
Path 1: Key-based import
If Webpushr can provide your subscriber list with each subscriber’s endpoint, auth key, p256dh, and VAPID public and private keys, we can import it as a CSV.
You can send a sample list to our Support Team and they will confirm if the file has required details or not to complete the Key Based Migration.
Path 2: Silent resubscribe
Silent resubscribe brings your subscribers over without needing those keys, and without asking anyone to opt in a second time. We recommend using this approach to avoid any hastle.
- Complete PushEngage installation from Site Settings » Installation.
- Your existing subscribers are re-subscribed to PushEngage quietly the next time they visit your site. They are not shown the opt-in popup again, because a subscriber who already granted notification permission does not need to grant it again.
- As subscribers return, they are recovered under PushEngage over time.
If you would rather ask subscribers for permission again as part of the switch, see Ask Before Resubscribing When Migrating to PushEngage.
Navigate to Site Settings » Site Details and scroll to Ask Before Auto-Subscribing and Toggle to Yes.
What to Expect After Migration
Migration is not a switch that is fully on the moment it completes. Reachability starts lower and climbs over time.
Think of a subscriber’s service worker as the delivery address of someone with no phone. The only way they learn something has arrived is when the mailman actually knocks. In the same way, a migrated subscriber’s service worker only updates when that person next visits your site, whether they come back on their own or land there from a push or an email. Until that visit happens, that subscriber shows up as lower reachability. As migrated subscribers return over the following days, your reachability rises gradually. Sending campaigns and keeping up your normal email and on-site activity helps subscribers come back sooner.
Frequently Asked Questions
Will all my subscribers move over immediately?
No, and that is normal for web push. With silent resubscribe, subscribers are recovered as they return to your site, so your reachable count builds up gradually rather than all at once.
Do I need keys from Webpushr?
Only for the key-based import path. If those keys are not available, you can still migrate with silent resubscribe, which does not need them.
Will my subscribers see a second opt-in popup?
No. Silent resubscribe re-subscribes people who already gave permission without showing the opt-in popup again.
Why is my reachable count lower right after migration?
Because a subscriber’s service worker only updates when they next visit your site. Until then they count as lower reachability, and the number rises as people come back over the following days.
If you run into any issues, please feel free to contact us by clicking here. Our support team will be able to help you.