Migrations
Moving from Excel macros and VBA to automated workflows
Macros often carry important work and only one person understands them. Rebuilding them as workflows makes that work visible and repeatable.
Last reviewed 14 November 2026
Replace Excel macros and VBA when the person who wrote them has left or is the only one who can run them, when they run on one laptop, or when security policy blocks macros. Document what each macro does, rebuild it as a scheduled workflow in n8n or Power Automate with data in a database, and compare outputs against the macro for a few cycles before retiring it.
Who this is for
Finance and operations teams with month-end, reporting or pricing work that depends on VBA in one or two workbooks.
Signs it is time to move
- One person runs the macro and holidays delay the process
- Macros are blocked by security settings on downloaded files
- The workbook breaks when a column moves
- The macro pulls data by copying and pasting from other systems
What it costs on each side
Excel is already paid for in Microsoft 365. The cost of the macro is the time spent running and fixing it and the risk of it failing at month end. A workflow adds a platform fee and a build cost, which we set against those hours during the audit.
The migration plan, step by step
- 01
Inventory
List every workbook with macros, what triggers them, the inputs and outputs, and who runs them.
- 02
Map
Read the VBA line by line and write the steps in plain language, including the edge cases it handles.
- 03
Rebuild
Pull inputs from the source systems by API, apply the rules in the workflow, and write outputs to a database, sheet or report.
- 04
Parallel run
Run the macro and the workflow on the same inputs for two or three cycles and compare every output.
- 05
Cut over
Retire the macro, save the workbook as a read-only archive and schedule the workflow.
- 06
Monitor
Alert a named owner on failure and review the first month-end closely.
Risks and how we avoid them
| Risk | How we avoid it |
|---|---|
| Hidden edge cases in VBA nobody remembers. | Run the parallel comparison across at least one month-end or busy period. |
| Rounding and date handling differ from Excel. | Check totals to the penny and agree rounding rules with finance. |
| Users still want Excel output. | Have the workflow produce the same workbook layout they used before. |
What we do and what it costs
The $500 audit documents the macros and gives a fixed price, credited to the build. Most macro rebuilds are workflow builds from $1.5k. Care plans from $50 a month keep them running.
Questions
n8n or Power Automate?
Power Automate suits teams deep in Microsoft 365 with licences in place. n8n suits mixed stacks or heavier logic. We recommend one after seeing the macros.
Can people still work in Excel?
Yes. The workflow can read from and write to Excel files in OneDrive or SharePoint so the familiar output stays.
What if nobody understands the VBA?
We read it and write down what it does before rebuilding. That document is part of the handover.
Related: Microsoft 365, n8n, Power Automate, Glossary: human in the loop, Modernise service, Automation audit, comparisons. All migrations.
We will tell you whether the move pays before you start
The audit lists what you run today, ranks it by cost and risk, and ends in one fixed price for the migration, credited to the build.
Book a discovery call
