Essentials for Office 365 2.15 - User Guide

Copy Dropbox to Microsoft Teams

This option allows Dropbox Business and Office 365 administrators to copy content from within Dropbox Business drives to a Microsoft Teams site in a single migration.

This operation has the following requirements for use:

·The account used to perform the migration from Dropbox Business needs to have Team Admin access to the Dropbox Business tenant.

·The account used to perform the migration into Microsoft Teams needs to be a minimum of Site Collection Administrator in this Office 365 tenant.

·The person performing the migration will need to know the relationship (user mapping) between each user's Dropbox user account and their corresponding Microsoft Teams name and account.

·The Microsoft Team must already exist.

To migrate content of a Dropbox Business Account(s) to Microsoft Teams, perform the following:

1.On the Drives tab click Copy Dropox and select the "Copy Dropbox to Microsoft Teams" option.

2.Give your project a name.

3.Enter the username of your Dropbox Administrator.

4.Make sure Dropbox Business - Connection Requirements are met.

5.Use the information in the following table to determine the appropriate action to take.

If you receive any message other than Successfully connected to Dropbox, double check your supplied information and try again.  If you are still experiencing issues, please contact Support for further assistance.

6.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 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 Administrator login for this tenant.  If you are still experiencing issues, please contact Support for further assistance.

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

8.You can also choose to Load and Apply report option, which allows you to load and apply an Analyze Dropbox report, which then sets the Migration Priority for each user mentioned in the report. Click Next to continue.

9.Select Re-Map Users option and load your mapping CSV file.  Group mapping is required (user mapping may also be included) so the software can properly resolve the differences between your users' Dropbox account and the corresponding Microsoft Teams name as well as maintain content authorship.  If your user accounts differ between Dropbox and Microsoft Team then you will want to add your user mapping to this same file.  

In the example below, lines 1-3 illustrate mapping a source Dropbox to a Microsoft Team by name while lines 4-5 in the same file are used to map the Dropbox user accounts to their respective Microsoft Teams user accounts to maintain item authorship.

sales@company.com,MicrosoftTeam Name
marketing@company.com,MicrosoftTeam MarketingGroup
IT@company.com,IT Group
scott@company.com,swilson@contoso.com
bill@company.com,bgeorge@contoso.com

If you wish to migrate one or more source accounts to a single Group library while also remapping the user account for the purpose of metadata and sharing, please use the following format in your mapping file.

user@dropbox.com,MicrosoftTeam GroupName(user@contoso.com)

The software will migrate the content from the source drive "user@dropbox.com" to the Documents libary in the group "Microsoft Team GroupName".  The metadata and shared permissions of Dropbox user "user@dropbox.com" will be mapped to the Microsoft Team user account "user@contoso.com".
 
If you would like to migrate source accounts to a target Teams channel, use the following mapping.
 
scott@company.com,swilson@contoso.com,ChannelName
 
The third column in this CSV will map the users to the specific target channel.

10.Click Check MS Team in order to begin the validation process​. This process will validate that the supplied user mapping is correct (MS Teams were located) and check to determine if each Team currently has a Site provisioned.  Click Next.

If the group is not found you may continue, however no content for this mapping will be migrated.  Alternatively, you may go back one page and remove the selected source Dropbox account or modify your mapping file, reload the CSV and click the Check button again.

11.If necessary, change content and file format conversion options​ as described below.

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 Dropbox revision history will be converted into Microsoft Teams versions.  Please note that this option is only referring to the major revisions (those shown as the "less detailed revisions") and not those that are automatically generated within Dropbox (those shown as the "more detailed" revisions).

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).

Skipped Non-Owned Folders - This option addresses the scenario where folders appear in a user's Dropbox 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 Microsoft Teams 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.
 
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 - Optionally, select from a series of filterable parameters to include or exclude specific content during migration.

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. 

Create User Specific Log File - If you would like a user specific log file (.txt format) created for each migrated Microsoft Team that will be saved directly to that Team'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.

12. Click Finish to begin the migration.

Nintex Deployment

The following steps will allow you to deploy your Nintex Workflow and Nintex Forms applications from within Essentials.

1.Select Nintex Deployment from the Drives tab.

2.In the Nintex Deployment window, enter a valid SharePoint URL, and click Connect.

3.Provide your user credentials to connect to SharePoint. Click Connect.

4.This will open the SharePoint Application Catalog. You must switch to classic view in order to perform the deployment, as deployment cannot be done in modern view.

5.If you do not have Nintex Workflows or Nintex Forms as part of your Site Contents, then select Add an App and install the nintex workflows/nintex forms application.

6.On the Site Contents page, Select the ellipses (...) next to the installed Nintex application, and click on Deployment.

7.On the Manage App Deployments page, enter the site collection URL or select one from the list available, select and add the managed paths to deploy to, and select and add the templates to deploy to.

8.Click Ok to apply your selections.

9.When asked whether you trust workflow0365.nintex.com click Trust It. This will start the actual deployment.
Note: Microsoft is now deploying the Nintex app to your tenant. It may take from a minute to hour(s) depending on the complexity of your site collection structure. Please verify your site collection for Nintex apps before starting a migration.

Post Migration Compare

You can run reports that highlight differences in the number of SharePoint objects between source and target after migrating any of the following:

·Google Drive to One Drive

· Google Drive to SharePoint Online

·Google Shared Drive to SharePoint Online

·SharePoint Online to SharePoint Online

The report is saved as an Excel file, so it can be shared with other administrators/site owners.

To initiate a Post Migration Compare:

On the Drives tab, select Post Migration Compare.

Google Drive to One Drive Post Migration Compare

Creating a CSV with Mappings

Before a Google Drive to One Drive Post Migration Compare report can be run, a CSV file must be created that maps each source and target user you want to compare. You can run a mapping report and modify it to contain only the source Google Drive user and target One Drive user, and target library, as shown in the example below.

To perform a Google Drive to One Drive Post Migration Compare:

1.Once you have initiated a Post Migration Compare, enter a Project Name.

2.For Location and name for report, click the Select button, then select the name and location for the Excel output. (Essentials automatically adds the xlsx extension).

3.For Source Location, select Google Drive and connect to Google Drive.

4.For Target Location, select One Drive and connect to the Office 365 tenant.

5.Click Next to display the Check for availability of sites dialog.

6.Click the Load from CSV button.

Essentials loads the mappings from the CSV file.

7.Click the Check for sites button.

Essentials retrieves the content for the mapped source and target users.

8.Click Next to display the Configuration of live compare dialog.

9.Select the Content Options for the report:

§Group By either List or Item.

§Show differences only: When this box is checked, the report will only show objects for which the count is different between the source and target. If you leave this box unchecked, the report will include all objects, regardless of whether the count is different. Count differences will be highlighted in red.

§Ignore target excess: When this box is checked, only objects for which the source count is higher than the target count will be highlighted in red. If you leave this box unchecked, objects for which the target count is higher than the source count will also display in red.

§Include Orphaned Files - When this box is checked, the report will include files that were created in a folder that was shared with a user and after the file was created, but their permission to the shared folder was removed. Including orphaned files will increase the time it takes for the report to run.

§Skip Non-Owned Files - When this box is checked, the report will exclude any content that exists in the user's Google Drive "My Drive" area that is not owned by the user.

§Include Shared Files - When this box is checked, the report will include files that have been shared with the user.

§Skip non supported objects - When this box is checked, any files that are not supported in Office 365 will be skipped.

10.Select the Formatting options that were used for the migration.

Now you can either:

·generate the report immediately (by clicking the Next button).

OR

·schedule the report to run at a specified time.

The report lists the count comparison between source and target for each object. If you are comparing content for multiple users, each will display in a separate tab.

If you accepted the default configuration options, all source and target objects will be included in the report. All differences in count between source and target are highlighted in red.

If you chose to Show differences only, objects with 0 Difference in Count are excluded from the report.

If you chose to Ignore target excess, only objects for which the count is higher on the source are highlighted in red.