Home > Google Drive Migration > Migration to SharePoint Online / OneDrive Migration

    Export to PDF

    Migration to SharePoint Online / OneDrive Migration

    Refer to the table below to view the supported and unsupported object types for Google Drive to SharePoint Online / OneDrive migration.

    *Note: The object types that are not listed in the table below are not supported.

    √ – Supported; × – Unsupported.

    Object TypeService Account Authentication Support StatusApp Profile Support StatusComment
    My DriveSuspended or archived users are not supported.
    Shared Drive
    Hold Google Drive Filexx
    Folder
    FileFor information on Google API limitations and export formats that can affect how Fly migrates files, see Download & export files.When the file version is restored, if the latest version name is different from the file name, the latest version name is used as the file name of the target end.
    Google DocsPartially SupportedPartially SupportedDue to Google API limitations, the major version history of Google Docs, Google Sheets, and Google Drawings may not be correctly migrated to the destination. The minor version history cannot be migrated.Google Sheets files can be migrated as Microsoft Excel files, and the content can be correctly migrated. However, the functions/Google Apps Script/formulas may not work in the Excel files in the destination.Google Drawings files can be migrated as PNG files. However, the dynamic effect is not supported in the PNG files in the destination.
    Google SheetsPartially SupportedPartially SupportedDue to Google API limitations, the major version history of Google Docs, Google Sheets, and Google Drawings may not be correctly migrated to the destination. The minor version history cannot be migrated.Google Sheets files can be migrated as Microsoft Excel files, and the content can be correctly migrated. However, the functions/Google Apps Script/formulas may not work in the Excel files in the destination.Google Drawings files can be migrated as PNG files. However, the dynamic effect is not supported in the PNG files in the destination.
    Google DrawingsPartially SupportedPartially SupportedDue to Google API limitations, the major version history of Google Docs, Google Sheets, and Google Drawings may not be correctly migrated to the destination. The minor version history cannot be migrated.Google Sheets files can be migrated as Microsoft Excel files, and the content can be correctly migrated. However, the functions/Google Apps Script/formulas may not work in the Excel files in the destination.Google Drawings files can be migrated as PNG files. However, the dynamic effect is not supported in the PNG files in the destination.
    Google SlidesPartially SupportedPartially SupportedThe major and minor version history of slides cannot be migrated.
    Google FormsPartially SupportedPartially SupportedThe source Google Form is migrated as a ZIP file in the destination. The questions and options of the form are migrated as a static HTML file in the ZIP file; the responses to the questions are stored in a CSV file in the ZIP file.Google Forms can be migrated to the destination. However, the major and minor version history of the forms cannot be migrated.There is a 10 MB limit on exported Google content. For information on Google API limitations that can affect how Fly migrates Google Forms, see Method: files.export.
    Google VidsPartially SupportedPartially SupportedThe source Google Vid is migrated as an .mp4 file in the destination.Versions cannot be migrated.
    Google My Maps××
    Google Sites××
    Google Apps Script××
    Google JamboardThe major and minor version history of Jamboards cannot be migrated.Google Jamboards can be migrated as PDF files. However, the dynamic effect is not supported in the PDF files in the destination.
    Google Photos××
    Connect More Apps××
    Shortcut××
    Third-party Shortcut××
    Google Fusion Tables××
    Computers××
    Sharing Links××

    *Note: After the Google Drive migration, the storage in the destination may be different from that in the source due to the following situations:

    - Some object types are not supported in the migration. - Some item versions cannot be migrated to the destination. - The data size may be different after the data type is converted in the destination.