Essentials for Office 365 2.14 - User Guide

Copy SharePoint Online to SharePoint Online

A simple Administrator driven wizard is provided to bulk migrate the Documents library content from the Source SharePoint Online into the appropriate Target SharePoint Online Documents library.  In order to successfully configure and run this operation, you will need to be able to authenticate against both SharePoint Admin Center portals in Office 365 using a Global Administrator login.  A mapping file may also be needed in order to resolve the user accounts between the source and destination tenants.

This operation has the following requirements for use:

·The account used to perform the migration needs to be at minimum a SharePoint Admin for the source Office 365 tenant.

·The account used to perform the migration needs to be at minimum a SharePoint Admin for the target Office 365 tenant.

·The person performing the migration will need to know the relationship (user mapping) between the user accounts in the source and target Office 365 tenants.

·Each user account must have either a SharePoint Online license assigned to it in Office 365.
 

Once the requirements above are satisfied, you can proceed with utilizing the bulk upload functionality.

1. Switch to the Drives tab in the Essentials console and click the button "Copy Tenant" located in the ribbon, and select Copy SharePoint Online to SharePoint Online.

2. When the wizard appears, select a Profile and give your project a name.

3. Enter a SharePoint Admin Center URL for the source Office 365. Once the URL is entered, click the Connect (or Claims) button, enter a valid Admin account and click Connect.

When you receive a successful connection message proceed to the next parameter. You may also choose to add Admin account by selecting the "+Admin" button.

4. Enter a SharePoint Admin Center URL for the target Office 365.  Once the URL is entered, click the Connect button, enter a valid Admin account and click Connect.

When you receive a successful connection message proceed to the next step. You may also choose to add additional Admin account by selecting the "+Admin" button.

5. Click the Load from Tenant button or Load From CSV. Note that Load from CSV will allow you to load users from a CSV file, which is the faster option as only the listed users are loaded (see the user mapping report section for details on how to create a user mapping report).
 
In the table, a list of currently provisioned SharePoint Site Collections will be loaded. Select the site Collection you wish to migrate, and click Next.

6. This operation will automatically check for sites, if a target URL is greyed out, it does not exist and will be created for you. You will also be able to see if there are any language conflicts (whether your sites are set up in different languages)

7.You can choose to remap your source site collections to specified target site collections by selecting Remap. This will allow you to use a saved CSV file for remapping to a specific site on the target. The following is a CSV example:
 
https://source.sharepoint.com/sites/old site URL,https://target.sharepoint.com/sites/new site URL
 
Once your CSV has uploaded you can select Check for Sites to recheck whether target sites exist based on your mapping csv - once your mapping is visible, click Next to continue.

8.The final page provides a few options to configure how the content portion of the operation should be configured.

 
Content Options

Convert to Modern Site Template - Enable this option if you are migrating a classic Team Site (STS#0) that you want to be converted to a modern Team Site (STS#3) on the target.  If you do not check this box, the site will retain the classic Team Site template.

 
Copy Sub-Sites - Enable this option to include all sub-sites of the current site in this operation.

Copy Features- This option will transfer site level feature settings from the source to the target site.
 
Copy Workflows - This option allows you to copy SharePoint Out-of-Box Workflows, SharePoint Designer Workflows, and Nintex Workflow .
Note:
- Workflows may have a reference on images, columns, files, lists, sites, etc. These objects should be copied with Workflows or be created/copied before Workflow migration.
- The Nintex Workflow must be installed before the migration
 
Copy Forms  - this option allows you to copy Classic Nintex Forms.
Note:
- The Nintex App must be installed before the migration
- Domains must be updated during the migration
- Rules must be preserved
- Collection to columns must be preserved
- The form must be published after migration
 
Copy Navigation - selecting this option will copy quick launch settings and top link bar settings from your source site to your target site, both for new and existing sites, for Modern and Classic team sites.  Note, that when enabled this setting works in 'replace mode', meaning it will delete all quick launch and top link bar settings on the target, and replace them entirely with the settings from the source - this means that if you have custom settings or libraries that do not exist on the source, these settings will be lost on the target.
 
Overwrite if file exists - In a version library, selecting the "Overwrite if File Exists" option does not overwrite the files already in SharePoint. SharePoint will append these to the list as new versions.

Incremental Copy - Incremental or delta migrations are an important and powerful option for large or ongoing projects and migration validation. Once enabled this option will migrate new, modified or versioned content from the source to the destination, capturing changes made by users during the previous migration. The value entered into the "Last" field will limit the amount of content examined to the time period specified, starting at present time. To perform an incremental migration, enter the amount of time to include and select the appropriate time period in days, weeks or months. Incremental migration is designed to be used in scenarios where the destination is not being modifed. To perform a delta migration, enter zero in the field and select days as the time period. Delta migration is designed to be used in scenarios where both the source and destination may be modified during the course of the migration. Please note that a delta migration compares dates between source and destination to determine which content to include, so it will take more time to process than an incremental migration.

Skip files greater than - When enabled, this option will skip any source files that are greater than the value specified (in MB or GB). An entry will be added to the post-migration log indicating which file(s) were skipped due to this configuration.
 
Re-Map Users - This option will allow you to map users between different domains or to change the user account in the target environment during copy.
 
Apply Filter - This feature allows the inclusion or exclusion of items by user defined criteria, such as date, size, file extension, file name, or file owner.
 
Note: the Apply Filter functionality is only applied to selected containers (i.e. site, lists or folders). If you select specific content (documents or items) then those objects will be included with the operation regardless of the filter applied. If you want to selectively include content, please select the container that this content resides in and apply the filter or apply the filter against the container first, then select the remaining content.
 
For the File Extension and Exclude Folders parameters only, you can use "," to set more than 1 criteria. For example, use this format "png,docx,pptx" to include multiple file extensions.
 
"Size" filter should have a whole number without decimals. It  is recommended that users not use the operators "Equal" and "Not Equal" to avoid difficulties with accurate file size, if the file size is greater than 1 MB.
 
Use the "Save Filter" option to save filter settings to a file and load them in different wizards or the Profile Manager.

Advanced Options

Enable Azure Turbo Mode: When enabled, this option utilizes Microsoft's SharePoint Online Migration API to increase the migration performance and throughput. A recommendation for optimal use of this API is larger sets of data; the more content, the better the throughput. Please review the User Manual for additional information as well as recommended configuration as this process is a resource intensive operation.

Because this API uses Azure storage as a staging area for the migration, it requires that you provide an Azure storage location. The options are to either utilize Microsoft supplied storage or to provide your own Azure storage location. If you wish to use your own Azure account, you must provide both the Azure Account Name as well as the corresponding Acces Key. If you cannot supply this information, please search our online Knowledge Base, User Manual or contact Support for additional information before proceeding or consider using the Microsoft Supplied Storage option. For more information please see the Azure Turbo Mode section.

·Microsoft Provided Storage: This option allows you to use Microsoft provided Azure storage instead of providing your own for the purpose of utilizing Azure Turbo Mode.

·User Provided Storage: This option allows you to provide your own Azure Storage instead of using one provided by Microsoft for the purpose of utilizing Azure Turbo Mode. It requires that you provide both your Azure Blob Storage Account Name as well as its corresponding Access Key by clicking the "Select" button to the right. If you cannot supply this information, please search our online Knowledge Base, User Manual or contact Support for additional information before proceeding.

Send Notification: When selected, this feature will send emails to the listed recipients once Migrations are completed. Enter a specific user email address. For two or more, separate each email address with a comma. Set up User Notifications here in order to use this feature. 

11. Click Finish to begin the migration.

Copy Box

Essentials for Drives provides a simplified, wizard driven experience to migrating content in, out, or between various drive management systems (local or cloud based).  It can also provide additional functionality to managing some or all OneDrive for Business sites within a specific Office 365 tenant.

Copy Box to OneDrive for Business

This option allows Box and Office 365 administrators to copy content from within multiple Box Drives to their respective OneDrive for Business sites in a single migration.

This operation has the following requirements for use:

·The account used to perform the migration from Box needs to have Full Enterprise Admin access to the Box tenant.

·The account used to perform the migration into OneDrive for Business needs to be a minimum of Site Collection Administrator Role in this Office 365 tenant.

·The person performing the migration will need to know the relationship (user mapping) between each user's Box user account and their corresponding Office 365 user account.

·Each user account must have either a SharePoint or OneDrive license assigned to it in Office 365 and can not be in  a 'Blocked' state.

Once the requirements above are satisfied, you can proceed with your Box to OneDrive for Business migration.

1.Switch to the Drives tab and click the "Copy Box" option and select the Copy Box to OneDrive button.

2.Give your project a name.

3.Enter the username of your Box Administrator and click Connect.

4.When the popup appears, enter this Admin account's password and click Connect.  Then "Grant access to Box" and you will return back to the migration configuration where a "Successfully connected to Box" message will appear.

5.In the Target Office 365 Connection Parameters section, specify your tenant SharePoint Administration Center URL and then click Connect (i.e. https://tenant-admin.sharepoint.com).  When prompted, enter your Office 365 Global Administrator or SharePoint Administrator login and password. Click Connect.  If you receive any message other than Successfully connected to SharePoint Admin, double check the URL and make sure you are supplying a Global Administrator or SharePoint Administrator login for this tenant.  If you are still experiencing issues, please contact Support for further assistance.

6.Click the "Load from Box" button to load in a list of available Box drives to include with this migration.  For performance reasons, if you have a large number of Box drives in your tenant you may wish to create a single column CSV file with the user accounts and choose the option "Load from CSV" instead.  

7.Select the Box drives that you wish to include with this migration, or select the Load and Apply Report button, which allows you to load and apply an Analyze Box report, which then sets the Migration Priority for each user mentioned in the report. Click Next to continue.

8.Select Re-Map Users option and load a user mapping CSV file.  User mapping is required so the software can properly resolve the differences between your users' Box and Office 365 accounts. Please see the User Mapping section if you require further instructions on creating a CSV file for user mapping.

9.Click Check for users personal sites in order to begin the validation process. This process will validate that the supplied user mapping is correct (Office 365 user accounts were located) and check to determine if each user currently has a OneDrive for Business for site provisioned.  If any of the valid users do not have a OneDrive for Business site currently provisioned,  you can select them and check Create personal sites for the selected users option.

10.Click Next to continue.

11.The final page provides a few options to configure how the content portion of the operation should be configured.
 
Content Options

Copy Content - A flag to determine if content is or is not included with this operation.  When not included the remainder of the options will become disabled.

Include Versions - The process in which Box version history will be converted into OneDrive for Business versions.

Incremental Copy - When enabled, the migration process will identify and migrate only that content which was created, modified or versioned within the defined interval (days, weeks or months).

Copy Permissions - Will convert Box permissions (known as Collaborators) into OneDrive for Business permissions.

Skip Non-Owned Folders - This option addresses the scenario where folders appear in a user's Box account which are not owned by this user; meaning the user is a folder collaborator and not the folder "Owner".  Skipping these folders will prevent duplicates from being migrated into OneDrive for Business because the folder will be migrated only once when the folder "Owner" is migrated.  Please refer to the in-application Help button for additional details.

Skip Files Greater Than - When enabled, this option will skip any source files that are greater than the value specified (in MB or GB). An entry will be added to the post-migration log indicating which file(s) were skipped due to this configuration.
Migrate to Folder - When this option is enabled, you can create a (or use an existing) root folder structure in the destination library where your source content will be migrated. You will need to define the path like this example:

/My Source Content/2017

In the above example, the folder "My Source Content" and subfolder "2017" will be created in the root library of your destination and all source content will be migrated to this folder location.
 
Apply Filter:  Creates and assign any number of filter parameters to be used to include or exclude content from the upload process, including but not limited to file extensions, size and dates.

Advanced Options

Enable Azure Turbo Mode: When enabled, this option utilizes Microsoft's SharePoint Online Migration API to increase the migration performance and throughput. A recommendation for optimal use of this API is larger sets of data; the more content, the better the throughput. Please review the User Manual for additional information as well as recommended configuration as this process is a resource intensive operation.

Because this API uses Azure storage as a staging area for the migration, it requires that you provide an Azure storage location. The options are to either utilize Microsoft supplied storage or to provide your own Azure storage location. If you wish to use your own Azure account, you must provide both the Azure Account Name as well as the corresponding Acces Key. If you cannot supply this information, please search our online Knowledge Base, User Manual or contact Support for additional information before proceeding or consider using the Microsoft Supplied Storage option. For more information please see the Azure Turbo Mode section.

·Microsoft Provided Storage: This option allows you to use Microsoft provided Azure storage instead of providing your own for the purpose of utilizing Azure Turbo Mode.

·User Provided Storage: This option allows you to provide your own Azure Storage instead of using one provided by Microsoft for the purpose of utilizing Azure Turbo Mode. It requires that you provide both your Azure Blob Storage Account Name as well as its corresponding Access Key by clicking the "Select" button to the right. If you cannot supply this information, please search our online Knowledge Base, User Manual or contact Support for additional information before proceeding.

Create User Specific Log File - If you would like a user specific log file (.txt format) created for each migrated Google Drive, that will be saved directly to that Group's Documents library, check this option before you finish.  This log file will contain all the content that was included in the migration with both source and target URLs as well as any file renaming that took place and skipped files due to lack of ownership.
NOTE: Create user Specific log file is disabled if Azure Turbo Asynchronous mode is on. Supported only for CSOM or Azure Turbo Synchronous modes.

12. Click Finish to begin the migration.

Box - Group Mapping

This may be necessary when you have a Collaboration group assigned to a Box Folder that you want to translate into a Microsoft Entra ID group in your Office 365 environment.

Finding the Box Group to map:

1.In the Box application, right click on the shared folder which contains the group you want to map the Office 365 group from, and select Share>Manage Collaborators.

2.As is displayed in the following image, the group for this example is "Box Dev".

3.When migrating this as is (with no mapping) into OneDrive for Business, a SharePoint group will be created with the same name "Box Dev".

If you would like to translate this Box Group into a Microsoft Entra ID Group, we first need to locate the "Account" name of the Microsoft Entra ID group you would like to map the Box Group to. You can do this by following these steps:

1.On your SharePoint Online site or OneDrive for Business Site, select the cogwheel settings tab, and then click Site Settings.

2.Select "People and Groups" under User Permissions.

3.Click on the name of the Microsoft Entra ID group for which you wish to find the Account ID for user mapping.

4.The Microsoft Entra account ID will be the set of numbers and characters listed beside "Account". Copy this sequence.

 

Make a new entry in your User Mapping file for the Group

As you can see, use the information from the Box side on the leftmost column and use the information from your SharePoint side on the rightmost column. When you use this mapping file, your group should map from Box group to your existing group in OneDrive for Business.