We capture the physical server
- We Start with the physical server and capture a virtual copy of it
- We then move the entire system to a temporary container
- Choose the container location (such as a network share, a NAS, a USB hard drive – any type of storage with enough space), and press Go to perform a full capture of the source server to that location.
Note: You do not have to capture all of the contents. You can exclude content you don’t want captured using the Advanced menu, saving space and – later- upload time.
Make the container accessible from the target server
- We discuss your options (AWS, AZURE, 3rd Party Hosted, Etc.) and pick our target container
- Once the container is created, we need to make it accessible from the target. This can be done either by uploading it to your desired cloud provider’s storage, or by setting up a VPN / tunnel connection between the servers.
Part 3: Deploy from the container into the Cloud
- If you do NOT want to transfer programs and are only interested in a profile, data, and shares transfer, switch the radio button on the main screen to “profile and settings only” mode.
- Specify the location of the container depending on which system you prefer (AWS, AZURE, Hosted)
- The transfer will take a while (depending on how much data you have to transfer), and report to you when done.
After the migration:
Once the migration process is complete, it is time to verify the results.
- You may need to adjust your domain’s DNS to point to the new server where needed. For example, changing the CRM-SERVER DNS entry to the new server’s address.
- The same goes for login scripts and GPO policy.
- Launch every application and console you use, and verify they load correctly.
- Using a client workstation, verify that clients can access the migrated server correctly and their applications run without issues.