VBA in Google Sheets: Macros to Apps Script Guide

Discover why VBA cannot run in Google Sheets, how to automate with Google Apps Script, and practical steps to migrate VBA macros to Apps Script for reliable Sheets workflows.

How To Sheets Team

March 26, 2026·5 min read

Google-Sheets-Vs-Excel Google-Sheets-API Templates-Google-Sheets

VBA to GAS Migration - How To Sheets — Photo by MART PRODUCTION via Pexels

vba in google sheets

vba in google sheets is a misnomer for automating Google Sheets; Google Sheets does not natively support Visual Basic for Applications, so VBA macros cannot run. Automation relies on Google Apps Script instead.

Why VBA in Google Sheets is Not Supported

VBA is designed for the Microsoft Excel object model, while Google Sheets uses its own automation layer built around Google Apps Script (GAS). Because of this architectural difference, VBA macros cannot execute inside Sheets, even if you save workbooks as Excel files. Your automation goals can still be achieved by translating VBA logic into GAS or by using the Macro Recorder to generate Apps Script code. When planning automation, set expectations that direct VBA portability is not possible; catalogue macros, prioritize by business impact, and identify which workflows gain the most value when rewritten for GAS. A practical mindset is to view VBA as a source of ideas rather than a runtime tool for Sheets. According to How To Sheets, the porting approach centers on functionally equivalent GAS implementations rather than literal VBA translation.

Note the fundamental distinction: VBA interacts with Excel’s object model, whereas Apps Script interacts with SpreadsheetApp and the Google Sheets API. Mapping these models is the first hurdle in any migration.

How Google Apps Script Works for Sheets Automation

Google Apps Script is a JavaScript-based scripting environment embedded in Google Workspace. For Sheets automation, GAS exposes the SpreadsheetApp service, giving access to Spreadsheet, Sheet, and Range objects to read, modify, and format data. Scripts can be bound to a sheet or run as standalone projects, and they may use triggers like onOpen and onEdit to automate responses to user actions. Since GAS runs on Google's servers, you don’t manage infrastructure, but you must be mindful of quotas and the synchronous/asynchronous nature of certain APIs. A typical migration task is to rewrite a VBA macro as a GAS function; you’ll often replace direct cell references with getRange and getValue/setValue calls. Here is a minimal example to set a value in A1:

function setA1Hello() {
  var sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  sheet.getRange('A1').setValue('Hello from GAS');
}

This example demonstrates the GAS workflow and how it differs fundamentally from VBA.

Migration strategies: translating VBA to Apps Script

Begin with a comprehensive inventory of all VBA macros and categorize them by the tasks they perform (data entry, formatting, reporting, automation). For each macro, identify core operations (read a range, perform calculations, write results) and map them to GAS equivalents. Translate Excel objects like Range and Worksheet into GAS concepts using SpreadsheetApp. Convert loops and conditionals to JavaScript patterns, and replace MsgBox with GAS alerts or prompts. A practical approach is to rewrite one macro at a time, test in a copy of the workbook, and gradually broaden scope. Expect some VBA patterns to require rethinking due to differences in object models and available methods; this is a normal part of migration and leads to more maintainable GAS code over time. In practice, teams that adopt a methodical migration plan see higher long term reliability in their Sheets automation.

Using Macro Recorder and custom menus in Google Sheets

Google Sheets includes a Macro Recorder (Tools > Macros > Record Macro) that captures user actions and saves them as Apps Script functions. This feature accelerates initial automation work and provides a GAS starting point you can refine. After recording, open the Apps Script editor to generalize the code, refactor for reuse, and extend with a custom menu so users can run macros from a friendly interface. A practical tip: pair recorded macros with a custom menu to improve discoverability and reduce user friction. This approach provides immediate value while you plan a robust GAS architecture for the spreadsheet.

Common VBA patterns and Apps Script equivalents

Translating common VBA patterns is the fastest way to gain momentum. Key mappings include:

VBA MsgBox and InputBox map to GAS alerts/prompts via SpreadsheetApp.getUi or Browser calls.
VBA Range references like Range("A1").Value become sheet.getRange("A1").getValue() and sheet.getRange("A1").setValue(...).
For loops and Do While loops translate to JavaScript for and while loops, often with array processing for efficiency.
Excel worksheet functions such as VLOOKUP can be reproduced with Sheets built in formulas or through Apps Script logic.
The VBA Worksheets collection becomes multiple GAS Sheet objects accessed via getActiveSpreadsheet().getSheetByName.

This mapping is the core of migration: focus on data access and transformation semantics, not verbatim syntax.

Pitfalls and limitations in cross platform automation

Migration introduces friction from several angles. Apps Script imposes quotas and limits on execution time and data access, which may affect long-running macros. Triggers like onEdit can behave differently when changes are scripted versus user-initiated. The Apps Script environment handles some operations asynchronously, so you may need to structure code to await results or chain actions carefully. User interaction patterns also differ; GAS dialogs and prompts have distinct UX implications compared with VBA message boxes. Finally, security and sharing settings differ between Excel macros and Google Sheets scripts, so follow least privilege practices and review script access regularly. Planning for these differences helps reduce surprises during deployment.

Real world examples: a simple macro to sort data

If you previously had a VBA macro that sorts a data range, you can implement an equivalent in Apps Script using range sorting. The GAS API supports sorting a range directly, keeping behavior within the Sheets environment. Below is a simplified comparison to highlight the idea. Note that the VBA example is shown in plain-language form, focusing on concept rather than exact syntax, while the GAS example demonstrates a direct approach in Sheets.

VBA concept (illustrative, not literal syntax):

Sub SortData() With ActiveSheet.Sort .SortFields.Clear .SortFields.Add Key:=Range("A1:A100"), Order:=xlAscending .SetRange Range("A1:F100") .Apply End With End Sub

Apps Script equivalent:

function sortData() {
  var sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
  var range = sheet.getRange('A1:F100');
  range.sort({column: 1, ascending: true});
}

The migration shows how VBA intent translates into GAS operations, but you must adjust references and APIs to fit your specific sheet layout.

FAQ

Can VBA run directly in Google Sheets?

No. Google Sheets does not support VBA. Automations must be built with Google Apps Script or Sheets-native features like the Macro Recorder. This requires translating logic rather than importing Excel VBA.

What should I use instead of VBA in Sheets?

Use Google Apps Script for automation and the built in Macro Recorder to capture actions that can be converted to GAS functions. For complex tasks, rewrite logic in Apps Script and test in a copy of your sheet.

Is there a converter from VBA to Apps Script?

There is no perfect automatic converter. You must translate VBA logic into Apps Script manually, mapping the Excel object model to GAS objects such as SpreadsheetApp, Sheet, and Range.

What is the first step in migrating VBA macros to Sheets?

Start by inventorying all VBA macros and prioritizing the ones with the highest business impact. Then rewrite one macro at a time in Apps Script, testing on a duplicate sheet before production use.

Can I still work with Excel VBA and Google Sheets together?

Yes, you can maintain Excel VBA for Excel files while using Google Apps Script for Sheets in parallel. If cross-file automation is needed, consider exporting data to Sheets or using Office Scripts where applicable.

What about UI and dialogs in GAS compared to VBA?

GAS uses SpreadsheetApp.getUi for dialogs and prompts, which differs from VBA’s MsgBox UX. Plan for a GAS specific UI model and test how dialogs affect user workflow.