2017: The Year of Windows 10 Migrations

Next year will signal the beginning of mass Windows 10 migrations. While the operating system, which launched in July 2015, may seem like old news to some, Gartner predicts enterprise adoption will actually take off in 2017 and hit full force in 2020.

Why the delay in adoption? Survey results reveal stability, application compatibility and security concerns. But there’s another factor at play: 73 percent of large organizations plan to combine their move to Windows 10 with a device refresh—so they’ve been waiting for their next hardware purchase (which typically occurs every two to four years).

Productivity hit causes some users to drag their feet

Many users get excited when told they’re getting a new device—until they think about the downtime involved. Typically, data migrations leave users without their device for at least three hours, and sometimes for as much as a day. Since most users can’t be without their device for that length of time without warning, migrations require heavy IT planning. Users are often given scheduled time slots in which IT will make the switch.

The complication of user profile data—such as desktop wallpapers, fonts and shortcuts—only adds to the reluctance. In fact, losing user profile data has been cited as one of the major challenges facing organizations that are moving to Windows 10.

Code42 offers a new path to Windows 10 migration success: DIY—Not just DIFM

The traditional Do-It-For-Me (DIFM) migration path allows IT to provide a white-glove tech refresh experience, and hand end users a final product. Although this is a great path for small refresh projects or less technically inclined workforces, it quickly drains IT resources.

For this reason, Do-It-Yourself (DIY) migrations have gained favor as IT looks for ways to accommodate expectations of on-the-go and increasingly tech savvy users. A DIY method lets users drive their own refresh process by performing the file transfer themselves. This eliminates many of the scheduling challenges of a DIFM migration. The cherry on top: IT time savings.

Code42 is already renowned for speeding the typical DIFM tech refresh. In fact, customers report that Code42 CrashPlan has cut their migration time from three days to 30 minutes, shortened project timelines by eight weeks and caused them to ditch Windows Easy Transfer all together.

With the 5.4 release of Code42 CrashPlan, we have bolstered migration capabilities to support seamless DIY migration workflows. The Device Replacement Wizard walks end users through each step of transferring both their files and their Windows user profile settings to a new device. No more scheduling with IT. No more re-configuring preferences due to lost user profile data. IT can simply image the new device and install Code42 CrashPlan. After that, users follow the steps to restore their files—and just keep working.

Best Practices in Device Migration: Two Scalable Strategies

One response to “2017: The Year of Windows 10 Migrations

  1. These profile specifics are then replicated in the Windows 10 operating system the next time users log on. With this process, one client was able to complete 250 migrations in a single night.

Leave a Reply

Your email address will not be published. Required fields are marked *