Your subscriber list
Subscribers ride through transparently — either via your existing VAPID pair (if PushEngage exposes it) or via our silent re-subscribe on next visit. Either way, no permission dialog.
Migration
Migrate from PushEngage to ReachBell in 5 minutes.
PushEngage is push-only and bills in dollars. ReachBell ships push, email, and automations in one tool with INR billing — and you can switch without re-prompting a single subscriber, even if PushEngage won’t hand over your VAPID keys.
Zero subscriber loss. Even without VAPID export.
PushEngage doesn’t always let you export VAPID keys. We solved that. ReachBell’s SDK detects existing push permission and silently re-subscribes the browser to your new project — no dialog, no banner, no user interruption. Subscribers don’t notice; you keep the list.
Three steps
A weekend project, max.
The longest part is exporting your CSV. Everything after is templates.
1. Pull your VAPID keys
PushEngage doesn't always expose the underlying VAPID pair in the UI — newer accounts manage them server-side. If you can see them in Settings → Site Settings → API Keys, export them. If not, our migrator does a silent re-subscribe handshake on the next page view (more on that below).
2. Replace the SDK script
Delete the clientcdn.pushengage.com snippet and its service-worker file (service-worker.js or pushengage-sw.js). Drop in ReachBell's three-line snippet plus /reachbell-sw.js. No permission re-prompt — the browser already has push permission for your origin.
3. Verify subscriber sync
Open ReachBell → Project → Verification and reload your site in a logged-in browser. You should see a "subscriber matched" event within seconds. Send a test push, confirm it lands on your device, then retire the PushEngage account.
The SDK swap
One script out, one script in.
The only code change on your site. Everything else lives in the ReachBell dashboard.
index.html · <head>
- <script src="https://clientcdn.pushengage.com/core/p7e8a9b0c1d2e3f4.js" async></script>
- <script>
- window._peq = window._peq || [];
- _peq.push(["init"]);
- </script>
+ <script src="https://cdn.reachbell.com/sdk/v1/reachbell.js" defer></script>
+ <script>
+ window.ReachBell = window.ReachBell || [];
+ ReachBell.push(rb => rb.init({
+ projectId: "prj_...",
+ silentResubscribe: true // for PushEngage cutovers
+ }));
+ </script>The silentResubscribe flag handles the case where PushEngage owns your VAPID keys — drop it once your list has rolled over.
What you keep
Everything that drives revenue.
The list, the triggers, the segments, the deliverability score — all of it crosses over.
Segments and tags
PushEngage's CSV export from Audience → Subscribers includes every dynamic and geographic segment. Import via our REST API or CSV uploader — segments rebuild on ingest.
Trigger campaigns
Cart abandonment, browse abandonment, price-drop, and inventory-back triggers all map 1:1 to ReachBell automations. We'll rebuild them for you on every paid plan.
Browser deliverability
Push deliverability is per-origin — browsers don't care which vendor manages the key. Your reputation and CTR carry over the moment our SDK loads.
What you gain
The three things PushEngage doesn’t ship.
Push is the start. ReachBell covers the rest of the engagement stack in the same dashboard.
Email is in the same tool
PushEngage is push-only and pushes you to a partner for email. ReachBell ships campaigns and transactional email on AWS SES in the same dashboard with shared segments.
Automations without upsell
Welcome series, drip nurtures, win-back journeys — included on Growth (₹2,999/month). No "talk to sales" gate to unlock a workflow builder.
Rupee pricing, GST invoices
PushEngage bills in USD with no GST invoice. ReachBell bills in INR via Cashfree (UPI, cards, net banking) and ships an invoice your accountant accepts.
Average cutover time, including trigger rebuild: one afternoon. Talk to sales@reachbell.com
FAQ
Questions, answered.
Everything teams usually ask before switching. Something missing? Email us — a human replies.
Will my PushEngage subscribers stay subscribed when I switch to ReachBell?
Yes. If you can extract your VAPID public/private pair from PushEngage (Settings → Site Settings on older accounts), bring them into ReachBell and every browser keeps its existing push subscription. If PushEngage doesn't expose the keys, ReachBell's SDK performs a silent re-subscribe on the next page view — the browser already has push permission for your origin, so no dialog appears, and the new subscription is recorded against your new VAPID pair in the background.
What if PushEngage won't give me my VAPID keys?
That's the common case on newer PushEngage accounts. Our silent re-subscribe flow handles it: the ReachBell SDK detects an existing push permission, generates a new subscription under our VAPID keys, and registers it with your project. Users see nothing — no permission prompt, no banner, no interruption. Over 1-2 weeks of traffic, the bulk of your active list rolls over.
How do I export my data from PushEngage?
Go to Audience → Subscribers → Export. PushEngage emails you a CSV with subscriber IDs, tags, segments, browser type, geo, and last-seen timestamp. Pipe it into ReachBell's subscriber importer (REST API endpoint /v1/subscribers/import or the dashboard uploader) and segments rebuild automatically from the tag columns.
Can I keep my PushEngage trigger campaigns running during the cutover?
Yes — keep PushEngage active for a week alongside ReachBell. Both SDKs can coexist on the page without conflict. Run a single A/B test (ReachBell campaign vs PushEngage trigger) to confirm parity on CTR and delivery, then disable PushEngage triggers and remove the script.
Do you help with the migration?
Every paid plan includes free migration help. Email sales@reachbell.com with your PushEngage site ID and a sample subscriber export — we handle the import, rebuild your trigger automations in our journey designer, and run a verification call before you flip the SDK. Most PushEngage migrations finish in one afternoon.