Planning a Cloud Migration

Overview

This Section covers what to consider when planning a migration project with OnRamp and recommended steps to make migrating user data to the cloud as efficient and painless as possible.

Project Considerations

Examining the basic conditions and available resources helps determine the best approach to a project. Aspects to consider include:

Number of Computers

Determining the number of computers to be migrated informs whether to automate extraction transfer to the cloud. OnRamp can handle manual or automated migration up to thousands of systems.

Networked Environment

In a networked environment, a central server may be used to store OnRamp and log files. Bandwidth limitations must also be taken into account. If no networked environment is available, OnRamp can be run on individual systems.

Cloud Storage Organization

Transferring files to the cloud is an opportunity to organize files and folders. OnRamp provides the means to transfer files of a certain type to a specific folder, or to keep current folder configurations in the cloud.

OnRamp Process Overview

  1. Install OnRamp in a central location (see Installing).
  2. Create one or more configuration files using the user interface (see Configuring).
  3. Run OnRamp on each desktop system where user data files should be transferred to the cloud. See the section on Automation for more information on how this can be automated.

Installing OnRamp

OnRamp supports a single installation on a server from which OnRamp is shared so it can be accessed and run from other systems. This is described in more detail in the section on Installing.

Choosing OnRamp Installation Location

Accessibility, and availability of a network connection are critical considerations in choosing where to install OnRamp. This location will store the application which needs to be accessible by each end-user whose files are to be transferred to the cloud. Additionally, log files which allow auditing by IT departments.

Alternatively, OnRamp can be installed on local machines. Computers which are not typically on the company network, such as laptops for traveling or remote employees, could be configured to run OnRamp locally.

Creating Configuration Files

The complexity of the migration to the cloud project determines how many configuration files are required. For a smaller project a single configuration file may cover all migration parameters and file rules. For a larger, more complex project, multiple configuration files may be required depending on the variety of file types, desired cloud folder structures and so on. Configuration options are described under Configuration, files rules, which are also stored in the configuration file, are discussed under File Rules, and Automating OnRamp explains how to specify configuration files in automation scenarios.

Transferring Data Files

Transferring user data to the cloud is performed on the user's PC. While transfers can be performed manually using OnRamp’s user interface, the rich command-line capabilities in OnRamp make it easy to integrate into any desktop management suite. The section Migrating to the Cloud describes the extraction user interface and the section Automating OnRamp provides a complete command-line reference.

In either case, the user will be prompted to log into their cloud account. In single sign on environments, the user is already logged into the cloud when the log onto their Windows Domain account and will therefore not be prompted.

Networked Environments

Overview

The most common scenario for using OnRamp is an environment with one or more Windows domains in which users are migrated from their Windows systems to the cloud. Usually migration occurs in conjunction with an corporate change in handling employee data, or in a move to Choose Your Own Device or Bring Your Own Device.

Cloud Configuration

Before users can move their data files to the cloud, the users must be provisioned to use the cloud. Users will need only their cloud account information, except in single sign on environments in which the user's are already logged into the cloud when they log on to their Windows machine.

Process

In order to make the migration process as efficient as possible, it’s possible to transfer data files to the cloud from multiple systems in parallel. OnRamp is flexible enough to transfer files while they are in use. However, it is advised the users save their files before this process to ensure the latest versions of their data are transferred.

The following process applies when using a networked environment:

  1. Install OnRamp to a network share, giving users 'Change' permissions to the share.
  2. While logged on to the machine as the user, navigate to the directory where the OnRamp files are located.
  3. Launch OnRamp.EXE
  4. Log into the user's cloud account within OnRamp.
  5. Run the migration.

Of course it’s also possible to create scripts to do the transfer to the cloud automatically. See Automating OnRamp for more information on using OnRamp from the command-line.

Local Installation

Overview

To migrate individual computers in a stand-alone manner, install OnRamp and store user log files on the user's system.

Installation

Install OnRamp to the user's system.

Process

The following process applies when using a networked environment:

  1. Install OnRamp to the user's machine.
  2. While logged on to the machine as the user, launch OnRamp.EXE
  3. Log into the user's cloud account within OnRamp.
  4. Run the migration.

Removable Media

Overview

To migrate individual computers from removable storage, such as in a crash cart process, install OnRamp and store user log files on removable storage (e.g. a USB flash drive, a USB hard drive, etc.).

Installation

The OnRamp installation program does not display removable devices as possible destination devices. It is necessary to specify the drive letter of the removable device in the installation path. Alternatively, if OnRamp is installed on a computer, the installation directory (with all of the sub-directories) can be copied to the removable device.

Process

The following process applies when using a removable storage device:

  1. Add the removable storage device containing OnRamp to the source system.
  2. Launch OnRamp.EXE from the removable drive.
  3. Log into the user's cloud account within OnRamp.
  4. Run the migration. Of course it’s also possible to create scripts to do the transfer to the cloud automatically. See Automating OnRamp for more information on using OnRamp from the command-line.