Moving from Excel to Google Sheets without losing the logic

The file uploads in a second. It is the macros, the pivot caches and the external links that take the fortnight.

Google converts the grid faithfully. What it does not convert is VBA, Power Query, Power Pivot data models, cross-workbook links, most conditional formatting edge cases, and any formula that only ever worked because of how Excel handles volatile recalculation. Teams discover this a week after switching.

We migrate deliberately: audit first, rebuild the automation in Apps Script, re-point the links, and then run both versions side by side against the same inputs until the outputs match to the cent. Only then do we retire the Excel file.

You probably recognise at least one of these

VBA macros that have no equivalent once the file is in Drive
Power Query steps with nowhere to go
Pivot tables that lose their calculated fields on conversion
Links to other workbooks that break the moment the folder structure changes
A team half-migrated, with two versions of the truth

What you get

A migration audit listing every feature that will not survive conversion, with a planned replacement for each
The rebuilt workbook in Sheets, structured for collaborative editing rather than single-user use
VBA logic re-implemented in Apps Script, with triggers where the macro was manual
A parallel-run reconciliation showing old and new outputs matching
Sharing and permission structure set up properly at handover

How the engagement runs

Audit

We open the workbook and inventory the automation, links and features at risk. You get the audit whether or not you proceed.

Fixed quote

Priced from the audit.

Rebuild

Automation first, formatting last.

Parallel run

Both files, same inputs, matched outputs, signed off before the Excel version is retired.

Questions we get asked

Can our VBA just be converted automatically?

No. There is no reliable VBA-to-Apps-Script converter, and anything claiming otherwise will leave you with code nobody can maintain. It is a rewrite, and we price it as one.

Should we migrate at all?

Sometimes not. If the workbook is a single-user model with heavy Power Pivot use, Excel is the right tool and we will tell you so — we also run Excel consultancies, so we have no reason to push you either way.

What about the file history?

Version history moves with the file once it is a native Sheet. Pre-migration history stays with the original, which we recommend archiving read-only rather than deleting.

Tell us what it needs to do

Share the file or describe the outcome. We reply with scope, price and a delivery date.

Get a fixed quote