{"id":111,"date":"2019-02-28T09:28:15","date_gmt":"2019-02-28T09:28:15","guid":{"rendered":"https:\/\/www.extnoc.com\/sd-wan\/?page_id=111"},"modified":"2026-11-02T13:03:33","modified_gmt":"2026-11-02T13:03:33","slug":"sd-wan-migration","status":"publish","type":"page","link":"https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/","title":{"rendered":"SD-WAN Migration"},"content":{"rendered":"

<\/span>SD-WAN Migration Overview and How It Works<\/span><\/h2>\n

Migrating information from one network to another used to be a tedious affair. The software-defined solution makes it easier so that you don\u2019t have to ask your technicians to pull out cables and other hardware since SD-WANs are designed to operate on top of what\u2019s already in place. Before the migration begins, an assessment will be done the network to see what devices comprise the architecture and what connections are used to support it.<\/p>\n

\"SD-WAN<\/div>\n

SD-WAN Migration Steps<\/h3>\n

SD-WAN deployment<\/a> options give organizations to deploy to branch offices and remote sites quickly either as physical appliances or software. Before beginning the migration process, leadership will need to work with their IT staffs and following these ten steps to ensure the network transitions goes smoothly:<\/p>\n

    \n
  1. \n
      \n
    1. \n

      SD-WAN Readiness<\/h4>\n

      Determine what applications are using the most throughput within your network and which of them will be given priority. This includes traffic flows and patterns, any cloud services that are being utilized, SaaS applications, and how to tie them all together into a unified platform.<\/li>\n

    2. \n

      Assess Access Types<\/h4>\n

      Not all access types are created equal. Simply chaining together different connections will not create an efficient network. You will need to have your teams assess the quality and capabilities of your access lines to ensure that your\u2019s organization\u2019s expectations are met.<\/li>\n

    3. \n

      Assess How the SD-WAN Will Integrate into Your Current Network<\/h4>\n

      SD-WANs doesn’t necessarily cover the entirety of the network in terms of functionality. Consider how to integrate the SD-WAN into your infrastructure when designing the network. This will help you assess protocol and application use, while providing a grounded understanding of bandwidth and protocol.<\/li>\n

    4. \n

      Find Out if SD-WAN Will Mesh with Your Cloud Strategy.<\/h4>\n

      Validate that your SD-WAN will work with the clouds you chose such as Amazon Web Services or Microsoft Azure. Some of the software-defined solutions will only create paths to public cloud providers through a local internet breakout, others through hub-style breakouts. Some of the solutions may not be fully optimized for performance or latency. In addition, they may support only a limited number of cloud providers.<\/li>\n

    5. \n

      Mapping Out Connectivity Flows<\/h4>\n

      Finding out how your connections flow within your network is essential to configuring policies for the SD-WAN. This ensures that application throughout is distributed fairly based on those policies. Be clear on your bandwidth, routing, and performance requirements for your applications.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

      \"SD-WAN<\/div>\n
        \n
      1. \n

        Keeping Best Practices and Aecurity Policies Up to Date<\/h4>\n

        Use this opportunity during the design and test portion of your deployment to test applications against current and future compliance or corporate security policies. By using SD-WAN, you\u2019ll be able to leverage the capabilities of the public internet. At the same time, not having the proper mechanisms in place when using it can expose your network to different cyber attacks.<\/li>\n

      2. \n

        While Planning your Migration, Consider Executing a Pilot Test<\/h4>\n

        Launching a pilot test for your network gives you opportunities to iron out any potential issues or flaws that may come up. Determine if the network\u2019s design is utilizing the correct access types for your network and support the priorities of your applications.<\/li>\n

      3. \n

        Site Priority and Applications for Migration<\/h4>\n

        Give priority to applications and sites that will benefit the most from the transition to the SD architecture. You\u2019ll need to think about key locations within your network as well as where applications are hosted. This will give you a better idea on how to design your migration plan.<\/li>\n

      4. \n

        Monitor Your Network During the Deployment Process<\/h4>\n

        Validating and verifying that the solution will be necessary to see how the network performs when stressed. You should also have the ability to monitor remote site traffic and leverage private and public connections in active-active mode. Ensure that your most critical traffic traverse the most stable paths within your WAN, while low-priority traffic utilizes cost-effective routes.<\/li>\n

      5. \n

        Efficient Network Monitoring<\/h4>\n

        Use the data from your SD-WAN\u2019s monitoring systems to give full visibility for your application and WAN performance.<\/li>\n<\/ol>\n

        <\/span>How Can Businesses Minimize Downtime During SD-WAN Migration?<\/span><\/h2>\n

        Businesses can minimize downtime during SD-WAN migration by maintaining appropriate fallback connectivity, testing critical applications before cutover, scheduling controlled deployment windows, and establishing clear rollback procedures. These measures help reduce the likelihood that network changes will interrupt customer-facing applications, internal operations, or communication systems.<\/p>\n

        For enterprises with distributed offices, even a short connectivity disruption can affect employee productivity, transaction processing, customer service, and access to centralized business applications.<\/p>\n

        Maintain Redundant Connectivity During Transition<\/h3>\n

        Where technically and commercially feasible, retain an existing WAN connection while deploying and validating the new SD-WAN environment. Redundant connectivity can provide an alternative path if the primary connection fails or the new configuration encounters problems.<\/p>\n

        However, redundancy alone does not guarantee uninterrupted service. Businesses must test routing convergence, failover behavior, application session recovery, and how existing and new network paths interact.<\/p>\n

        Test Business-Critical Applications Before Cutover<\/h3>\n

        Identify applications that require reliable connectivity, including enterprise resource planning (ERP), customer relationship management (CRM), voice and video conferencing, and cloud-based business platforms.<\/p>\n

        Test application access, authentication, DNS resolution, routing, security inspection, and traffic prioritization before moving production workloads. Where possible, perform these tests from representative branch locations.<\/p>\n

        Schedule Migration During Approved Change Windows<\/h3>\n

        Coordinate migration activities with business stakeholders and application owners. Select maintenance windows that minimize operational impact, particularly for locations supporting round-the-clock operations.<\/p>\n

        Communicate expected changes, affected locations, support contacts, escalation procedures, and contingency arrangements before deployment begins.<\/p>\n

        Establish Clear Rollback Criteria<\/h3>\n

        A rollback plan should identify the technical and operational conditions that require the team to restore the previous configuration or redirect traffic to an alternative path.<\/p>\n

        Potential triggers include persistent application failures, unexpected routing behavior, security policy violations, or performance degradation beyond agreed thresholds.<\/p>\n

        Document who can authorize rollback, how to restore the previous configuration, and how to verify service recovery.<\/p>\n

        Monitor Network Performance After Migration<\/h3>\n

        Continue monitoring network health after cutover. Track latency, jitter, packet loss, tunnel status, availability, failover events, and application performance.<\/p>\n

        Compare these results with pre-migration baselines and investigate significant deviations. Proceed with each migration wave only after the agreed acceptance criteria are met.<\/p>\n

        By combining phased deployment, application validation, redundancy, and rollback planning, businesses can reduce migration risk without assuming they can eliminate all disruptions.<\/p>\n

        <\/span>What Are the Common Risks of SD-WAN Migration and How Can Businesses Mitigate Them?<\/span><\/h2>\n

        SD-WAN migration can introduce risks involving application performance, routing, security, interoperability, connectivity, and operational readiness. Businesses can reduce these risks through infrastructure assessments, controlled pilots, documented change management, and post-migration validation.<\/p>\n

        Identifying risks before implementation helps enterprise IT teams protect critical business services and avoid unexpected remediation costs.<\/p>\n

        Application Performance Degradation<\/h3>\n

        Applications may experience latency, jitter, packet loss, or inconsistent performance if traffic policies do not reflect actual business requirements.<\/p>\n

        Mitigation<\/strong>: Establish baseline performance measurements, classify critical applications, configure appropriate traffic prioritization, and validate application behavior under normal and degraded network conditions.<\/p>\n

        Routing and Connectivity Errors<\/h3>\n

        Incorrect routing policies, overlapping IP address ranges, tunnel configuration errors, or unexpected interactions between legacy and new infrastructure can interrupt connectivity.<\/p>\n

        Mitigation<\/strong>: Review routing dependencies before migration, test configurations in a pilot environment, validate primary and secondary paths, and maintain a documented rollback procedure.<\/p>\n

        Security Policy Gaps<\/h3>\n

        Changes to internet breakout, traffic routing, segmentation, or centralized policy management can introduce security gaps if controls are not mapped correctly.<\/p>\n

        Mitigation<\/strong>: Review firewall rules, encryption requirements, identity-based access, segmentation, and inspection policies. Validate security controls before moving production traffic and document approved exceptions.<\/p>\n

        Legacy Infrastructure and Compatibility Issues<\/h3>\n

        Older routers, firewalls, applications, and network configurations may not support the required SD-WAN capabilities or may require upgrades.<\/p>\n

        Mitigation<\/strong>: Complete an inventory and compatibility assessment, identify unsupported configurations, and plan necessary hardware, software, and licensing changes before deployment.<\/p>\n

        Business Disruption During Cutover<\/h3>\n

        Unexpected dependencies or incomplete testing can disrupt applications when traffic moves to the new network.<\/p>\n

        Mitigation<\/strong>: Use phased migration, approved maintenance windows, representative pilot locations, application testing, and explicit rollback triggers.<\/p>\n

        Inadequate Monitoring and Operational Readiness<\/h3>\n

        If monitoring, alerting, documentation, and escalation procedures are incomplete, a team may deploy a network but struggle to support it.<\/p>\n

        Mitigation<\/strong>: Define operational ownership before deployment. Validate dashboards, alert routing, incident handling, configuration records, and support responsibilities in each migration wave.<\/p>\n

        Budget and Project-Schedule Overruns<\/h3>\n

        Unexpected circuit requirements, equipment replacements, licensing costs, or coordination delays can increase implementation costs.<\/p>\n

        Mitigation<\/strong>: Develop a realistic migration budget, confirm supplier dependencies, document contract obligations, and maintain contingency allowances for identified risks.<\/p>\n

        Businesses should maintain a migration risk register that records each risk, its potential business impact, mitigation measures, responsible owner, and current status. Reviewing this register throughout implementation helps project teams prioritize unresolved issues and make informed deployment decisions.<\/p>\n

        <\/span>How Should Businesses Choose an SD-WAN Migration Provider?<\/span><\/h2>\n

        Businesses should choose an SD-WAN migration provider based on its ability to assess existing infrastructure, design the target architecture, manage deployment risks, coordinate multiple locations, validate application performance, and provide appropriate post-migration support.<\/p>\n

        The right provider should align its delivery model with the organization’s network complexity, security requirements, operational resources, and long-term connectivity strategy.<\/p>\n

        Evaluate Assessment and Planning Capabilities<\/h3>\n

        A qualified provider should assess existing circuits, network devices, application dependencies, site readiness, and connectivity requirements before proposing a migration plan.<\/p>\n

        Ask how the provider identifies migration risks, prioritizes locations, estimates implementation effort, and establishes measurable success criteria.<\/p>\n

        Review Deployment and Rollback Methodology<\/h3>\n

        Confirm that the provider follows a documented implementation process covering pilot testing, configuration validation, phased deployment, change approvals, cutover, and rollback.<\/p>\n

        Ask how it handles failed migrations, unexpected application behavior, and connectivity issues during deployment.<\/p>\n

        Assess Security and Compliance Requirements<\/h3>\n

        The provider should understand the organization’s requirements for encryption, segmentation, access control, firewall integration, traffic inspection, and security monitoring.<\/p>\n

        Businesses in regulated industries should also determine how the proposed architecture supports applicable internal controls and regulatory obligations. Explicitly document responsibility for each security control.<\/p>\n

        Verify Multi-Site Implementation Experience<\/h3>\n

        Enterprises with multiple branches need coordinated deployment planning, consistent configuration management, and clear communication across locations.<\/p>\n

        Evaluate the provider’s ability to manage site dependencies, coordinate internet and MPLS vendors, schedule change windows, and maintain visibility into each migration wave’s progress.<\/p>\n

        Examine Monitoring and Ongoing Support<\/h3>\n

        Determine whether the provider’s responsibilities end at deployment or include ongoing monitoring, incident management, troubleshooting, configuration changes, and performance reporting.<\/p>\n

        Clarify service coverage, escalation procedures, support hours, reporting frequency, and any service-level commitments.<\/p>\n

        Compare Total Cost and Contractual Scope<\/h3>\n

        Evaluate the complete cost of migration, including assessment, design, hardware, licensing, circuit changes, implementation, training, and ongoing support.<\/p>\n

        Compare proposals using the same scope and assumptions. Confirm exclusions, customer responsibilities, dependencies, project milestones, acceptance criteria, and any recurring management charges.<\/p>\n

        The most suitable provider is not necessarily the one offering the lowest initial price. It is the one whose technical capabilities, implementation methodology, operational accountability, and commercial terms align with the organization’s business objectives.<\/p>\n

        <\/span>What Factors Affect the Cost of SD-WAN Migration?<\/span><\/h2>\n

        The cost of SD-WAN migration depends on the number of locations, existing network infrastructure, hardware requirements, connectivity options, licensing, implementation complexity, and ongoing operational support. Businesses should evaluate both one-time migration expenses and recurring costs to understand the total cost of ownership.<\/p>\n

        A structured cost assessment helps procurement and IT teams compare migration approaches, identify hidden dependencies, and determine whether the expected operational benefits justify the investment.<\/p>\n

        1. Number of Locations and Network Complexity<\/strong>
        \nMigrating a small number of standardized branches generally requires less coordination than migrating hundreds of locations with different routers, firewalls, circuit providers, and application dependencies.<\/p>\n

        Multi-site enterprises should account for site surveys, deployment scheduling, configuration differences, travel where required, and coordination with local teams.<\/p>\n

        2. Hardware and Infrastructure Upgrades<\/strong>
        \nExisting routers, firewalls, and other network devices may require replacement or upgrades to support the target SD-WAN architecture.<\/p>\n

        Costs can include appliances, power and rack requirements, installation, compatibility testing, and equipment deployment across branch locations.<\/p>\n

        3. Connectivity and Circuit Charges<\/strong>
        \nBusinesses may need new broadband, dedicated internet access, or cellular connections while retaining MPLS circuits during the transition.<\/p>\n

        The migration budget should account for installation charges, recurring connectivity fees, overlapping circuit costs, contract termination conditions, and any temporary dual-running period.<\/p>\n

        4. Software Licensing and Security Integration<\/strong>
        \nSD-WAN licensing costs depend on the selected platform, features, subscription model, and number of sites or devices.<\/p>\n

        Additional expenses may arise from security integration, centralized management, monitoring, reporting, and integration with existing network or security systems.<\/p>\n

        5. Assessment, Design, and Implementation<\/strong>
        \nMigration services may include network assessment, architecture design, configuration, pilot deployment, production cutover, testing, documentation, and project management.<\/p>\n

        Complex environments may require additional engineering effort to address legacy configurations, application dependencies, routing changes, and security requirements.<\/p>\n

        6. Training and Operational Support<\/strong>
        \nIT teams may require training to operate the new environment, interpret monitoring data, troubleshoot connectivity issues, and manage configuration changes.<\/p>\n

        Businesses should also consider ongoing managed support, monitoring, maintenance, incident response, and provider management costs.<\/p>\n

        7. Downtime Risk and Contingency Planning<\/strong>
        \nInsufficient planning can increase migration costs through business disruption, emergency remediation, repeated site visits, or delayed project completion.<\/p>\n

        Investing in pilot testing, change management, rollback planning, and post-cutover validation can help reduce these risks, although it cannot eliminate them.<\/p>\n

        <\/span>How Should Businesses Estimate the Total Cost?<\/span><\/h2>\n

        A practical migration budget should separate one-time and recurring expenses.<\/p>\n

        \n\n\n\n\n\n\n\n\n
        Cost category<\/strong><\/td>\nExamples<\/strong><\/td>\n<\/tr>\n<\/thead>\n
        One-time costs<\/td>\nAssessment, design, hardware installation, configuration, migration services, training<\/td>\n<\/tr>\n
        Recurring costs<\/td>\nConnectivity, SD-WAN licensing, monitoring, managed support, maintenance<\/td>\n<\/tr>\n
        Transition costs<\/td>\nOverlapping MPLS and internet circuits, temporary resources, contract-related charges<\/td>\n<\/tr>\n
        Contingency<\/td>\nAdditional remediation, unexpected compatibility issues, delayed deployment<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

        Businesses should compare the total cost of ownership over a defined planning period rather than evaluating only the initial implementation quote. The comparison should use consistent assumptions for site count, service scope, contract duration, connectivity, and ongoing support.<\/p>\n

        Actual costs vary significantly by architecture, provider, and business requirements. Organizations should obtain a scope-based estimate rather than rely on a generic price as a universal benchmark.<\/p>\n

        Examples of Migrating SD-WAN<\/h3>\n

        Some of the case examples of organizations migrating from traditional WANs to SD-WANs include:<\/p>\n

          \n
        • Intuit’s transition to a hybrid SD-WAN: the company utilizes both traditional WAN connections along with the failover capability of SD-WANs.<\/li>\n
        • A South American ISP utilized a transoceanic network connection to migrate data between Brazil and Miami.<\/li>\n
        • A Tier 1 provider migrates data via SD-WAN by optimizing utilization of capacity, while reducing network costs at the same time.<\/li>\n<\/ul>\n
          \"SD-WAN<\/div>\n

          SD-WAN Branches to the Data Center<\/h4>\n

          The SD architecture utilizes the unified connection embedded within the network to connect to the data center.<\/p>\n

          Branch Firewall<\/h4>\n

          Each branch office will have localized firewalls to monitor for any malicious traffic that attempts to infiltrate the network and respond accordingly.<\/p>\n

          Existing MPLS WAN with SD-WAN Offload<\/h4>\n

          The software-defined solution allows the use of existing network connections to offset bulk data throughout that traverses between location.<\/p>\n

          Secure and Optimized Communication Between SD-WAN Branches<\/h4>\n

          Communications between the branch offices, remote sites, and their headquarters occur via the use of end-to-end connectivity and network zoning. This helps in ensuring that multiple sites are secure from external threats.<\/p>\n","protected":false},"excerpt":{"rendered":"

          SD-WAN Migration Overview and How It Works Migrating information from one network to another used to be a tedious affair. The software-defined solution makes it easier so that you don\u2019t have to ask your technicians to pull out cables and other hardware since SD-WANs are designed to operate on top of what\u2019s already in place. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-111","page","type-page","status-publish","hentry"],"acf":[],"yoast_head":"\nSD-WAN Migration Overview and How It Works | ExterNetworks<\/title>\n<meta name=\"description\" content=\"Learn how to streamline your SD-WAN migration in 2026. Discover our expert overview on how it works and the steps to ensure a seamless network transformation.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SD-WAN Migration Overview and How It Works | ExterNetworks\" \/>\n<meta property=\"og:description\" content=\"Learn how to streamline your SD-WAN migration in 2026. Discover our expert overview on how it works and the steps to ensure a seamless network transformation.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/\" \/>\n<meta property=\"og:site_name\" content=\"SD-WAN\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-02T13:03:33+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.extnoc.com\/sd-wan\/wp-content\/uploads\/2023\/02\/sd-wan-migration-2.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"800\" \/>\n\t<meta property=\"og:image:height\" content=\"450\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"SD-WAN Migration Overview and How It Works | ExterNetworks\" \/>\n<meta name=\"twitter:description\" content=\"Learn how to streamline your SD-WAN migration in 2026. Discover our expert overview on how it works and the steps to ensure a seamless network transformation.\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/www.extnoc.com\/sd-wan\/wp-content\/uploads\/2023\/02\/sd-wan-migration-2.jpg\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"12 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"SD-WAN Migration Overview and How It Works | ExterNetworks","description":"Learn how to streamline your SD-WAN migration in 2026. Discover our expert overview on how it works and the steps to ensure a seamless network transformation.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/","og_locale":"en_US","og_type":"article","og_title":"SD-WAN Migration Overview and How It Works | ExterNetworks","og_description":"Learn how to streamline your SD-WAN migration in 2026. Discover our expert overview on how it works and the steps to ensure a seamless network transformation.","og_url":"https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/","og_site_name":"SD-WAN","article_modified_time":"2026-11-02T13:03:33+00:00","og_image":[{"width":800,"height":450,"url":"https:\/\/www.extnoc.com\/sd-wan\/wp-content\/uploads\/2023\/02\/sd-wan-migration-2.jpg","type":"image\/jpeg"}],"twitter_card":"summary_large_image","twitter_title":"SD-WAN Migration Overview and How It Works | ExterNetworks","twitter_description":"Learn how to streamline your SD-WAN migration in 2026. Discover our expert overview on how it works and the steps to ensure a seamless network transformation.","twitter_image":"https:\/\/www.extnoc.com\/sd-wan\/wp-content\/uploads\/2023\/02\/sd-wan-migration-2.jpg","twitter_misc":{"Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/","url":"https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/","name":"SD-WAN Migration Overview and How It Works | ExterNetworks","isPartOf":{"@id":"https:\/\/www.extnoc.com\/sd-wan\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/#primaryimage"},"image":{"@id":"https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/#primaryimage"},"thumbnailUrl":"https:\/\/extnoc.com\/sd-wan\/wp-content\/uploads\/2022\/06\/sd-wan-migration-1-2.jpg","datePublished":"2019-02-28T09:28:15+00:00","dateModified":"2026-11-02T13:03:33+00:00","description":"Learn how to streamline your SD-WAN migration in 2026. Discover our expert overview on how it works and the steps to ensure a seamless network transformation.","breadcrumb":{"@id":"https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/#primaryimage","url":"https:\/\/extnoc.com\/sd-wan\/wp-content\/uploads\/2022\/06\/sd-wan-migration-1-2.jpg","contentUrl":"https:\/\/extnoc.com\/sd-wan\/wp-content\/uploads\/2022\/06\/sd-wan-migration-1-2.jpg"},{"@type":"BreadcrumbList","@id":"https:\/\/www.extnoc.com\/sd-wan\/sd-wan-migration\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.extnoc.com\/sd-wan\/"},{"@type":"ListItem","position":2,"name":"SD-WAN Migration"}]},{"@type":"WebSite","@id":"https:\/\/www.extnoc.com\/sd-wan\/#website","url":"https:\/\/www.extnoc.com\/sd-wan\/","name":"SD-WAN","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.extnoc.com\/sd-wan\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"}]}},"_links":{"self":[{"href":"https:\/\/www.extnoc.com\/sd-wan\/wp-json\/wp\/v2\/pages\/111","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.extnoc.com\/sd-wan\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.extnoc.com\/sd-wan\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.extnoc.com\/sd-wan\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.extnoc.com\/sd-wan\/wp-json\/wp\/v2\/comments?post=111"}],"version-history":[{"count":5,"href":"https:\/\/www.extnoc.com\/sd-wan\/wp-json\/wp\/v2\/pages\/111\/revisions"}],"predecessor-version":[{"id":546,"href":"https:\/\/www.extnoc.com\/sd-wan\/wp-json\/wp\/v2\/pages\/111\/revisions\/546"}],"wp:attachment":[{"href":"https:\/\/www.extnoc.com\/sd-wan\/wp-json\/wp\/v2\/media?parent=111"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}