OneDrive for Business is gaining recognition and traction among SMBs and enterprises. In particular, replacing user home drives, commonly stored on on-premises file shares, with OneDrive is becoming a common request to Office 365 system integrators and MSPs. As our partners have started to do more of these projects, some common roadblocks have become apparent:

More and more enterprise customers want to migrate their users’ Home drive, most often stored on File Servers, to the users’ One Drive for Business. But there are several hurdles:

• he structure of the File Servers is not in harmony with user names in Office 365.
• They do not want to migrate the complete File Servers structure.
• They are not aware of the limits in OneDrive for Business.

With MigrationWiz, you are able to migrate, but the migration process is different:

Step 1	Upload the files into an Azure Blob storage.
Step 2	Create a Project in MigrationWiz: Source is Azure, Destination is OneDrive for Business
Step 3	Filter the different Folders to migrate only the relevant data to the users’ OneDrive for Business.

Before you begin to upload, you must check all documents, determine if any limitation prevents these documents from being stored in OneDrive for Business. There are several articles about these limitations:

Restrictions and limitations …. sync SharePoint lib. to your computer through ODFB
Migrating File Shares to OneDrive for Business
SharePoint Online and OneDrive for Business: software boundaries and limits

So then you are able to identify the folders:

In the following example we only want to upload only 3002 and 3003 == User A and User B

File Server structure	Azure Blob container (after uploading)
FS\3001
FS\3001\doc1.docx
FS\3002\	FS\3002\
FS\3002\Doc21.docx	FS\3002\Doc21.docx
FS\3002\Doc22.docx	FS\3002\Doc22.docx
FS\3003\	FS\3003\
FS\3003\Subfolder1	FS\3003\Subfolder1
FS\3003\Subfolder1\Doc31.docx	FS\3003\Subfolder1\Doc31.docx
FS\3003\doc32.docx	FS\3003\doc32.docx
FS\3003\doc33.docx	FS\3003\doc33.docx
FS\3004
FS\3004\doc41.docx
FS\3005
…	Directory.metadata
	File.metadata

Only the folders and files (these are highlighted in yellow) should be uploaded to the Azure blob in the named container.

The Second part is the migration with MigrationWiz

The table below indicates what will be migrated into the OneDrive for Business document library destination:

User A	User B
Doc21.docx	doc32.docx
Doc22.docx	doc33.docx
	Subfolder1
	Subfolder1\Doc31.docx

So this can be done, using two CSV files and also two PowerShell cmdlets.

The first CSV file is the configuration file where several kinds of information will be stored:

FSConfig.csv	ProjectName	The Project Name in MigrationWiz.
	ContainerName	The container name of the blob storage in Azure. The container in this Azure blob storage must exist. (Only lowercase names are allowed)
	RootPath	The root path of the File Server.
	AccessKey	The name of the Azure Blob storage.
	SecretKey	The Security Key to access the Blob storage.
	ODFBAdmin	The email of the Office 365 Global administrator.
	Password	The Password of the Office 365 Global administrator.

In the second CSV file are stored users’ name and the corresponding File Server folder. Additionally, the Filter Folder and Folder Mapping must be saved.

Users.csv	DestinationEMail	Email address of the user, in which the ODFB data is stored.
	SourceFolder	The Subfolder of the File Server, which is mapped with the email address (User)
	FilterFolder	The RegEx for the User, which filters only the Subfolder and for the given user.
	FolderMapping	Filters the Folder.

If all data are saved in both CSV files, then we may execute the first PowerShell cmdlet with the name Uploader.ps1.

Now only the selected folders, subfolders and files are uploaded to the Azure Blob storage in the named container.

The second PowerShell cmdlet ProjectImport.ps1 creates the complete Project in MigrationWiz. You do not have to set any information. All information about the project (Source, Destination, container) and all users are inserted.

And now you ready to start the Migration with checking your credentials and then with a full migration.

Fore more information go to our community site at BitTitan