Migrate from Purple WiFi to MyWiFi: Step-by-Step Guide
Key Takeaways: Migrating from Purple WiFi to MyWiFi takes 1-2 weeks per client location. The process: export contact data from Purple, configure MyWiFi platform and hardware integration, rebuild splash pages, recreate automation sequences, and verify everything works before cutting over. Guest data is portable — you own it. Hardware compatibility is broader on MyWiFi (20+ vendors vs. Purple's more limited list). The white-label depth is significantly deeper, giving resellers full branding control. Plan the migration during a low-traffic period to minimize data capture gaps.
Purple WiFi built a solid reputation in guest WiFi analytics, particularly in the UK market. After their acquisition by Switch in 2021, some resellers have found that the platform's direction, pricing, or feature set no longer aligns with their business needs.
This guide walks through the migration from Purple to MyWiFi — what to expect, what to prepare, and how to execute the transition without disrupting your clients' guest WiFi experience.
Why resellers move from Purple
Resellers migrate from Purple for several common reasons. These are observations from resellers who've made the switch — not criticisms of the platform:
- •White-label limitations: Purple's standard plans don't offer the same depth of white-label platform customization that reseller businesses require. Dashboard domains, email sending domains, and portal URLs may carry Purple branding.
- •Hardware compatibility: Purple supports fewer hardware vendors, limiting deployment options at venues with existing equipment.
- •Reseller-focused features: MyWiFi was built specifically for the reseller channel. Features like subuser management, client-level isolation, and reseller-specific pricing reflect that focus.
- •Pricing structure changes: Post-acquisition pricing adjustments have affected margins for some resellers.
- •WhatsApp OTP: MyWiFi offers native WhatsApp WiFi login — a feature not available on Purple — which is essential for resellers operating in international markets.
Purple does several things well: their analytics visualizations are strong, their UK market presence is established, and their enterprise positioning is clear. The migration decision isn't about Purple being bad — it's about whether the platform fits your specific reseller business model.
Pre-migration checklist
Before starting the technical migration:
1. Audit your current Purple deployment
Document everything:
- •Number of client locations
- •Hardware vendor and model at each location
- •Current splash page designs (screenshots)
- •Active automation sequences (triggers, filters, delays, actions)
- •CRM integrations (Mailchimp, HubSpot, etc.)
- •Contact database size per client
- •Reporting schedules and formats
2. Export all data from Purple
Contact data: Export all guest contacts in CSV format. Include: email, name, phone, visit count, last visit date, and any custom fields.
Analytics data: Export historical analytics reports if available. Visit trends, peak hours, and demographic data. This baseline ensures continuity in client reporting.
Campaign data: Document (screenshot or copy) all active email templates, automation workflows, and campaign configurations. These need to be recreated in MyWiFi.
3. Set up MyWiFi
- •Sign up for the appropriate MyWiFi plan based on your location count
- •Configure white-label branding (dashboard domain, portal domain, logo, colors)
- •Set up client subuser accounts
- •Create locations matching your Purple deployment
4. Notify clients
Tell your clients about the migration — but keep it simple:
"We're upgrading your WiFi marketing platform this month. You'll see a refreshed login page on your WiFi and some improvements to the dashboard. There's no action needed on your end. I'll handle everything and your data is fully preserved."
Migration steps
Step 1: Rebuild splash pages in MyWiFi (Day 1-3)
Recreate each client's portal using MyWiFi's WYSIWYG editor:
- •Upload client logo and brand assets
- •Set brand colors
- •Configure login methods (replicate what was on Purple, or upgrade to include new options like WhatsApp)
- •Set form fields
- •Add legal compliance elements (consent checkbox, privacy policy, terms links)
- •Configure smart redirect (post-auth destination URL)
- •Generate preview link and send to client for approval
Tip: This is an opportunity to optimize. If the Purple portal had 4 form fields, consider reducing to 2. If it only offered email login, consider adding social login or WhatsApp OTP. Migration is a natural moment to improve.
Step 2: Recreate automation sequences (Day 2-4)
Rebuild your automation workflows:
- •Welcome sequence: Recreate trigger (first connection), delays, and email content
- •Return visit incentive: Recreate the 7-day no-return trigger
- •Win-back campaign: Recreate the 30-day inactivity trigger
- •Birthday campaign: Recreate if birthday data was captured
- •CRM sync: Reconnect CRM integrations (Mailchimp, HubSpot, etc.)
MyWiFi's automation builder supports the same trigger types as Purple (connect, disconnect, inactive, birthday) plus additional filter options and channel actions (SMS, WhatsApp, webhooks).
Step 3: Import contact data (Day 3-5)
Import the CSV exported from Purple:
- •Map Purple export columns to MyWiFi contact fields
- •Assign contacts to the correct location
- •Import in batches if multiple locations
- •Verify import accuracy (spot-check 10-20 records)
- •Re-segment contacts based on visit history
Important: Imported contacts retain their marketing consent from the original collection (you're transferring data within your processing capacity as the reseller). Document the migration date in your data processing records.
Step 4: Configure hardware (Day 4-6)
Reconfigure each venue's WiFi hardware to point to MyWiFi's portal instead of Purple's:
- •Access the venue's WiFi controller
- •Update the external captive portal URL to MyWiFi's portal endpoint
- •Update the walled garden to include MyWiFi's domains (and remove Purple's)
- •Update the authentication callback URL
- •Test the portal on iPhone, Android, and laptop
Hardware compatibility advantage: MyWiFi supports 20+ hardware vendors including Cisco Meraki, Ubiquiti UniFi, Aruba, Ruckus, Datto, MikroTik, EnGenius, Cambium, Cradlepoint, and more. If your Purple deployment was limited by hardware support, the migration may allow you to serve venues with previously incompatible equipment.
Step 5: Test and verify (Day 5-7)
Before cutting over, compare features to ensure every Purple capability has been replicated or upgraded:
- • Portal loads correctly on all devices
- • Authentication completes end-to-end
- • Guest data appears in MyWiFi dashboard
- • Automation sequences fire on test connections
- • CRM integration syncs test contacts
- • Reports generate accurately
- • Client dashboard access works with subuser credentials
Step 6: Cutover and monitor (Day 7-14)
- •Switch the hardware configuration from Purple to MyWiFi (this is the cutover moment — do it during off-peak hours)
- •Monitor the first 24-48 hours closely
- •Verify real guest connections appear in the new platform
- •Confirm automation campaigns fire for real guests
- •Send the first post-migration report to the client
Timeline summary
| Day | Activity |
|---|---|
| 1-3 | Rebuild splash pages, get client approval |
| 2-4 | Recreate automation sequences |
| 3-5 | Import contact data |
| 4-6 | Configure hardware |
| 5-7 | Test everything |
| 7 | Cutover (during off-peak hours) |
| 7-14 | Monitor and verify |
Total time per location: 7-14 days, with 3-5 hours of active work.
For multi-location clients, batch the migration. Do 3-5 locations per week.
Post-migration: what's new on MyWiFi
After migration, take advantage of features that weren't available on Purple:
- •Full white-label: Custom dashboard domain, portal domain, email sender domain, and complete branding control
- •WhatsApp OTP login: Add WhatsApp as a login option for venues in WhatsApp-dominant markets
- •20+ hardware vendors: Deploy at venues with hardware Purple didn't support
- •Built-in ad server: Monetize captive portal impressions with advertising (Agency plans and above)
- •Sales CRM: Live preview links and lead tracking for prospecting new clients
- •Zapier integration: Connect to 6,000+ apps via webhooks and Zapier
Resellers migrating from Purple also gain access to formal partner program benefits — including tiered reseller margins, co-marketing support, and dedicated partner success resources.
FAQ
Will my clients experience any WiFi downtime during migration?
The cutover moment (switching the hardware from Purple to MyWiFi) takes 5-15 minutes. During that window, guests may see no portal or a brief loading error. Schedule the cutover during the venue's lowest traffic period (typically 2-4 AM or early morning). The interruption is too short for most guests to notice.
Can I migrate Purple's analytics history?
Partially. Contact data and visit counts can be exported and imported. Detailed analytics (heatmaps, hourly traffic patterns, presence data) typically can't be migrated between platforms. Screenshot or export Purple's analytics reports for historical reference, and start fresh analytics tracking in MyWiFi from the migration date.
Do I need to be on-site for the migration?
Not if you have remote access to the WiFi controller (cloud-managed systems like Meraki, UniFi Cloud, or Aruba Central). The entire migration can be done remotely. Have someone at the venue test the portal on a real device after cutover.
What if some of my clients' hardware isn't supported by MyWiFi?
Check the hardware compatibility list. MyWiFi supports 20+ vendors — it's one of the broadest compatibility lists in the industry. For truly unsupported hardware, a MyWiFi hotspot device can be deployed alongside the existing network to handle captive portal duties.
How long should I maintain both platforms during migration?
Keep your Purple account active for 30 days after the last client has migrated. This gives you a fallback if any issues arise and time to verify all data has been successfully transferred. Cancel the Purple subscription only after you've confirmed all clients are fully operational on MyWiFi.
Will the migration affect my clients' GDPR compliance?
No, as long as the data transfer follows your existing Data Processing Agreement. You're transferring data within your capacity as a data processor — the data controller (your client) is unchanged. Document the migration in your data processing records and update the DPA to reference the new sub-processor (MyWiFi).