Migrate from Bloom Intelligence to MyWiFi: Hardware-Agnostic

Key Takeaways: Bloom Intelligence built its platform around sensor-based WiFi analytics — physical presence detection, walk-by traffic, and dwell-time measurement. Resellers migrate to MyWiFi when they need a broader platform: full marketing automation (email, SMS, WhatsApp), white-label for branded services, 20+ hardware vendor support without proprietary sensors, and a reseller-focused pricing model. The migration shifts from sensor-dependent analytics to cloud-based, hardware-agnostic WiFi marketing that captures identity data alongside behavioral metrics.

Bloom Intelligence positioned itself in the WiFi analytics space with a focus on customer intelligence — presence analytics, churn prediction, and behavioral measurement using WiFi sensor technology. Their approach to WiFi data is analytics-first: understanding foot traffic patterns, dwell times, and visitor demographics through passive WiFi sensing.

This analytics-first approach has real value for venues that need foot traffic measurement. The migration to MyWiFi typically happens when resellers want to add full marketing automation, white-label branding, and multi-channel campaign capabilities on top of the analytics foundation — or when they want to deploy across hardware they already have in the field without requiring proprietary sensors.

---

Why resellers migrate from Bloom

• •Hardware dependency: Bloom's platform often requires specific sensor hardware for full functionality. MyWiFi is hardware-agnostic, working with 20+ existing WiFi vendors — no proprietary hardware required for core features.
• •Marketing automation depth: MyWiFi provides full multi-channel marketing: email sequences, SMS campaigns, WhatsApp messaging, behavioral triggers, CRM integrations, and campaign analytics. The platform was built for marketing execution, not just data collection.
• •White-label capability: Full white-label on all MyWiFi plans — custom dashboard domains, portal domains, email sender domains, and complete branding control for resellers.
• •Reseller-first pricing: Per-AP tiered pricing designed for channel partners managing multiple client venues across verticals.
• •Captive portal focus: MyWiFi's WYSIWYG portal builder with drag-and-drop design, social login, WhatsApp OTP, and paid WiFi options provides a richer guest interaction than passive sensing alone.

Bloom's analytics capabilities — particularly passive presence detection (counting WiFi-enabled devices without requiring authentication) — provide data that active captive portals don't capture. If walk-by traffic and passive dwell time are critical metrics for your clients, verify that MyWiFi's presence analytics (available on Pro+ plans) meets the specific measurement needs before migrating.

---

Migration considerations

Analytics vs. marketing: different approaches

Bloom approach: Sensor detects WiFi-enabled devices passively. No guest interaction required. Data includes: device count, dwell time, visit frequency, walk-by vs. walk-in ratio. Identity data is limited to what's captured through an optional captive portal.

MyWiFi approach: Captive portal captures identity data actively. Guest authenticates via email, social login, or WhatsApp. Data includes: verified contact info, visit frequency, dwell time, campaign engagement, and behavioral triggers. Presence analytics (passive detection) is available as an add-on.

The migration shifts the primary data source from passive sensing to active authentication. This means richer identity data (real emails, phone numbers, social profiles) but a different metric for total foot traffic (connected guests vs. all WiFi-enabled devices).

Data portability

Export from Bloom:

• •Contact/guest databases (CSV)
• •Analytics summaries and reports (PDF or CSV)
• •Campaign configurations (document or screenshot)

Note: Passive presence data (anonymous device detections) typically cannot be migrated because it's aggregated, non-personal data that doesn't transfer to a contact-based system.

---

Migration steps

Phase 1: Setup and build (Day 1-5)

1. •Sign up for MyWiFi and configure white-label
2. •Create locations matching Bloom deployment
3. •Build branded captive portals for each venue
4. •Create marketing automation sequences
5. •Configure CRM integrations

Phase 2: Data and hardware (Day 5-8)

1. •Import Bloom contact data via CSV
2. •Configure existing venue WiFi hardware for MyWiFi portal redirect
3. •If venues had Bloom-specific sensors, decide whether to keep them for foot traffic counting alongside MyWiFi for marketing (dual-use) or retire them

Phase 3: Test and cutover (Day 8-12)

1. •Test portals and automations
2. •Cutover during off-peak hours
3. •Monitor for 1 week
4. •Deliver first post-migration report

---

Addressing the analytics gap

If your clients valued Bloom's passive presence analytics, address the gap proactively:

MyWiFi's presence analytics

Available on Pro plans and above, MyWiFi's presence analytics tracks:

• •Connected vs. non-connected device counts
• •Dwell time distribution
• •New vs. returning visitor ratio
• •Peak hour analysis
• •Footfall trends over time

For venues where compatible hardware supports it (Meraki CMX, for example), passive presence data supplements the active captive portal data.

Supplementary tools

For venues that need deep foot traffic analytics beyond WiFi marketing:

• •People counters: Dedicated foot traffic sensors (RetailNext, Dor, ShopperTrak) provide accurate entry/exit counts independent of WiFi
• •Google Popular Times: Free, approximate foot traffic data from Google Maps
• •POS transaction data: Transaction count as a proxy for customer volume

The combination of MyWiFi's marketing platform + a dedicated people counter often provides more comprehensive data than a WiFi analytics-only approach.

---

Post-migration capabilities

---

FAQ

Will I lose passive foot traffic data after migration?

If you relied on Bloom's passive sensing, yes — that specific data source changes. MyWiFi tracks connected devices and presence analytics on compatible hardware. For total foot traffic (including walk-bys who don't connect), you'd need a supplementary counting solution. Many resellers find that the marketing value of identity-based data more than compensates for the loss of anonymous walk-by counts.

Is MyWiFi suitable for restaurant analytics the way Bloom was?

Yes, with a different emphasis. Bloom focused on visit frequency prediction and churn scoring through passive analytics. MyWiFi focuses on capturing guest identity and driving return visits through automated campaigns. The end goal — more return visits, higher guest retention — is the same. The mechanism differs.

Can I use both platforms simultaneously?

Yes. Some resellers maintain Bloom sensors for analytics while using MyWiFi for captive portal and marketing. This dual-stack approach provides both passive foot traffic data and active guest engagement but increases operational complexity and cost.

How do I explain the platform change to my clients?

"We're upgrading your WiFi marketing system to add automated campaigns, branded portals, and multi-channel messaging. You'll see enhanced reporting that connects guest data directly to marketing campaigns and measurable return visits. The analytics you relied on continue — plus now we can actually reach those guests with targeted offers."

What's the typical timeline for migrating 10 locations from Bloom?

2-3 weeks with a phased approach. The hardware reconfiguration is the most variable component — it depends on whether venues have standard commercial WiFi equipment (quick) or Bloom-specific sensors that need replacement (longer).