This article explains how to configure your  migration platform to migrate on premises File systems to Office 365 (OneDrive, Sharepoint Online Library) or Azure Blob storage.

How it works:

A local agent runs on your on premises environment.

The agent periodically connects to the plaform on port SSL 443 and retrieves the migration jobs to run.

Prerequisites:

  • Requires dotnet framework 4.5 on the server where the agent is installed.

Steps:

Connect to the Cloudiway Migration Platform.

Step 1. Create the source and target connectors

Click on File Migration.

Cloudiway File System migration

Click on Source and create a File System OnPremises Connector.
Cloudiway File System migration

The connector doesn’t require any configuration.

The credentials under which the agent is running is the identity of the logged on user.

Cloudiway File System migration

Click on Target and create the target connector.

Cloudiway File System migration to Sharepoint online, onedrive or Azure Blob Storage

Note: Google Drive is not a supported target when local File system is used as source.

Step 2. Local agent setup

From the source connector, download the local agent (FILEAgent.zip) and its configuration file.

Prerequisites : Dotnet framework 4.5.

Unzip FILEAgent.zip and copy configuration.json in the same directory.

The agent will browse the file system  with the credentials of the logged on user.

  • On the server where the local agent will run, open a command prompt.
    • Navigate to the directory where you unzipped the local agent and run CIW.LocalAgent.exe

The agent is now up and running and ready to start migration jobs.

If you’re getting the error : Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object.

 
Cloudiway File Local Agent Error

On the folder where your unzipped the agent, right click engine.dll and click on properties.
Then click “Unblock”.
Cloudiway File Local Agent Solution

 

The local agent connects every minute to the platform and retrieves the tasks to execute.

Step 3. Platform Configuration

It’s now time to define your folders to migrate.
You can either create them manually or import them with a CSV file.

3.1 Define a migration job manually

On the File User list, click on Manage-> Single User

Fill the required fields.
To migrate a local folder, you can enter its path like c:\home\rh
To migrate a folder on the network, first map a share ( for example x:, s:) and define the path in the form s:\rh, etc…
Cloudiway File System migration

3.2 Define your migration jobs with a csv file

To automate the creation of your jobs, you can define them in a csv file and upload it.

Create an import file like this one:
FirstName;LastName;SourceEmail;TargetEmail;BatchName
user;one;h:\homeuser1;user1@target.com;week1
user;two;h:\homeuser2;user2@target.com;week1
On the computer where you will run the local agent, create your drive letter (in this sample it’s h:) that points to the root share.
for example : net use h: \\servername\share
The logged account will need to have permissions on all files.

Step 4. Migrate

Click on User List.

Select the lines.

Click on Migration -> Start

Click on Start
Cloudiway Sharepoint Onpremises migration

The migration should start with the minute.