WAN7 min read

SD-WAN vs MPLS: how multi-site organizations decide

For years, MPLS was the default way to connect branch offices. SD-WAN changed the economics, but it isn’t automatically the right answer for every site. Here is how to think through the decision.

Fiber strands fanning out into many points of light

How they differ

MPLS is a private network sold by a carrier. Traffic travels over the provider’s backbone with predictable latency and service-level agreements, but bandwidth is relatively expensive and changes can take weeks.

SD-WAN is an overlay. It builds encrypted tunnels across whatever circuits a site has — broadband, fiber, LTE, 5G or MPLS — measures each path continuously and steers applications down the best one at that moment.

Where SD-WAN wins

Cost per megabit
Business broadband usually delivers far more bandwidth for the money than MPLS.
Resilience
Two diverse circuits plus cellular backup means a single failure no longer takes a site offline.
Cloud and SaaS
Branches can reach cloud services directly instead of backhauling everything through headquarters.
Speed of change
New sites and policy changes are pushed centrally, often without an engineer on site.

Where MPLS still earns its place

MPLS remains a good fit for a small number of sites with strict latency or jitter requirements, for locations where broadband options are poor, and where a contract or regulatory requirement favors a private carrier network. SD-WAN can manage MPLS as one of its paths, so keeping it at a few critical sites doesn’t mean giving up the overlay.

Questions to answer before you decide

What do your applications need?
Profile voice, video, ERP and SaaS traffic, and note which are sensitive to latency.
What circuits are available at each site?
Check broadband and fiber options, including diverse carriers and physical paths.
When do contracts end?
Align migration waves with MPLS renewal dates to avoid paying for both longer than necessary.
Who will run it?
SD-WAN simplifies a lot, but someone still needs to own policy, monitoring and carrier issues.

A sensible migration path

Start with a pilot at one or two representative sites, running SD-WAN alongside the existing MPLS. Validate application performance and failover, then migrate in waves. Many organizations end up with a hybrid: broadband plus cellular at most sites, MPLS retained where it’s truly needed.

Want an engineer’s view of your own network? Free network assessment

Network assessment

Ready for a network that holds?

Tell us about your sites, circuits and goals. A senior network engineer replies within one business day.