Use drive shipping to import SharePoint data to Office 365

This article is for administrators. Are you trying to upload your files to SharePoint Online or OneDrive for Business? See Upload files to a library

Use the Office 365 Import service and drive shipping to import files and documents to SharePoint Online and OneDrive for Business sites in your Office 365 organization. Drive shipping means that you copy the SharePoint Online migration package (that includes both the data files and manifest files) to a hard disk drive and then physically ship the drive to Microsoft. When Microsoft receives your hard drive, data center personnel will copy the data from the hard drive to a storage area in the Microsoft cloud. The Office 365 Import service copies the files from the storage area to SharePoint and OneDrive for Business sites in Office 365. Using drive shipping is the most efficient way to import documents to users OneDrive for Business sites.

Here are the steps required to use drive shipping to import data to SharePoint and OneDrive for Business sites in your Office 365 organization.

Step 1: Download the data import tool and secure storage key

Step 2: Create a SharePoint Online migration package

Step 3: Prepare the SharePoint Online migration package

Step 4: Copy the SharePoint Online migration package to the hard drive

Step 5: Create a data import mapping file

Step 6: Create a data import job in Office 365

Step 7: Ship the hard drive to Microsoft

Step 8: Upload the manifest files to Office 365

Step 9: Update the data import mapping file

Step 10: Create a data import job for the manifest files

What happens next

Before you begin

  • You have to be a global administrator in your Office 365 organization to access the Import page (under Data governance) in the Office 365 Security & Compliance Center.

  • Only 3.5 inch SATA II/III internal hard drives are supported for use with the Office 365 Import service. You can use hard drives up to 10 TB. For the import jobs that you create in Step 6, only the first data volume on the hard drive will be processed. The data volume must be formatted with NTFS. When copying data to your hard drive, you can attach it directly using a SATA connector or you can attach it externally using an external SATA II/III USB adaptor. We recommend using one of the following external SATA II/III USB adaptors:

    • Anker 68UPSATAA-02BU

    • Anker 68UPSHHDS-BU

    • Startech SATADOCK22UE

    • Sharkoon QuickPort XT HC

    If you have an adapter that's not listed, you can try using your adapter to copy the PST files to the hard drive in Step 4 to see if it works before purchasing a supported adapter.

    Important: External hard drives that come with an built-in USB adaptor aren't supported by the Office 365 Import service. Additionally, the disk inside the casing of an external hard drive can't be used. Please don't ship external hard drives.

  • The hard drive that you copy the data files to must be encrypted with BitLocker. The tool that you run in Step 4 will help you set up BitLocker. It also generates a BitLocker encryption key that Microsoft data center personnel will use to access the drive to upload the files to the storage area in the Microsoft cloud.

    The computer that you use to copy files to the hard drive has to be running one of the following versions of Windows that support BitLocker:

    • Windows 10

    • Windows 8

    • Windows Server 2012

    • Windows Server 2008 R2

    • Windows 7 Ultimate Edition

    • Windows 7 Enterprise Edition

  • The cost to import files to import data to SharePoint and OneDrive for Business sites in your Office 365 organization using drive shipping is $2 USD per GB of data. For example, if you ship a hard drive that contains 1,000 GB (1TB) of data files, the cost is $2,000 USD. You can work with a partner to pay the import fee. For information about finding a partner, see Find your Office 365 partner or reseller.

  • You or your organization must have an account with FedEx or DHL.

    • Organizations in the US and Europe must have FedEx accounts.

    • Organizations in East Asia, Southeast Asia, Japan, and Australia must have DHL accounts.

    Microsoft will use (and charge) this account to return the hard drive back to you.

  • The hard drive that you ship to Microsoft might have to cross international borders. If this is the case, you're responsible for ensuring that the hard drive and the data it contains are imported and/or exported in accordance with the applicable laws. Before shipping a hard drive, check with your advisors to verify that your drive and data can legally be shipped to the identified Microsoft data center. This will help to ensure that it reaches Microsoft in a timely manner.

  • For frequently asked questions about using drive shipping to import SharePoint data to Office 365, see FAQ about importing SharePoint data to Office 365. For more information about importing data to Office 365, see Overview of importing PST files and SharePoint data to Office 365.

Return to top

Step 1: Download the data import tool and secure storage key

The first step is to download the Azure Import Export tool and secure storage key that you will use in Step 4 to copy SharePoint or OneDrive for Business files to the hard drive.

  1. Go to https://protection.office.com.

  2. Sign in to Office 365 using the credentials for an administrator account in your Office 365 organization.

  3. In the left pane of the Security & Compliance Center, click Data governance and then click Import.

  4. On the Import page, click Go to the Import service.

  5. On the Import data to Office 365 page, click New job Add Icon , and then click Ship data to Microsoft.

  6. In Step 3, click Download tool to download the Azure Import Export tool.

  7. In the pop-up window, click Save > Save as to save the WAImportExport.zip file to a folder on your local computer.

  8. Extract the WAImportExport.zip file.

  9. Back on the Ship files to Microsoft on physical hard drives page, under Copy the Drive Shipping key, click Show key.

  10. Copy the key that's displayed in the box and save it to a file. Be sure to copy the entire key. Take precautions to protect the file that contains this key.

  11. Click Cancel to close the Ship files to Microsoft on physical hard drives page.

    You'll come back to the Import data to Office 365 page when you create the import job in Step 5.

Return to top

Step 2: Create a SharePoint Online migration package

The next step is to create a migration package that's based on the files that you want to import to Office 365. The migration package also contains metadata files that contain the information used to import the data files. This procedure assumes the files that you want to import to Office 365 are located on a file share or file server in your organization.

  1. Download and install the SharePoint Online Management Shell.

  2. Open the SharePoint Online Management Shell from the Start page, and then run the following command:

    $credentials = Get-Credential
  3. In the Windows PowerShell Credential Request dialog box, type the user name and password for your Office 365 global administrator account, and then click OK.

  4. Run the following command to connect the shell to your SharePoint Online organization:

    Connect-SPOService -Url https://<Your organization name>-admin.sharepoint.com -credential $credentials

    Tip: To verify that you're connected to your SharePoint Online organization, run the Get-SPOSite cmdlet to get a list of the sites in your organization.

  5. In the SharePoint Online Management Shell, run the following command to create a migration package.

    New-SPOMigrationPackage -SourceFilesPath <File share or server where data files are located> -OutputPackagePath <Location on file share to copy the package to> -TargetWebUrl <Target SharePoint or OneDrive for Business site> -IgnoreHidden -ReplaceInvalidCharacters

    The following table describes the parameters used in this command, and their required values.

    Parameter

    Description

    Example

    SourceFilesPath

    The path for the file share or file server that contains the data files that will be imported to Office 365.

    -SourceFilesPath "c:\Share1\DataFiles\DataImportJob1"

    Or

    -SourceFilesPath "\\FILESERVER01\SPFiles\DataImportJob1"

    OutputPackagePath

    The location where the metadata files for the migration package will be copied to.

    -OutputPackagePath "c:\Share1\DataFiles\ImportJob1\Package"

    TargetWebUrl

    The URL for the Web site in your SharePoint Online organization that you're importing the data files to. This could be the URL for a SharePoint or OneDrive for Business site.

    -TargetWebUrl https://contoso.sharepoint.com/sites/SPOCorpSite

    IgnoreHidden

    Use this optional switch to ignore hidden files and folders. Using this switch might help reduce the size of a migration package.

    -IgnoreHidden

    ReplaceInvalidCharacters

    Use this optional switch to replace characters in file and folder names that would be invalid in SharePoint and OneDrive for Business. For a list of these characters, see Invalid characters in file or folder names or invalid file types in OneDrive for Business.

    -ReplaceInvalidCharacters

    Here's an example of the syntax for the New-SPOMigrationPackage cmdlet using actual values for each parameter:

    New-SPOMigrationPackage -SourceFilesPath "\\FILESERVER01\Files\DataImportJob1" -OutputPackagePath "c:\Share1\DataFiles\ImportJob1\Package" -TargetWebUrl https://contoso.sharepoint.com/sites/SPOCorpSite -IgnoreHidden -ReplaceInvalidCharacters
  6. Leave the SharePoint Online Management Shell open. You'll use it in Step 3 to prepare the migration package so you can upload it to Office 365.

Return to top

Step 3: Prepare the SharePoint Online migration package

After you create the migration package (from source files on file share, a file server, or an on-premises SharePoint site), the next step is to prepare the migration package by running the ConvertTo-SPOMigrationTargetedPackage cmdlet in your SharePoint Online organization. This cmdlet verifies that the migration package and the source files match, and then validates the SharePoint Online site and document library that you want to import the data files to. The cmdlet creates a target package that will be copied to the hard drive in Step 4.

  1. In the SharePoint Online Management Shell, run the following command. See the previous step for instructions on how to connect to your SharePoint Online organization.

    ConvertTo-SPOMigrationTargetedPackage -SourceFilesPath <Location of source files> -SourcePackagePath <Location of  metadata files> -OutputPackagePath <Location to copy the target package to> -TargetWebUrl <Target SharePoint or OneDrive for Business site> -TargetDocumentLibraryPath <Target document library>

    The following table describes the parameters used in this command, and their required values.

    Parameter

    Description

    Example

    SourceFilesPath

    The path for the file share or file server that contains the data files that will be uploaded to Office 365. Use same value that you used for the SourcesFilesPath parameter when you ran the New-SPOMigrationPackage in Step 2.

    -SourceFilesPath "\\FILESERVER01\SPFiles\DataImportJob1"

    Or

    -SourceFilesPath "c:\Share1\DataFiles\ContosoCorpSite"

    SourcePackagePath

    The location where the metadata files for the migration package will be copied to.

    -SourcePackagePath "c:\Share1\DataFiles\ContosoCorpSite"

    OutputPackagePath

    The location on the file share or file server where the metadata files for the target migration package produced by this cmdlet will be copied to.

    -OutputPackagePath "c:\SPFiles\DataImportJob1\TargetPackage"

    TargetWebUrl

    The URL for the Web site in your SharePoint Online organization that you're importing the data files to. Use the same value that you used for the TargetWebUrl parameter when you ran the New-SPOMigrationPackage in Step 2.

    -TargetWebUrl https://contoso.sharepoint.com/sites/ContosoCorpSite

    TargetDocumentLibraryPath

    The name of the document library (located in the site specified by the TargetWebUrl) that the data files will be imported to.

    -TargetDocumentLibraryPath "Shared Documents"

    This example is for a migration package created from source files on a file share or file server.

    ConvertTo-SPOMigrationTargetedPackage -SourceFilesPath "\\FILESERVER01\SPFiles\DataImportJob1" -SourcePackagePath "c:\Share1\DataFiles\ImportJob1\Package" -OutputPackagePath "c:\SPFiles\DataImportJob1\TargetPackage" -TargetWebUrl https://contoso.sharepoint.com/sites/ContosoCorpSite -TargetDocumentLibraryPath "Shared Documents"

Return to top

Step 4: Copy the SharePoint Online migration package to the hard drive

The next step is to use the WAImportExport.exe tool that you installed in Step 1 to copy the migration package to the hard drive. This tool encrypts the hard drive with BitLocker, copies the manifest and data files to the hard drive, and creates a journal file that stores information about the copy process.

Note: After you run the WAImportExport.exe tool the first time to turn on BitLocker and copy the manifest files to the hard drive, you have to use a different syntax each time after that to copy data files. See step 4 in the following procedure.

  1. Open a Command Prompt (Run as administrator) on your local computer.

    Tip: If you run the command prompt as an administrator (by selecting "Run as administrator" when you open it) error messages will be displayed in the command prompt window. This can help you troubleshoot problems running the WAImportExport.exe tool.

  2. Go to the directory where you installed the WAImportExport.exe tool in Step 1.

  3. Run the following command to copy the manifest package (created in Step 3) to the hard drive.

    WAImportExport.exe PrepImport /j:<Name of journal file> /t:<Drive letter of the hard drive> /id:<Name of session> /sk:<Storage account key obtained in Step 1> /srcdir:<OutputPackagePath or SourceFilesPath> /dstdir:<Azure container name> /encrypt /disposition:overwrite /logdir:<Log file location>

    The following table describes the parameters and their required values.

    Parameter

    Description

    Example

    /j:

    Specifies the name of the journal file that is created. This file is saved to the same folder where the WAImportExport.exe tool is located. Each hard drive you ship to Microsoft must have one journal file. Every time you run the WAImportTool.exe to copy files to a hard drive, information will be appended to the journal file for that drive. You'll submit the journal when you create the import job in Step 6.

    Microsoft data center personnel will use the information in the journal file to associate the hard drive with the import job, and to upload the data and manifest files to the Azure storage location in the Microsoft cloud.

    /j:SPOHDD1.jrn

    /t:

    Specifies the drive letter of the hard drive when it's connected to your local computer.

    /t:h

    /id:

    Specifies the name of the copy session. A session is defined as each time you run the WAImportExport.exe tool to copy files to the hard drive. Files are copied to a folder named with the value specified by this parameter.

    /id:SPOManifest1

    /srcdir:

    Specifies the source directory in your organization that contains the manifest package or the data files that will be copied during the session.

    To copy the manifest files, use the value of the OutputPackagePath parameter when you ran the ConvertTo-SPOMigrationTargetedPackage cmdlet in Step 3.

    To copy the data files, use the value of the SourceFilesPath parameter.

    /srcdir:"c:\SPFiles\DataImportJob1\TargetPackage"

    Or

    /srcdir:"c:\Share1\DataFiles\ContosoCorpSite"

    /dstdir:

    Specifies the name of the container in the Azure storage location that the sources files will be copied to. This container will be created when Microsoft datacenter personnel upload the files on the hard drive to the Azure storage location.

    Tip: Use a naming convention for the container names that you specify with this parameter. For example, use a value to identify whether you're copying manifest files or data files. Also, include something about the target site that the data will be imported to or the current date. Note that the value that you use for this parameter should be unique each time you run the WAImportExport.exe tool. You'll specify the value of this parameter in the mapping file that you create in Step 5.

    /dstdir:ContosoCorpSiteManifest

    Or

    /dstdir:ContosoCorpSiteData

    /sk:

    Specifies the storage account key that you obtained in Step 1. Be sure to surround the value of this parameter with double-quotation marks (" ").

    "yaNIIs9Uy5g25Yoak+LlSHfqVBGOeNwjqtBEBGqRMoidq6/e5k/VPkjOXdDIXJHxHvNoNoFH5NcVUJXHwu9ZxQ=="

    /encrypt

    This switch turns on BitLocker for the hard drive. This parameter is required the first time you run the WAImportExport.exe tool for a specific hard drive.

    The BitLocker encryption key is copied to the journal file and to the log file that is created. As previously explained, the journal file is saved to the same folder where the WAImportExport.exe tool is located.

    /encrypt

    /disposition:

    This optional parameter specifies the behavior when the Azure storage location specified by the /dstdir: parameter already exists. Valid values for this parameter are: overwrite, rename, and no-overwrite.

    /disposition:overwrite

    /logdir:

    This optional parameter specifies a folder to save log files to. If not specified, the log files are save to the same folder where the WAImportExport.exe tool is located.

    /logdir:c:\users\admin\desktop\SPImportLogs

    Here's an example of the syntax for the WAImportExport.exe tool using actual values for each parameter. Use this syntax only the first time you run the WAImportExport.exe tool for a new hard drive. Use the syntax in step 4 each subsequent time that you run the WAImportExport.exe tool.

    WAImportExport.exe PrepImport /j:SPOHDD1.jrn /t:f /id:SPOManifest1 /sk:"yaNIIs2Uy7g25Yoak+LlSHfqVBGOeNwjqtBEBGqRMoidq6/e5k/VDkjOXdDIXJHxHvPoGoFH5NcVUKYZwu9ZxQ==" /srcdir:c:\Users\Admin\Desktop\DriveShippingshare\TargetPackage /dstdir:"ContosoCorpSiteManifest" /encrypt /disposition:overwrite /logdir:c:\users\admin\desktop\SPODriveShipLogs

    After you run the command, status messages are displayed that show the progress of copying the manifest files to the hard drive. A final status message shows the total number of files that were successfully copied.

  4. Run the following command to copy the data files to the hard drive. Be sure to use a unique value for the /id: parameter each time you run this command.

    WAImportExport.exe PrepImport /j:<Name of journal file> /id:<Name of new session> /srcdir:<SourceFilesPath> /dstdir:<Azure container name> /disposition:overwrite

    Here's an example of the syntax for running subsequent sessions to copy data files to the same hard drive.

    WAImportExport.exe PrepImport /j:SPOHDD1.jrn /id:SPOData1 /srcdir:c:\Users\Admin\Desktop\DriveShippingshare /dstdir:ContosoCorpSiteData /disposition:overwrite

    Important: You don't have to specify the BitLocker key (by using the /bk: parameter) when you run the WAImportExport.exe tool after you initially enable BitLocker. This is because the tool retrieves the BitLocker key from the journal file. If you include the /bk: parameter, the tool will return an error.

  5. Repeat step 3 and step 4 for each SPO migration package that you want to copy to the hard drive. That means you'll run the WAImportExport.exe tool twice for each SPO migration package: once to copy the manifest files and once to copy the data files. As previously stated, use unique value for the /dstdir: parameter each time you run the tool.

Return to top

Step 5: Create a data import mapping file

After the data and manifest files for each migration package have been copied to the hard drive, the next step is to create a comma separated value (CSV) mapping file that specifies the SharePoint or OneDrive for Business sites in Office 365 that the data files will be imported to. This file also specifies of the location of the data and manifest files that Microsoft datacenter personnel uploaded to the Azure storage location after they receive your hard drive. You'll submit the data mapping file in Step 6 when you create the import job.

Important: You need to add a row to the data import mapping file for each SPO migration package that you copied to the hard drive.

  1. Download a copy of the CSV Import mapping file.

  2. Open or save the CSV file to your local computer. The following example shows a completed import mapping file (opened in NotePad). It's much easier to use Microsoft Excel to edit the CSV file.

    Workload,FilePath,Name,Mailbox,IsArchive,TargetRootFolder,SPFileContainer,SPManifestContainer,SPSiteUrl
    SharePoint,,,,,,ContosoCorpSiteData,ContosoCorpSiteManifest,https://contoso.sharepoint.com/sites/ContosoCorpSite
    

    The first row, or header row, of the CSV file lists the parameters that will be used by the Import service to import files to SharePoint or OneDrive for Business sites. Each parameter name is separated by a comma. Each row under the header row represents the parameter values for importing files. Be sure to replace (or remove) the placeholder data in the mapping file with your actual data.

  3. Use the information in the following table to populate the CSV file with the required information.

    Parameter

    Description

    Example

    Workload

    Specifies the Office 365 service that data will be imported to. To import data files to SharePoint Online or OneDrive for Business, use SharePoint.

    SharePoint

    FilePath

    For importing files to SharePoint or OneDrive for Business, leave this parameter blank.

    Not applicable

    Name

    For importing files to SharePoint or OneDrive for Business, leave this parameter blank.

    Not applicable

    Mailbox

    For importing files to SharePoint or OneDrive for Business, leave this parameter blank.

    Not applicable

    IsArchive

    For importing files to SharePoint or OneDrive for Business, leave this parameter blank.

    Not applicable

    TargetRootFolder

    For importing files to SharePoint or OneDrive for Business, leave this parameter blank.

    Not applicable

    SPFileContainer

    Specifies the name of the file container in the Azure storage location that you uploaded the data files to. Use the same value that you used for the /dstdir: parameter in Step 4 when you copied the data files to the hard drive.

    ContosoCorpSiteData

    SPManifestContainer

    Specifies the name of the file container in the Azure storage location that you uploaded the manifest files to. Use the same value that you used for the /dstdir: parameter in Step 4 when you copied the manifest files to the hard drive.

    ContosoCorpSiteManifest

    SPSiteUrl

    Specifies the SharePoint or OneDrive for Business site that the data files will be imported to. Use same value that you used for the TargetWebUrl parameter when you ran the ConvertTo-SPOMigrationTargetedPackage in Step 3.

    https://contoso.sharepoint.com/sites/ContosoCorpSite

    Note: Don't change anything in the header row, including the Exchange parameters; they will be ignored during the SharePoint data import process.

Return to top

Step 6: Create a data import job in Office 365

The next step is to create the data import job in the Import service in Office 365. As previously explained, you will submit the journal file that was created in Step 4 and the data import mapping file that you created in Step 5. After you create the new job, the Import service will use the information in the mapping file to import the data files to the specified SharePoint or OneDrive for Business site after the data and manifest files are copied from the hard drive to the Azure storage area.

  1. Go to https://protection.office.com.

  2. Sign in to Office 365 using the credentials for an administrator account in your Office 365 organization.

  3. In the left pane, click Data governance and then click Import.

  4. On the Import page, click Go to the Import service.

  5. On the Import data to Office 365 page, click New job Add Icon , and then click Ship data to Microsoft.

  6. On the New job page, click the I‎'ve prepared my hard drives and have access to the necessary drive journal files and I have access to the mapping file check boxes, and then click Next.

  7. Type a name for the data import job, and then click Next.

  8. On the Upload the drive files page, click Add Add Icon , and then go to the same folder where the WAImportExport.exe tool is located. The journal file that was created in Step 4 was copied to this folder.

  9. Select the journal file; for example, SPOHDD1.jrn.

    Tip: When you ran the WAImportExport.exe tool in Step 4, the name of the journal file was specified by the /j: parameter.

    Each hard drive you ship to Microsoft must have a corresponding journal file. Add additional journal files if applicable.

  10. After adding a journal file for each hard drive that you will ship to Microsoft, click Next .

  11. Click Add Add Icon to select data mapping file that you created in Step 5.

  12. After the data mapping file is uploaded, click Next.

  13. On the Contact information page, type your contact information in the applicable boxes.

    Note that the address for the Microsoft location that you will ship your hard drive to is displayed. This address is auto-generated based on your Office 365 data center location. Copy this address to a file or take a screenshot.

  14. Click Next .

    A page is displayed with a summary of your contact information and the Microsoft location that you will ship your hard drive to

  15. Click Finish.

    A page is displayed with information about the next steps of the drive shipping process.

  16. On the Import data to Office 365 page, click Refresh Refresh icon to displayed the new drive shipping import job in the list of import jobs. Notice that status is set to Waiting for Tracking number.

    New drive shipping job displayed on the Import data to Office 365 page

Return to top

Step 7: Ship the hard drive to Microsoft

The last step is to ship the hard drive to Microsoft, and then provide the tracking number and return shipment information for the drive shipping job. When the drive is received by Microsoft, data center personnel will upload your data files to the Azure storage area for your organization.

Ship the hard drive

Keep the following things in mind when you ship hard drives to Microsoft:

  • Don't ship the SATA-to-USB adapter; you only have to ship the hard drive.

  • Package the hard drive properly; for example, use an anti-static bag or bubble wrap.

  • Use a delivery carrier of your choice to ship the hard drive to Microsoft.

  • Ship the hard drive to the address for the Microsoft location that was displayed when you created the import job in Step 6. Be sure to include "Office 365 Import Service" in the ship-to address.

  • After you ship the hard drive, be sure to write down the name of the delivery carrier and the tracking number. You'll provide these in the next step.

Enter the tracking number and other shipping information

After you've shipped the hard drive to Microsoft, complete the following procedure on the Import service page.

  1. Go to https://protection.office.com.

  2. Sign in to Office 365 using the credentials for an administrator account in your Office 365 organization.

  3. In the left pane, click Data governance and then click Import.

  4. On the Import page, click Go to the Import service.

  5. On the Import files to Office 365 page, select the job for the drive shipment that you want to enter the tracking number for.

  6. In the details pane, click Enter tracking number.

    The Shipping Details page is displayed.

    Enter the tracking number and other shipping information for your drive shipping job
  7. Provide the following shipping information:

    1. Delivery Carrier   Type the name of the delivery carrier that you used to ship the hard drive to Microsoft.

    2. Tracking Number   Type the tracking number for the hard drive shipment.

    3. Return Carrier Account Number   Type your organization's account number for the carrier that listed under Return Carrier. Microsoft will use (and charge) this account to ship your hard drive back to you. Note that organizations in the USA and Europe, must have an account with FedEx. Organizations in Asia and the rest of the world, must have an account with DHL.

  8. Click Save to save this information for the import job.

    On the Import data to Office 365 page, click Refresh Refresh icon to updated the information for your drive shipping import job. Notice that status is now set to Drives in transit.

Return to top

Step 8: Upload the manifest files to Office 365

After you've created the drive shipping import job and shipped the hard drive to Microsoft, the next step is to upload the manifest that you created in Step 3 to an Azure storage location for your organization. This step consists of two tasks:

  • Create manifest container names, SAS URLs, and download the Azure AzCopy tool.

  • Run the AzCopy tool to upload the manifest files to Azure.

Create manifest container names and SAS URLs and download the AzCopy tool

The first step is to create (and save to a file) the container name and SAS URL that you'll need to upload the manifest files to Azure. The container name will be used to create the Azure container that your manifest files will be uploaded to. The SAS URL is a combination of the network URL for your Azure storage location and a Shared Access Signature (SAS) key. This key provides the necessary permissions to upload the manifest files to Azure. You'll also download the AzureAzCopy tool, which you'll use to upload the manifest files to Azure.

Important: You have to use Azure AzCopy version 5.0 to successfully upload the manifest files to the Azure storage location. Newer versions of the AzCopy tool aren't supported. Be sure to download the AzCopy tool from the Upload files over the network page by following the procedures in this step.

  1. Go to https://protection.office.com.

  2. Sign in to Office 365 using the credentials for an administrator account in your Office 365 organization.

  3. In the left pane, click Data governance and then click Import.

  4. On the Import page, click Go to the Import service.

  5. On the Import data to Office 365 page, click New job Add Icon , and then click Upload SharePoint or OneDrive data.

  6. On the Upload files over the network page, under step 2, click Create URLs and container names.

    Two sets of container names and URLs are displayed. You only have to copy the ones for the manifest container.

  7. Copy and save the following two things to a file. Be sure to copy the entire line of text for each.

    • Manifest container name; you'll use this name in Step 9 when you edit the import mapping file.

    • Manifest container SAS URL; you'll use this URL in the next step when you upload the manifest files to Azure.

  8. In step 4 on the Upload files over the network page, click Download tool to download and install the Azure AzCopy tool.

  9. In the pop-up window, click Run to install the AzCopy tool.

  10. Create additional containers names and SAS URLs (also copying them to a file) for each manifest that you want to upload to Azure. Be sure to click Cancel to close the Upload files over the network page, and then re-open it to generate a new set of container names and SAS URLs.

    Important: You have to create a unique manifest SAS URL and manifest container name for each SPO migration package that you copied to the hard drive in Step 4. Be sure to keep track of the container name-SAS URL pair that you'll use for each migration package.

Return to top

Run the AzCopy tool to upload the manifest files to the Azure storage location

Now you'll use the AzCopy.exe tool that you installed in the previous step to upload the manifest files (that you created in Step 3) to the Azure storage location for your organization.

  1. Open a Command Prompt (Run as administrator) on your local computer.

  2. Go to the directory where you installed the AzCopy.exe tool in the previous step. If you installed the tool in the default location, go to %ProgramFiles(x86)%\Microsoft SDKs\Azure\AzCopy.

  3. Run the following command to upload the manifest files to the manifest container in the Azure storage location..

    AzCopy.exe /Source:<OutputPackagePath> /Dest:<Manifest container SAS URL> /V

    The following table describes the parameters and their required values. Note that the information you got in the previous step and in Step 3 is used as the values for these parameters.

    Parameter

    Description

    Example

    /Source:

    Specifies the source directory that contains the manifest package that you created in Step 3. Use the same value that you used for the OutputPackagePath parameter when you ran the ConvertTo-SPOMigrationTargetedPackage cmdlet in Step 3.

    /Source:"c:\SPFiles\DataImportJob1\TargetPackage"

    /Dest:

    Specifies the SAS URL for the manifest container that you generated in the previous step. Be sure to surround the value of this parameter with double-quotation marks (" ").

    /Dest:"https://3c3e5952a2764023ad48941.blob.core.windows.net/manifest-2016101217-30170d684bbd4030bd3200e323c4ff87?sv=2012-02-12&se=2017-01-10T17%3A53%3A28Z&sr=c&sp=wl&sig=QLQH1LNWxSeooOJ1T6BZWuicDdCTErbJfy6m1Ms5P0U%3D"

    /V

    Outputs verbose status messages into a log file. If you don't include a path for a log file, the verbose log file is named AzCopyVerbose.log in %LocalAppData%\Microsoft\Azure\AzCopy. Each time you run AzCopy.exe and specify this parameter, the verbose status message will be appended to the log file.

    /V

    Or

    /V:C:\Users\Admin\Desktop\AzCopy1.log

    Here's an example of the syntax for the AzCopy.exe tool using actual values for each parameter:

    AzCopy.exe /Source:"c:\SPFiles\DataImportJob1\TargetPackage"/Dest:"https://3c3e5952a2764023ad48941.blob.core.windows.net/manifest-2016101217-30170d684bbd4030bd3200e323c4ff87?sv=2012-02-12&se=2017-01-10T17%3A53%3A28Z&sr=c&sp=wl&sig=QLQH1LNWxSeooOJ1T6BZWuicDdCTErbJfy6m1Ms5P0U%3D" /V:C:\Users\Admin\Desktop\AzCopy1.log
  4. Repeat the previous step and run the AzCopy.exe command for each SPO migration package that you copied to the hard drive in Step 4. Be sure to use unique values for the /Source: and /Dest: parameters each time you run the tool. These values will correspond to a specific SPO migration package.

Return to top

Step 9: Update the data import mapping file

The next step is to update the CSV import mapping file that you created in Step 5. You have to replace the value of the SPManifestContainer parameter with a value that corresponds to a manifest container name that you generated in Step 7. Additionally, each data import mapping file that you submit when you create the import job in Step 10 can have only one row. For example, if the mapping file that you submitted in Step 6 when you created the drive shipping import job had 4 rows, you'll have to create 4 separate mapping files, with each one having one row that corresponds to a specific SPO migration package.

  1. In Windows Explorer, copy the data import mapping file that you created in Step 5 and save it with a new file name that corresponds to a SPO migration package.

  2. Use Excel (or NotePad) to open the new file.

  3. Delete all the rows except the one that corresponds to the SPO migration package that you named the file for. Be sure to leave the header row.

  4. In the SPManifestContainer column, replace the current value with the manifest container name (that you generated in Step 7) that corresponds to the SPO migration package, and then save the file.

  5. Repeat step 1 through step 4 for each migration package.

Here's an example of the original data import mapping file for a drive shipping import job and three corresponding mappings files that were created from it. Note that the new mapping files have a single row and a new (and unique) value in the SPManifestContainer column.

Original mapping file

Workload,FilePath,Name,Mailbox,IsArchive,TargetRootFolder,SPFileContainer,SPManifestContainer,SPSiteUrl
SharePoint,,,,,,ContosoCorpSiteData,ContosoCorpSiteManifest,https://contoso.sharepoint.com/sites/ContosoCorpSite SharePoint,,,,,,adminData,adminManifest,https://contoso-my.sharepoint.com/personal/admin_contoso_onmicrosoft_com SharePoint,,,,,,saradData,saradManifest,https://contoso-my.sharepoint.com/personal/sarad_contoso_onmicrosoft_com SharePoint,,,,,,janetsData,janetsManifest,https://contoso-my.sharepoint.com/personal/janets_contoso_onmicrosoft_com

New mapping files

Workload,FilePath,Name,Mailbox,IsArchive,TargetRootFolder,SPFileContainer,SPManifestContainer,SPSiteUrl
SharePoint,,,,,,ContosoCorpSiteData,manifest-2016101218-b9922ffde1784377a5404dc4d0a2b407,https://contoso.sharepoint.com/sites/ContosoCorpSite
Workload,FilePath,Name,Mailbox,IsArchive,TargetRootFolder,SPFileContainer,SPManifestContainer,SPSiteUrl
SharePoint,,,,,,adminData,manifest-2016101217-30170d684bbd4030bd3200e323c4ff87,https://contoso-my.sharepoint.com/personal/admin_contoso_onmicrosoft_com
Workload,FilePath,Name,Mailbox,IsArchive,TargetRootFolder,SPFileContainer,SPManifestContainer,SPSiteUrl
SharePoint,,,,,,saradData,manifest-2016101222-a41b2f6f4996436faa9610a4365ab6a6,https://contoso-my.sharepoint.com/personal/sarad_contoso_onmicrosoft_com
Workload,FilePath,Name,Mailbox,IsArchive,TargetRootFolder,SPFileContainer,SPManifestContainer,SPSiteUrl
SharePoint,,,,,,janetsData,manifest-2016101222-b850987c7a7047da84fd0f0ddcf0c577,https://contoso-my.sharepoint.com/personal/janets_contoso_onmicrosoft_com

Return to top

Step 10: Create a data import job for the manifest files

The last step is to create a data import job in the Import service in Office 365 for the manifest files that you uploaded to Azure in Step 8. As previously explained, you can submit multiple data mapping files (that you created in the previous step) for a single import job. After you create the new import job, the Import service will use the information in the mapping files to import the data on the hard drive that you shipped to Microsoft.

  1. Go to https://protection.office.com.

  2. Sign in to Office 365 using the credentials for an administrator account in your Office 365 organization.

  3. In the left pane, click Data governance and then click Import.

  4. On the Import page, click Go to the Import service.

  5. On the Import data to Office 365 page, click New job Add Icon , and then click Upload SharePoint or OneDrive data.

  6. On the Upload files over the network page, click the I'm done uploading my files and I have access to the mapping file check boxes, and then click Next.

  7. Type a name for the manifest import job, and then click Next.

  8. Click Add Add Icon to select an import mapping file that you created in Step 9.

  9. After the name of the CSV file appears in the list, select it and then click Validate to check your CSV file for errors.

    The CSV file has to be successfully validated to create a data import job. If the validation fails, click the Invalid link in the Status column. A copy of your mapping file is opened, with a error message for each row in the file that failed.

  10. Add and validate additional mapping files, if applicable, that you created in Step 9.

  11. When the mapping files are added and validated, read the terms and conditions document, and then click the checkbox.

  12. Click Finish to submit the job.

    The job is displayed in the list of import jobs on the Import data to Office 365 page.

  13. Select the job and click Refresh Refresh icon to update the status information that's displayed in the details pane.

Return to top

What happens next

After your hard drive is received by Microsoft, the status for the import job on the Import data to Office 365 page will change to Drives received. Data center personnel will use the information in the journal file that you submitted when creating the import job to upload your SharePoint files to the Azure storage area for your organization. At this point, the status will change to Import in-progress. After the files are uploaded to Azure, the Import service uses the information in the import mapping file to import the data files to the target SharePoint or OneDrive for Business site.

At any point during the import process, you can click View details in the details pane for the selected import job to see detailed information and the current status. This includes information about individual files. When the import is complete and the data files have been imported to the target sites, the status will be changed to Completed.

Return to top

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!

×