More and more offices are switching to SDWAN systems due to its cost-efficiency, added security features, and scalability. And while all of these are true, simply switching to this kind of network at your office is not always a plug-and-play affair. While many SDWAN providers promise easy migration, you can’t discount the fact that each implementation is different, and so it’s best to be prepared.
Hence, here are some tips you can follow to ensure that your SDWAN migration is problem-free:
- Evaluate each site first.
If your company operates at multiple sites, it’s best to check the requirements for each individual site first. For example, a site may be marked as critical for the everyday operations of your company, and so you may need to keep your old leased line infrastructure as a backup connection. The reverse—having the SDWAN as some sort of backup or only implementing this kind of network for routing purposes—may be also true.
There’s also the fact that different sites may have different kinds of networks in place. One site may be still running on legacy digital lines, while another site may have two MPLS connections. Obviously, there would be different considerations during a site migration due to these concerns. Hence, it’s essential to evaluate sites on a case-by-case basis first before trying to implement an SDWAN solution.
- Check available broadband options.
Speaking of keeping leased lines as backup options, it’s also important to note which broadband options are actually available at each site. After all, should you decide to downgrade your current leased line subscription and use an SDWAN instead, you’ll need to evaluate if a downgrade is actually available with your current provider.
Otherwise, you may end up looking for an alternative plan, whether with your current provider or another ISP, that doesn’t exist. You may even discover that there are no other available ISPs in the area that your site’s operating in!
- Compute the cost.
SDWAN may be cost-efficient, but it’s not really cheap. Since it’s still a pretty new technology, some providers may charge a premium rate. Hence, before you switch, it’s important to crunch the numbers—for some sites, maybe it’s still better to stick to your old setup in the meantime.
- Go for a gradual roll-out.
Of course, with the three tips mentioned above, it’s easy to see that migrating to an SDWAN isn’t something you should stop all operations for it and expect to be done in a week. Hence, it’s better to do the migration site-by-site—starting with the less crucial ones to test the process first. That way, your team and your provider can iron out the kinks before trying to migrate the more critical sites. And once your less-crucial sites are up and running on an SDWAN network, you can migrate tasks to these sites while the critical locations are being upgraded. This ensures continued operation even during the entire migration.
With these tips, we hope that your company’s migration to an SDWAN system goes smoothly.