# Move a pilot group and remote users first, branches by risk next, MPLS hubs and China sites last

Guide, 12 Nov 2026, read 12/13 Nov 2026

**The short answer.** Order a SASE migration by blast radius, not by site size. Pilot users first, remote users off the VPN second, internet-only branches third, MPLS branches and hubs after that, China last. Aryaka states most customers are live in under 4 months, and Palo Alto Networks documents a one-way management choice.

## Order by blast radius

The common mistake is to start with the biggest site because it carries the most savings, or the smallest because it is safe. Neither tells you whether policy is right. Start with a group you can recover quickly, then widen only after a clean week.

The sequence I use has six steps: pilot users, remote users, internet-only branches, branches with MPLS, data center and hub sites, then special cases such as China and OT. Each step has one rollback you can describe in a sentence.

## Steps one and two: users before sites

Pilot with 20 to 50 people across IT, finance and one field team, on managed laptops. This finds category and TLS inspection problems before a branch depends on them. Move the remote user population next, because it replaces the VPN and does not touch circuits.

If you are coming from an existing cloud proxy, ask whether the vendor publishes a migration tool. Cisco states that a no-cost tool lets customers typically complete an upgrade from Umbrella in under an hour. That is the only vendor deployment time of that kind I found, and it covers one source product. Cisco published no deployment time for a new Secure Access plus SD-WAN rollout on 12 Nov 2026.

Keep a written exception list from day one. Every application that breaks under inspection, every legacy host that needs a bypass and every team that asks for an exemption goes on it with an owner and an expiry date. An exception list that is reviewed monthly stays short. One that nobody reads becomes the real policy.

## Step three and four: branches and the MPLS overlap

Internet-only branches move before MPLS branches, because there is no second path to preserve. Branches on MPLS need an overlap period in which both transports carry traffic. Check Point states its SD-WAN steers by link health and fails over in under a second to MPLS, 5G or broadband. Forcepoint's SD-WAN page describes mixing broadband and private MPLS. Cato states that its platform coexists with existing infrastructure and allows gradual adoption. Aryaka states it supports a mix of Aryaka and third-party security during migration.

All of those are vendor statements. What they mean for you: do not cancel MPLS circuits at cutover. Keep them for one full billing cycle after the last application moves, and read the notice period in each carrier contract before you start.

## Timelines vendors publish

Aryaka states that most customers are live in under 4 months, with implementation, operations and 24/7 support included as a service. Cloudflare says partners TachTech and Adapture cut SASE migrations from 18 months to 6 weeks, a vendor-selected example.

My own numbers are less flattering. Device install is the quick part. The slow parts are policy mapping, application owner sign-off and the carrier change windows.

## Choices that cannot be undone

Palo Alto Networks documents that Prisma Access has two management options, Strata Cloud Manager and Panorama, that features differ between them, and that a deployment cannot be migrated from Strata Cloud Manager back to Panorama. Decide that in the design phase, not in week six.

Fortinet states that a subscription provides between one and four security PoPs unless a PoP add-on or global license is bought, and that Comprehensive subscriptions under 200 users have limited PoP availability. A pilot on a small license can show good latency that a full rollout does not reproduce. Test with the PoP set you will own.

## Data center, hub and special sites last

Hubs concentrate traffic, so a fault there hurts everyone. Move them after branches have run for a month, and use a second tunnel or interconnect during the move. Palo Alto Networks lists Colo-Connect at up to 20 Gbps per region as an add-on for private connectivity from a hub. Treat that as a design input, not a migration step.

China goes last and gets its own plan. Cisco requires a separate Secure Access China subscription operated by Digital China Cloud Technology. Palo Alto Networks sells Prisma Access China as a separate deployment type. Fortinet routes China through a dedicated partner. Start the paperwork early, since those arrangements involve a different contract party.

## Cutover checklist per site

Per site I want: a recorded baseline of latency to three named applications, the rollback written down, a named person at the site for the window, and a seven-day watch period before the circuit decision. Move one site type fully before starting the next. Then record what broke at each step in the runbook. The second wave takes half the time of the first when you do.

## Sources

- Cisco, Secure Access data sheet: https://www.cisco.com/c/en/us/products/collateral/security/secure-access/secure-access-ds.html (read 12 Nov 2026)
- Check Point, Internet Access: https://www.checkpoint.com/harmony/sase/internet-access/ (read 12 Nov 2026)
- Forcepoint, Secure SD-WAN: https://www.forcepoint.com/product/secure-sd-wan (read 12 Nov 2026)
- Palo Alto Networks, Prisma Access licensing guide: https://www.paloaltonetworks.com/apps/pan/public/downloadResource?pagePath=/content/pan/en_US/resources/datasheets/prisma-access-licensing-guide (read 12 Nov 2026)
- Cato Networks, platform architecture: https://www.catonetworks.com/platform/architecture/ (read 12 Nov 2026)
- Cisco, Secure Access regions: https://www.cisco.com/c/en/us/td/docs/security/secure-access/secure-access-help/CiscoSecureAccessHelp/regions-intro/secure-access-regions.html (read 12 Nov 2026)
- Aryaka, Unified SASE platform: https://www.aryaka.com/unified-sase-platform/ (read 12 Nov 2026)
- Aryaka, SASE reviews: https://www.aryaka.com/sase-reviews/ (read 12 Nov 2026)
- Cloudflare, SASE migrations blog: https://blog.cloudflare.com/complexity-is-a-choice-sase-migrations-shouldnt-take-years/ (read 12 Nov 2026)
- Palo Alto Networks, Prisma Access administration guide: https://docs.paloaltonetworks.com/content/dam/techdocs/en_US/pdf/prisma-access/prisma-access-administration.pdf (read 12 Nov 2026)
- Fortinet, FortiSASE ordering guide: https://www.fortinet.com/content/dam/fortinet/assets/data-sheets/og-fortisase.pdf (read 12 Nov 2026)

Last reviewed 12 Nov 2026. Canonical: https://bestsasesolutions.com/guides/sase-migration-order/
