During the migration to OneDrive, Google files such as Docs, Sheets, and Slides will be automatically converted to their Microsoft equivalents, Word, Excel, and PowerPoint.

Below, you'll find a series of guides designed to help you understand and prepare for any potential issues that may arise during this transition.

 

Migrated file guides

Migrating from Google Docs to Microsoft Word

Migrating from Google Docs to Microsoft Word can introduce several challenges, especially if you are accustomed to Google’s environment. Here are some common issues colleagues may face:

Microsoft Word uses a feature-rich ribbon interface, which can feel more complex for users accustomed to Google Docs’ minimalist design. For example, Word includes multiple tabs such as References, Mailings, and Review, each with advanced tools, whereas Google Docs keeps most options in a simpler, single toolbar. 

Google Apps Script is not supported in Microsoft Word. Any functionality built using Apps Script will not transfer and must be reimplemented using an alternative Microsoft technology. For example, if your Google Docs used Apps Script to automate document formatting, you could recreate this in Word using VBA (Visual Basic for Applications), Power Automate, or Office Scripts.

When converting a Google Docs file (.gdoc) to a Microsoft Word file (.docx), some formatting may be lost or altered. For example, styles, spacing, and page layout might not transfer perfectly, which can affect the overall look of the document. Additionally, embedded objects such as charts, drawings, or diagrams may not render correctly in Word and could require manual adjustment or reinsertion.

Google Docs tends to rely on simpler, ad‑hoc formatting. Word is built around Styles, Themes and template files. After conversion, apply Word’s built‑in Styles for headings, normal text and captions, then save a .dotx template so future documents inherit the same look and behaviour. This improves consistency, navigation and automatic tables of contents. 

Docs has simpler pagination. Word uses section breaks for different headers, footers, margins and orientation within one file. If pages look wrong post‑migration, replace page breaks with the correct section breaks, set Different first page or Different odd and even where needed, and reapply margins and orientation per section.

Word uses fields for dynamic content such as tables of contents, figure lists, cross‑references, dates and file properties. After conversion, select the document and press F9 to update fields, or right‑click and Update field per item. Re‑create cross‑references using Insert reference so they stay live.

Google’s equations may convert imperfectly. Re‑enter key equations using Word’s Equation Editor, insert symbols via Insert, Symbol, and consider converting unfixable equations to images as a last resort to preserve appearance.

Because Google Docs and Microsoft Word work differently, some embedded features may stop working after migration. For example, Google Docs’ smart chips (such as @mentions or linked files) do not exist in Word and will not transfer. Similarly, embedded links within the document may break during conversion.

If you find that features or links no longer work as expected after migration, you will need to fix them manually. This may involve replacing Google-specific features with Word equivalents (e.g., using Word’s Comments instead of @mentions) and updating any broken links so they point to the correct files or locations. 

Content linked to Google Sheets or Google Drawings will not remain live. Recreate charts using Excel data, then paste as a linked chart or embed the Excel object. For drawings, re‑insert as images or rebuild with Word shapes. Use Paste Special to control whether visuals are embedded, linked or pasted as images for stability. 

Google Some Google Docs features, such as smart chips (e.g., @mentions or file links), do not exist in Microsoft Word and will not transfer during migration. These elements will need to be removed or replaced manually. 

On the other hand, Microsoft Word offers more advanced formatting and layout tools, such as Styles, Themes, and Section Breaks, which may require reworking your document for consistency. For example, if your Google Doc uses simple manual formatting, you might need to apply Word’s built-in styles to maintain a professional and consistent look. 

Hyperlinks to Google Drive content may break or become inaccessible after migration if they are not updated properly. For example, a link to a Google Doc or Sheet stored in Google Drive will not work for users who only have access to the new Microsoft environment. These links should be replaced with updated paths to the equivalent files in OneDrive or SharePoint.

Google Docs add-ons may not have direct equivalents in Microsoft Word. This means you may need to adjust your workflow or use alternative tools available in Word. For example, if you used a Google Docs add-on for document translation, you might need to switch to Word’s built-in Translate feature under the Review tab or use Microsoft Translator. 

Migrating from Google Sheets to Microsoft Excel

Migrating from Google Sheets to Microsoft Excel can introduce several challenges, especially if you are accustomed to Google’s environment. Here are some common issues colleagues may face:

Microsoft Excel has a feature-rich interface, which can feel more complex for users who are used to the simpler layout of Google Sheets. For example, Excel includes multiple ribbons, advanced charting options, and tools like Power Query, which may seem overwhelming at first. In contrast, Google Sheets has a more minimal design with fewer menus and options.

Google Apps script is not supported in Microsoft Excel and functionality will need to be reimplemented in an appropriate alternative technology e.g. Microsoft Excel VBA, Power Automate or Office Scripts in Excel.

Because Google Sheets and Microsoft Excel work differently, some functions and formulas may stop working after the file is migrated. 

 

Google-specific functions

Google‑specific functions such as GOOGLEFINANCE(), GOOGLETRANSLATE(), or IMPORTDATA() simply don’t exist in Excel. To replace them, you can use Power Query for importing data from web sources or CSV files, and for translations, Microsoft offers a built‑in Translate feature or the Microsoft Translator add‑in. For financial data, you may need to connect to a data provider or use Excel’s stock data types. 

Array formulas and dynamic ranges

One of the biggest differences is how formulas behave. Google Sheets uses ARRAYFORMULA() to spill results across multiple cells, whereas Excel handles this with dynamic arrays in newer versions or with array formulas entered using Ctrl+Shift+Enter in older versions. If you see broken array logic after migration, you’ll need to rewrite it using Excel’s equivalents like SEQUENCE(), FILTER(), or by converting ranges into Excel Tables for structured references.

Converting a Google Sheets file (.gsheet) to an Excel file (.xlsx) can cause formatting issues. For example, while most formatting will migrate successfully, cell colours, merged cells, or conditional formatting may not appear the same in Excel so you may need to check and amend these

Conditional formatting rules often need attention after migration. Some rules from Google Sheets don’t translate well, so you may need to recreate them using Excel’s Conditional Formatting Manager. For complex logic, Excel supports formula‑based rules, which can replicate most scenarios.

Another common issue is linked data. If your Google Sheets relied on links to other Sheets or Google Drive files, those links will break. The best approach is to move the source files into OneDrive or SharePoint and then update the references, or consolidate the data into a single workbook using Power Query.

In most cases, basic data validation lists will migrate from Google Sheets to Excel and still work. Simple dropdowns may survive, but anything dynamic or dependent are likely to need manual rework in Excel.  For example; 

If the  dropdown in Google Sheets references a static list in the same sheet, Excel usually preserves it. 

If the dropdown references a range on another sheet, Excel often converts it into a static list or breaks the reference entirely, because Excel’s data validation does not allow direct cross-sheet references in the same way Google Sheets does. 

Dynamic dropdowns (where the list expands automatically) will not migrate as dynamic. Excel will treat them as fixed ranges unless you convert the source into an Excel Table and reapply validation. 

Cascading dropdowns (where the second list depends on the first) will not work after migration. You’ll need to rebuild them using Excel’s INDIRECT() function or VBA.

Pivot tables and charts usually migrate, but calculated fields or filters can break. Rebuilding them in Excel is often the quickest fix, and if you need more advanced modelling, Power Pivot is a strong option.

Comments and collaboration features differ — Google’s comments and @mentions don’t carry over, so you’ll need to re‑add them using Excel’s modern threaded comments if you’re on Microsoft 365. 

Some Google Sheets add-ons do not have direct equivalents in Microsoft Excel. This means you may need to find alternative solutions or create manual workarounds. For example, if your Google Sheet uses an add-on to pull data from an external API, Excel will not automatically replicate this functionality. You might need to use Excel’s built-in features, such as Power Query, or manually import the data instead. 

Migrating from Google Slides to Microsoft PowerPoint

Migrating from Google Slides to Microsoft PowerPoint can introduce several challenges, especially if you are accustomed to Google’s environment. Here are some common issues colleagues may face:

Microsoft PowerPoint uses a feature-rich ribbon interface, which can feel more complex for users accustomed to Google Slides’ minimalist design. For example, PowerPoint includes multiple tabs such as Design, Transitions, and Animations, each with advanced options, whereas Google Slides keeps most tools in a simpler, single toolbar.

Layouts, Fonts & Themes

When converting a Google Slides file (.gslides) to a PowerPoint file (.pptx), slide layouts, fonts, and spacing may change, especially if the original presentation used custom fonts or themes. For example, a slide that uses a Google-only font like Roboto may appear differently in PowerPoint if that font is not installed, and custom theme colours might not transfer exactly, affecting the overall design.

Google Slides supports only basic transitions, so any advanced motion effects will need to be rebuilt in PowerPoint. If you want to enhance the presentation, consider using PowerPoint’s Morph transition or Animation Pane to replicate or improve the original flow.

Some Google Slides features, such as smart chips (e.g., @mentions or links to Google Docs/Sheets), do not exist in Microsoft PowerPoint. These elements will not transfer during conversion and may need to be removed or replaced manually. 

On the other hand, PowerPoint offers more advanced animation and transition effects than Google Slides. If your original presentation uses Google’s basic transitions, you may want to rework them in PowerPoint to take advantage of its richer options.

Hyperlinks to Google Docs, Sheets, or Forms usually break. Replace them with OneDrive or SharePoint links, or embed the relevant file as an object if you need offline access. Interactive elements like Google Forms cannot be replicated natively in PowerPoint, so you’ll need to link to Microsoft Forms or redesign the interaction.

Videos, charts, or drawings embedded in Google Slides may not transfer correctly when converting to PowerPoint. In some cases, these elements might not appear at all and will need to be re-inserted manually. For example, a YouTube video embedded in Google Slides may not play in PowerPoint and will require adding the video again using PowerPoint’s Insert → Video feature. For charts linked to Google Sheets, export the data to Excel and re‑link the chart in PowerPoint. Drawings and Diagrams. 

Google Drawings or embedded diagrams often flatten into static images. If you need them editable, recreate them using PowerPoint’s shapes or SmartArt.

Google’s commenting system is simple and integrated. PowerPoint uses threaded comments, which may feel different.

Converting files between Google Slides and PowerPoint can sometimes cause broken links, formatting issues, or loss of interactive elements. For example, hyperlinks to Google Docs or Sheets may no longer work in PowerPoint, and interactive features like embedded Google Forms will not transfer. These elements may need to be updated or recreated manually after conversion.

Some Google Slides add-ons do not have direct equivalents in Microsoft PowerPoint. This means you may need to adjust your workflow or find alternative tools within PowerPoint. For example, if you used an add-on in Google Slides to insert live polls, you’ll need to replace it with a PowerPoint feature such as Microsoft Forms integration or another supported add-in.

Microsoft PowerPoint includes advanced tools that go beyond what Google Slides offers. For example, Morph transitions allow smooth object movement between slides, Slide Master enables consistent design across an entire presentation, and Presenter Coach provides real-time feedback on your delivery during practice sessions. These features can significantly enhance presentation quality and interactivity compared to Google Slides.