Migration from MPLS to SD-WAN – Migration checklist

The transition from an MPLS-based network to an SD-WAN is often unclear. What steps need to be taken when switching from a conventional MPLS network to an SD-WAN? We’ll tell you here:

1. migration of the sites from MPLS to SD-WAN

1.1 – Categorization of locations
Grouping of individual locations according to their requirements for availability, package delivery times, package loss and costs.

1.2 – Choosing the right “last mile”
The higher the requirements of the categorized locations, the more performant and secure the last mile must be. Internet via fiber optics, copper, radio relay, LTE or a hybrid solution consisting of several connection variants.

1.3 – Choosing the right “middle mile”
While the “last mile” covers availability and packet loss, the focus of the “middle mile” is particularly on latency and carrier lock-in. There are basically two variants of the “middle mile”. One is the unpredictable public Internet and/or the SLA-supported backbones of various carriers.

1.4 – The right choice of network architecture
With the right combination of DIA and broadband services on the “last mile” and a private backbone on the “middle mile”, it is possible to achieve MPLS-like quality. But with Internet-like price and flexibility.

2. procurement of services

2.1 – Procurement of the infrastructure
Should the procurement be carried out by the IT and/or purchasing department in conjunction with laborious market research, or should it be outsourced to a “last mile” market specialist such as Savecall? Savecall takes over the entire procurement process and obtains vendor-neutral offers in the shortest possible time. In most cases, this is completely cost-neutral.

2.2 – Procurement of the SD-WAN service
The SD-WAN market has grown enormously. At first glance, it seems impossible to compare products. A wide variety of hardware meets equally diverse software. Each provider has its own license. This in turn contains endless “feature lists” that have to be painstakingly disentangled. The question is: Which product is suitable for my predefined catalog of requirements? Here too, Savecall can provide support throughout the entire process thanks to its many years of experience. From conceptualization to obtaining quotations with final negotiated prices.

3. review of the security strategy

Security processes can be designed more effectively and efficiently in the SD-WAN. To do this, the previous security measures must be reassessed.

3.1 – Define SASE solution
Equip every company location with its own local firewall? Far too expensive and extremely complex to manage – the solution is SASE.
SASE integrates security functionalities into the WAN. On a session and user basis, in a zero-trust environment. Security and network are managed via the cloud so that administrators can make changes once and apply the policies to all locations and users. Secure Access Service Edge thus enables the company to securely connect remote workers and “IoT services” to the WAN. There are basically 4 SASE subscription models. “Cloud-native SASE”, “Cloud-managed on-premises SASE”, “Managed SASE” and “Hybrid SASE options”.

3.2 – Recognizing the “problem with centralizing security in the SD-WAN”
Depending on the solution and provider, centralizing the security solution may make the security processes more manageable and scalable, but this approach can also generate considerable additional latency, which can be particularly noticeable in cloud and Internet applications. This problem can quickly become a hidden cost factor if only upgrading the infrastructure (last mile / middle mile) subsequently helps. SD-WAN solutions that already provide for deep SASE integration throughout their architecture are an advantage here.

4. connection of cloud applications with the SD-WAN

The complete connection of cloud data centers (IaaS) or cloud applications (SaaS) to the SD-WAN is only a matter of time. By connecting cloud resources to the SDWAN, companies can counteract latency and packet loss and generally help to significantly improve “user-friendliness” through more stable performance.

5. optimization for mobile users

The SD-WAN solution should enable “mobile users” to connect to any SD-WAN node and ensure high-performance access to the corporate network. It should be possible to monitor data traffic in the SD-WAN. Particular attention should be paid to the security solution (SASE).

6. the right SD-WAN management model

There are basically four ways to manage SD-WAN solutions: “do-it-yourself (DIY)”, “fully managed carrier service”, “self-service” and “co-managed services”. The approaches differ in the degree of administration, responsibility for continuous monitoring, infrastructure maintenance and change management required by the customer. The company structure, existing “know-how”, personnel resources and the preferences of the IT department are decisive for the right decision.