Convert XLSM to Google Sheets Without Losing Macros (2026 Guide)

If you are trying to convert an XLSM file to Google Sheets and keep your macros working, this guide starts with the honest answer: it is not possible in the way you might hope. Google Sheets does not run VBA. It never will. The two platforms use fundamentally different automation systems that are not interoperable at the code level.

But here is what is possible: migrating the logic behind your macros into Google Apps Script, so that your Google Sheet does the same things your Excel macros did — just using a different codebase. This guide explains how to do that migration correctly, when it is worth the effort, and when you should simply keep Excel.

The Honest Answer: Google Sheets Does Not Run VBA

When you upload or import an XLSM file into Google Drive and open it as a Google Sheet, here is exactly what happens:

• Cell values, formulas, and most formatting are imported
• Named ranges are imported
• Charts are imported with varying fidelity
• All VBA modules, UserForms, and class modules are silently discarded
• Worksheet-level event code (e.g., Worksheet_Change) is discarded
• ActiveX controls are dropped or converted to non-functional placeholders

There is no error message, no warning dialog, and no partial execution. Google's import pipeline simply has no VBA runtime — it reads the data and ignores everything else. The vbaProject.bin container inside your XLSM is treated as an unknown binary and discarded.

Understanding the Platform Difference

VBA (Visual Basic for Applications) is a COM-based language that runs inside Microsoft Office applications. It has direct access to the Excel object model, the Windows file system, Windows APIs, COM objects, and ActiveX controls. It runs synchronously in the application process.

Google Apps Script is a JavaScript ES5-based cloud scripting language. It runs on Google's servers, not in your browser. It has access to Google Workspace APIs (Sheets, Drive, Gmail, Calendar, etc.) but no access to local file systems, Windows APIs, or COM objects. It runs asynchronously with quota limits on execution time and API calls.

These are not two implementations of the same idea — they are entirely different architectures serving related but distinct purposes.

The Apps Script Migration Path

If the business logic in your VBA is the valuable thing — not the VBA itself — then Apps Script migration is viable. Here is the correct process.

Step 1: Audit Your VBA Modules

Before writing a single line of Apps Script, fully document what your VBA does. Open the VBA editor (Alt + F11) and for each module, write down:

• The procedure name and purpose
• What triggers it (button click, Workbook_Open, time-based, etc.)
• What data it reads and from where
• What it produces or modifies
• Any external dependencies (file system, database connections, COM objects)

External dependencies are the blockers. If your macro reads from a local SQL Server database, accesses a Windows network share, or calls a COM object, that code cannot be migrated to Apps Script without replacing the data source as well.

Step 2: Import the Data into Google Sheets

Upload the XLSM to Google Drive, then right-click → Open with → Google Sheets. Review the imported data for accuracy. Pay attention to:

• Date and number formatting differences
• Formula syntax differences (most Excel formulas convert automatically, but some advanced functions do not exist in Sheets)
• Merged cells and conditional formatting fidelity

Step 3: Rewrite in Apps Script

Open the Apps Script editor via Extensions → Apps Script. Below is a comparison of common VBA patterns and their Apps Script equivalents.

Here is a minimal Apps Script example of a procedure that mirrors a common VBA task — iterating a column and highlighting rows based on a condition:

function highlightOverdueRows() {
  var ss = SpreadsheetApp.getActiveSpreadsheet();
  var sheet = ss.getSheetByName("Tasks");
  var data = sheet.getDataRange().getValues();
  var today = new Date();

  for (var i = 1; i < data.length; i++) {
    var dueDate = new Date(data[i][3]); // Column D
    var status = data[i][4];           // Column E

    if (dueDate < today && status !== "Complete") {
      sheet.getRange(i + 1, 1, 1, data[0].length)
           .setBackground("#3d1515");
    }
  }
}

Step 4: Attach Triggers

Apps Script triggers replace VBA event procedures. Go to the Apps Script editor → Triggers (clock icon) → Add Trigger. Common trigger mappings:

• On open — replaces Workbook_Open and Auto_Open
• On edit — replaces Worksheet_Change, but note it fires on any cell edit, not just specific ranges
• Time-driven — replaces Application.OnTime scheduled procedures

What Cannot Be Migrated

Be realistic about the following VBA patterns before committing to a migration:

• UserForms: Google Sheets has no equivalent native dialog system. You can build custom HTML dialogs using HtmlService, but it requires HTML/CSS/JavaScript skills and is not a simple port.
• ActiveX controls: Buttons, combo boxes, and list boxes embedded in worksheets must be replaced with Google Sheets drawing-based buttons linked to Apps Script functions — a manual process for each control.
• File system access: Any VBA that reads or writes local files (Open filepath For Input) cannot be migrated directly. The equivalent is Google Drive API access, which requires OAuth and different file handling logic.
• Windows API calls: Declare Function calls into Windows DLLs have no equivalent in Apps Script.
• Performance-critical loops: Apps Script has a 6-minute execution limit and significantly lower throughput than VBA for large-range operations. A VBA macro that processes 100,000 rows in 10 seconds may time out in Apps Script.

When to Keep Excel

Google Sheets is an excellent collaborative tool. But it is not a drop-in replacement for Excel with macros. If your workflow depends on VBA-heavy automation, the migration cost is real and should be estimated carefully before committing.