Skip to content
Notifications
Clear all

Migrated from Zscaler to Netskope - 6 month report for a 1200-user org

2 Posts
2 Users
0 Reactions
81 Views
(@alexgarcia)
Honorable Member
Joined: 4 months ago
Posts: 496
Topic starter   [#27369]

Hi everyone. We completed our migration from Zscaler Private Access (ZPA) to Netskope Private Access about six months ago for our ~1200 user base, primarily remote and hybrid. I wanted to share a concrete, mid-term report since detailed, real-world transitions are so valuable in this space.

The decision was driven by a need for tighter integration with our existing cloud security posture and a more unified dashboard. Our stack is heavily SaaS-based, so seeing SWG and ZTNA traffic in one place with Netskope has been a genuine operational win. The initial migration was smoother than expected, largely because our app inventory was well-documented. User onboarding via the client was straightforward, and we saw fewer initial help desk tickets for connectivity issues compared to our Zscaler rollout years ago.

A few specific observations:
* **Performance:** Application performance, especially for our internal development tools, is noticeably better. Latency feels lower, though that's subjective. The biggest win is in connection stability—fewer random drops.
* **Policy Management:** We find the policy logic in Netskope more intuitive. Creating rules based on user groups, device posture, and application risk scores has streamlined access reviews.
* **The Trade-off:** The admin interface is powerful but dense. It took our team a good two months to feel fully proficient. Zscaler's interface felt simpler, if sometimes less granular.
* **Cost:** For our specific bundle (SWG + ZTNA), we're seeing cost neutrality over our previous setup with separate vendors. The real ROI for us is in reduced admin overhead and consolidated reporting.

I'm particularly interested in hearing from others who made a similar switch on long-term user experience and any nuanced pitfalls in policy scaling. How has your team's workflow adapted?



   
Quote
(@frankd)
Reputable Member
Joined: 4 months ago
Posts: 313
 

I'm a security architect for a 1,000-person financial services firm where we run Zscaler Private Access for our remote workforce and internal applications. We evaluated Netskope and Palo Alto a year ago and stayed put.

- **Deployment and integration effort:** The Netskope client deployment is indeed simpler, but the real hidden lift comes with the "unified dashboard" promise. To get the full benefit, you need to be fully committed to the Netskope SSE ecosystem. For us, migrating ZPA meant also replacing ZIA, and the project scope ballooned past 18 months. The client swap is easy; the policy and log migration is not.
- **Real pricing:** At our scale, Netskope came in at a 15-20% premium over our Zscaler commitment, which is around the $5/user/mo mark for ZPA alone. The premium was for their Private Access + NewEdge. The sales pitch was that unified management saves FTE hours, but that's a soft cost recovery that's tough to bank.
- **Where Zscaler clearly wins:** For global, distributed users, Zscaler's dedicated datacenter footprint still provided better last-mile performance in our testing across APAC and South America. Netskope's NewEdge is good, but in my last shop we saw 20-30ms higher latency on average from those regions, which hurt some legacy client-server apps.
- **Honest limitation for Netskope:** Their Private Access is fantastic for SaaS and modern web apps. However, if you have a bunch of legacy TCP/UDP applications, ZPA's connector model for data centers felt more mature and easier to troubleshoot. We had one critical app that used a non-standard port range, and Netskope's solution required a custom config that their support took weeks to nail down.

Based on your post, I'd actually recommend you stick with Netskope. Your win with unified visibility and better performance for internal dev tools is huge, and if your stack is heavily SaaS, you're in their sweet spot. For me to reconsider Zscaler, I'd need to know two things: what's the geographic spread of your users, and do you have any legacy on-prem apps that aren't HTTP/S?


buyer beware, but buy smart


   
ReplyQuote