Data Migration: Moving Your Organization’s Crown Jewels

I recently hosted an on-demand webinar in which I covered the technical details on performing data migrations using Code42. In past webinars and blog posts, we’ve talk about the benefits of using Code42 for migration—in other words, the WHY. But what we haven’t covered in-depth is the HOW.

In this webinar, I walk through the three main approaches in performing migrations. They are the self-service, Do-It-For-Me (DIFM), and the Do-It-With-Me (DIWM). The self-service migration utilizes the self-service wizard in the client and allows the user to migrate their settings (as of the 5.4 client) and files themselves to their new device. The DIFM method involves IT performing the migration on behalf of the user. The user simply hands in their old device and is immediately given their new device. Finally, the DIWM method is a combination of the two. IT works directly with the user in migrating the data, typically through the self-service wizard. Each has its pros and cons depending upon resources, time, geography, automation, etc.

When it comes to Windows migrations, we now support the migration of a user’s profile along with their data (as of the 5.0 & 4.4 clients). A user profile includes things like wallpaper, folder options, taskbar settings, etc. To do that, Code42 leverages the Windows User State Migration Tool (USMT). Why did Code42 choose to use that instead of building it directly in? Well, USMT gives you the power and flexibility to migrate nearly anything and is built by Microsoft themselves. I go into detail on exactly how to set that up, what’s best practice, and how to troubleshoot errors.

For the Do-It-For-Me migration, I walk through all the steps in detail on how an IT professional can perform the migration without the user needing to be present—in other words, a completely white-glove approach. And for organizations that are tasked with hundreds or thousands of these migrations, I point out the steps in the process that can be automated through the Code42 API.

Along with the approaches, I cover how to stay on top of devices that may have been orphaned from a migration process where the old device was not adopted. Throughout the webinar, I try to provide some helpful hints to help in your successful migration project, so I hope you will check it out today!