Docs Migration: Google Docs, Sheets, and Slides to Microsoft Office¶

Status: Authored 2026-04-30 Audience: M365 administrators, migration engineers, and business application owners managing the transition from Google productivity apps to Microsoft Office. Scope: Format conversion fidelity, formula compatibility (Sheets to Excel), macro migration (Apps Script to VBA/Office Scripts/Power Automate), and template migration.

Overview¶

Google Docs, Sheets, and Slides automatically convert to Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) during Drive migration via Migration Manager. The file-level conversion is largely automated and high-fidelity for most documents. The primary migration challenges are:

1. Apps Script macros --- Google's JavaScript-based automation does not convert to Microsoft formats.
2. Google Sheets-specific functions --- Some Sheets functions have no direct Excel equivalent.
3. Templates and workflows --- Organizational templates must be recreated.
4. Add-on integrations --- Google Workspace Marketplace add-ons must be replaced with Office add-ins.

Google Docs to Word conversion¶

What converts well¶

What may need manual adjustment¶

Best practice¶

After migration, spot-check a representative sample of documents:

• 5 simple documents (memos, letters).
• 5 complex documents (reports with tables, images, TOC).
• 5 documents with comments/suggestions.
• 3 documents with embedded charts or drawings.
• 2 documents with headers/footers and page numbers.

Google Sheets to Excel conversion¶

Formula compatibility¶

Google Sheets and Excel share most common formulas. Migration Manager converts Sheets formulas to Excel equivalents automatically.

Formulas that convert directly (no changes needed)¶

Formulas that require manual adjustment¶

Google Sheets functions with no Excel equivalent¶

Chart conversion¶

Pivot table conversion¶

Google Sheets pivot tables convert to Excel PivotTables with high fidelity. Key differences:

Apps Script to Microsoft migration¶

Apps Script is the single most complex migration challenge. Google Apps Script is a JavaScript-based platform tightly integrated with Google Workspace. There is no automated conversion to Microsoft equivalents.

Migration strategy by complexity¶

Apps Script to Office Scripts mapping¶

Example: Apps Script to Office Scripts conversion¶

Google Apps Script (bound to a Sheet):

function formatReport() {
    var sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
    var range = sheet.getDataRange();
    var values = range.getValues();

    for (var i = 1; i < values.length; i++) {
        if (values[i][3] > 100000) {
            sheet.getRange(i + 1, 4).setBackground("#90EE90");
        }
    }
}

Office Scripts equivalent:

function main(workbook: ExcelScript.Workbook) {
    let sheet = workbook.getActiveWorksheet();
    let range = sheet.getUsedRange();
    let values = range.getValues();

    for (let i = 1; i < values.length; i++) {
        if ((values[i][3] as number) > 100000) {
            sheet
                .getRange(`D${i + 1}`)
                .getFormat()
                .getFill()
                .setColor("#90EE90");
        }
    }
}

Apps Script to Power Automate mapping¶

For scripts that interact with email, Drive, Calendar, or external APIs, Power Automate is the recommended replacement:

Template migration¶

Organizational templates¶

Google Workspace organizational templates (stored in the template gallery) must be manually recreated in Microsoft 365.

Migration steps¶

1. Export templates from Google Workspace:

   • Navigate to Google Docs/Sheets/Slides template gallery.
   • Download each template as .docx/.xlsx/.pptx.

2. Upload to SharePoint:

   • Create a "Templates" document library in SharePoint.
   • Upload converted templates.
   • Configure as organizational templates in M365 admin center.

3. Configure M365 template locations:

# Set organizational template location in SharePoint
# Templates uploaded to: https://contoso.sharepoint.com/sites/templates/Documents
# Configure in M365 admin center > Settings > Org settings > Office templates

1. Brand templates with organizational identity:
   • Update headers, footers, and logos in Word templates.
   • Apply organizational color palette in PowerPoint templates.
   • Configure default fonts and styles.

Personal templates¶

Users with personal templates in Google Workspace should:

1. Open templates in Google Workspace.
2. Download as Office format.
3. Save to OneDrive in a "Templates" folder.
4. Pin the folder in Office apps for quick access.

Post-conversion validation checklist¶

Documents (Google Docs to Word)¶

• Text content is complete and correctly formatted.
• Images are present and positioned correctly.
• Tables are intact with correct formatting.
• Headers and footers are preserved.
• Table of contents is functional (may need refresh).
• Comments and tracked changes are preserved.
• Hyperlinks are functional.
• Page numbering is correct.

Spreadsheets (Google Sheets to Excel)¶

• All formulas calculate correctly.
• Charts render with correct data and formatting.
• Pivot tables function and refresh correctly.
• Conditional formatting rules are preserved.
• Data validation rules are intact.
• Named ranges are preserved.
• Cross-sheet references work.
• IMPORTDATA/IMPORTRANGE formulas are replaced with Power Query (if applicable).
• Apps Script macros are documented for rebuild.

Presentations (Google Slides to PowerPoint)¶

• All slides are present with correct layouts.
• Animations and transitions are preserved.
• Embedded media (images, videos) display correctly.
• Speaker notes are preserved.
• Slide master/layouts are intact.
• Fonts are available (install any missing fonts).

Google Workspace add-on to Office add-in mapping¶