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.
These prerequisites are applied to the server (workstation) where the agent is running.
- .NET Framework version 4.5 or higher
- Install SharePoint Online Management Shell
- PowerShell permission policy is set up to RemoteSigned
To check a policy of your workstation, use the following cmdlet:
To set up a policy to RemoteSigned, execute the following cmdlet:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
Connect to the Cloudiway Migration Platform.
Step 1. Create the source and target connectors
Click on File Migration.
Click on Source and create a File System OnPremises Connector.
The connector doesn’t require any configuration.
The credentials under which the agent is running is the identity of the logged on user.
Click on Target and create the target connector.
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.
On the folder where your unzipped the agent, right click engine.dll and click on properties.
Then click “Unblock”.
The local agent connects every minute to the platform and retrieves the tasks to execute.
Note: if you still experience this error, try to unblock all agent’s dll by executing this command:
Get-ChildItem | Unblock-File
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…
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.
Step 4. Migrate
Click on User List.
Select the lines.
Click on Migration -> Start
Click on Start
The migration should start with the minute.