Your Files Have Macros. But Will They Work in Google Workspace?
Finding out that a spreadsheet contains macros is useful. But for an organization preparing to move from Microsoft Office or WPS Office to Google Workspace, that is only the beginning.
The more important question is:
What does that macro actually depend on, and can the same workflow continue after migration?
Macros can support reporting, repetitive tasks, data processing, integrations, scheduled activities, and other important business processes. Some functionality may have a path into Google Workspace, while other dependencies may require redesign or a different approach.
That is why Google Endpoints Readiness Tool (GRT) is expanding Workspace Readiness with Macro Compatibility & VBA Dependency Assessment, helping organizations move beyond simply detecting macros and understand what those dependencies could mean for migration.
Knowing a Macro Exists Is Not Enough
Imagine an organization preparing hundreds or thousands of Office files for a move to Google Workspace.
The migration team discovers that several files contain macros.
That tells them there is a dependency, but it does not answer the questions they actually need for planning:
What does the VBA do?
Does it depend on Microsoft Office or Windows-specific functionality?
Could the workflow be recreated using Google Apps Script?
Will it require redevelopment before users can move?
Without that context, teams may know where macros exist but still have little visibility into the amount of work required to address them.
GRT Goes Deeper Into VBA Dependencies
The new assessment is designed to analyze accessible VBA information collected through GRT's existing File Scanner and identify dependency patterns that may affect Google Workspace migration.
Instead of stopping at macro detection, GRT looks for functionality connected to areas such as:
Microsoft Office application automation
external applications and integrations
local file operations
database and HTTP communication
scheduled and event-based automation
Windows-specific functionality
This gives migration teams more context around what the existing macro relies on, rather than simply showing that VBA is present.
Macro Coverage Depends on How the Application Is Used
GRT's macro assessment also differs between browser-based and installed Office applications.
For browser-based application usage, macro assessment is available for Microsoft applications. WPS browser applications are not included in macro assessment.
For installed applications, GRT can assess macro usage across both Microsoft Office and WPS Office.
This distinction helps teams understand exactly where macro visibility is available within their existing environment and prevents browser-based and installed application readiness from being treated as the same assessment.
From “Macro Detected” to a Clearer Compatibility View
GRT then evaluates detected VBA functionality against predefined compatibility rules.
The assessment groups findings into three categories:
Compatible The detected VBA functionality satisfies the supported compatibility rules.
Partially Compatible The functionality may have a path within Google Workspace, but rewriting or redesign may be required using Google Apps Script or another Google Workspace service.
Not Compatible The existing VBA implementation relies on unsupported dependencies, particularly Windows-specific or operating-system-level functionality that cannot run directly in Google Apps Script.
This gives IT teams a much more useful starting point for migration planning.
Instead of seeing one large group of “files with macros,” they can begin separating straightforward cases from workflows that need deeper investigation.
Some Macros May Need Redesign, Not Replacement
A Partially Compatible result does not necessarily mean the business workflow has to disappear.
It means the existing VBA implementation may need to be approached differently in Google Workspace.
For example, an existing macro might automate Microsoft Outlook, communicate with a database, schedule an action, generate a print workflow, or interact with local files.
Some of these activities may have alternatives through Google Workspace services or Google Apps Script, but the implementation may need to be rewritten.
This distinction is important.
The question changes from:
“Does this VBA code work exactly as it is?”
to:
“Can this business process be redesigned for the Google Workspace environment?”
Some Dependencies Need More Attention
Other VBA functionality can depend heavily on Windows itself.
Examples can include Windows API calls, launching external programs, controlling desktop windows, accessing the Windows Registry, working directly with the local file system, or using Windows COM objects.
These dependencies cannot simply run in Google Apps Script in the same way.
Identifying them before migration helps teams recognize where a workflow may need a more significant redesign or a different solution.
It also reduces the risk of finding out after migration that an important workflow depends on functionality that is no longer available.
Understanding Why a Macro Is Limited Matters
A compatibility label alone is useful, but the reason behind it is even more valuable.
The enhanced assessment is designed to show which VBA dependency was identified, why it creates a compatibility limitation, and whether the functionality may require redesign or relies on an unsupported dependency.
This gives migration teams something actionable.
Instead of telling a business team:
“This macro may not work.”
IT can have a more informed conversation about what part of the existing automation needs attention and what kind of migration effort may be required.
GRT Can Also Highlight Potential Apps Script Dependencies
Google Workspace uses Google Apps Script for automation rather than VBA.
For functionality that may have a Google Workspace path, GRT can identify where redevelopment using Apps Script or other supported Workspace services may need to be considered.
That does not mean every VBA function has a direct Apps Script replacement.
It means teams can identify where rewriting or workflow redesign should become part of the migration plan.
Importantly, GRT is designed to assess and highlight these dependencies — not automatically convert VBA code into Apps Script.
Why This Changes Workspace Migration Planning
Macro dependencies can be easy to underestimate because the business logic is often hidden inside familiar Office files.
A spreadsheet may look like an ordinary document while supporting a process employees rely on every week.
Knowing that a macro exists is useful.
Knowing whether it is compatible, what it depends on, why it may not work, and where redevelopment could be required is much more valuable.
That additional visibility helps migration teams:
identify compatibility risks earlier
focus investigation on files that need the most attention
understand where Apps Script redesign may be required
recognize Windows-specific dependencies
estimate redevelopment needs before migration
make more informed Workspace migration decisions
Move From Macro Discovery to Migration Readiness
Google Endpoints Readiness Tool helps organizations understand application usage and Workspace migration readiness across their current environment.
With macro assessment, the level of visibility depends on the application environment: browser-based macro assessment covers Microsoft applications, while installed application assessment can include both Microsoft Office and WPS Office.
Macro Compatibility & VBA Dependency Assessment takes that readiness view further.
Instead of only answering:
“Where do we have macros?”
organizations can begin answering:
“Which macros can move, which need redesign, and which dependencies require a different plan?”
That is a much stronger starting point for a Google Workspace migration.
Because when business workflows depend on macros, migration readiness is not simply about finding them.
It is about understanding what is behind them before users move.
FAQ
What is Macro Compatibility & VBA Dependency Assessment?
It is an enhancement to GRT Workspace Readiness designed to analyze accessible VBA functionality, identify dependencies, and provide compatibility insights for organizations preparing to migrate to Google Workspace.
Does GRT assess macros in both Microsoft Office and WPS Office?
For installed applications, GRT can assess macro usage across both Microsoft Office and WPS Office. For browser-based applications, macro assessment is currently focused on Microsoft applications and does not include WPS browser applications.
What compatibility results can GRT provide?
Analyzed VBA functionality can be classified as Compatible, Partially Compatible, or Not Compatible based on identified dependencies and predefined compatibility rules.
What does Partially Compatible mean?
It means the existing VBA functionality may have a possible path in Google Workspace but requires rewriting or redesign, potentially using Google Apps Script or another supported Workspace service.
Does GRT automatically convert VBA macros into Google Apps Script?
No. The feature identifies potential Apps Script redevelopment dependencies and migration considerations, but it does not automatically rewrite or convert VBA code.
How does this help with Google Workspace migration?
It gives migration teams earlier visibility into macro dependencies, compatibility limitations, potential redesign requirements, and areas that require further investigation before users are moved.
