The Source and Destination must be OneDrive for Business - not the personal OneDrive version.
If you are migrating to an Office 365 Small Business Tenant account, the processes will be very similar. However, you will not be able to use admin credentials for your Destination endpoint, and will, instead, be using end user credentials.
Note: We no longer support migrations to or from GoDaddy hosted OneDrive.
Preparing the Source
Preparing the Destination
If you are leveraging a OneDrive V2 destination endpoint follow the 'Prepare Azure Environment' steps below. If you are not using the V2 endpoint, skip this step and navigate to the 'Create an Administrator Account' section.
Important: While there is an option to use Microsoft-provided Azure storage, we recommend that you use your own Azure storage instead. The security token generated for the Microsoft-provided storage expires after just a couple of days and that expiration will cause the migration to fail.
Prepare Azure Environment
Note: If using Microsoft-provided Azure storage, you can skip this section.
- Estimate Azure storage costs. This step is optional but is useful in order to provide the customer with upfront storage costs ahead of time. For more information, see Estimate Azure Storage costs for migrations.
- Buy an Azure subscription (or use the free one-month trial, and be aware that this option is only viable if you are performing a very small migration). For more information, see How do I buy an Azure subscription?
- See How do I create an Azure Storage Account? to create your storage account. You will need to set up a STORAGE (General Purpose v1 or v2) account rather than a storage blob. Take note of the storage account name and the primary access key. (In Azure, from the storage screen, click Manage Access Keys at the bottom of the screen.) These need to be entered into the MigrationWiz migration project when specifying the Destination settings. We recommend that you create your Azure storage account in the same Microsoft data center as the Destination Office 365 tenant. There is no need to create any Azure containers for this migration.
Note: The access key information that is needed are these:
- -accesskey – This is the Storage account name for the Blob – example “accountname”
- -secretkey - This is the access key for the Storage account – example “W1RrDfkPNkfYfdVqizMNJjn5mXchwMP5uYBY8MsMqWTA7EubG911+4fZlki0Gag==”
Create A Document Project
Add Items To Project
To add the user accounts (also called "Line Items") that will be migrated into the project using the CSV file created in the Prepare Source section, click "Add" in the menu dashboard and select "Bulk-Add".
- NOTE: If you're also running a Mailbox Project for the users that will be migrated here, you can use the "Add from MSPComplete" option. Verify the users are licensed in MSPComplete or in the Mailbox project before adding them.
Important: The users Source and Destination address must be entered with the same domain that they're currently assigned in each Office 365 Tenant. Read the Cannot Authenticate article for more information.
Set Project Advanced Options. Read the What project Advanced Options are available? article for more information.
- For non-standard URL endpoints, add
OneDriveProExportAdminUrl=<non standard URL>and
OneDriveProImportAdminUrl=<non standard URL>. (Replace "<non standard URL>" with your custom URL.)
- Under Support/Support Options add:
UseAsynchronousMetadataRead=1- This sets the default API to be the AMR API in order to reduce the number of calls against the tenants. This can improve the migration performance when running migrations with large numbers of folders.
InitializationTimeout=8- This increases the initialization timeout window to eight hours. Read the Cannot get folders from My Drive article for more information.
IncreasePathLengthLimit=1- Use this Advanced Option in MigrationWiz to enable the use of 400 characters for the file path name. Read the What would I use the Advanced Option IncreasePathLengthLimit=1 for? article for more information.
- If the migration project is a long-term project, it may be necessary to add an additional Advanced Option for use during the final migration pass to verify the contents of previously migrated items. For more information, contact Support.
- BitTitan has no limitations to the number of folders per migration. Any folder limits will be set by Microsoft.
Note: There are no spaces on either side of the "=" sign, and the entries are case-sensitive, so pay special attention to the capital letters in the commands above.
- Set the Advanced Option to send a notification to end users after the migration pass completes. (This is optional.)
- Notifications > Send successful migration and notification to: > Source email address (if users are still using the original Source Office 365 tenant) or Destination email address (if users are already using the Destination Office 365 tenant).
- Customize notification email. Checkmark the Customize "successful migration" email box. Add your own customization text and company name to this email.
Note: Notifications should only be set up before the final pass. If performing a single, Full pass, set this up now. If you are following a Pre-Stage migration strategy, only set this up prior to the final Full (Delta) pass.
Remove the Authentication AppClick the bar chart icon in the MigrationWiz dashboard to receive an email containing all the project migration statistics. Read the How do I request statistics for my migration project? article for more information.
- To prevent users from inadvertently logging in and using their Source accounts, decommission their Source OneDrive for Business user accounts, or change their passwords.
- Notify users once the migration has completed.
Note: If you set the MigrationWiz Advanced Option for Notifications, they will receive an email upon migration completion. Assist them with setting up access to their OneDrive for Business accounts, and setting up their synchronization settings.