Keep Your Macros Running After Every Office Update.
Plenty of organizations still run invoicing, imports or month-end reports on a macro someone wrote years ago. It works until an Office update, a security change or a file move breaks it, usually on the day it is needed most. Ceifa supports those macros as part of your managed IT: we fix them when they fail, back them up, document what they do, make small changes on request, and warn you before a fragile one gives out.
Why Macros Stop Working, Usually on a Busy Day
Most VBA failures are not caused by the code changing. They are caused by everything around it changing: an Office update, a stricter macro security setting, a move from 32-bit to 64-bit Office, files migrated to SharePoint or OneDrive so old paths no longer exist, or the account a macro relied on being disabled when someone left. Microsoft now blocks macros in files that arrive from email or the internet by default, which catches out plenty of older tools.
That is why macro support belongs with the people who manage the rest of your IT. We see the updates, the security policies, the file moves and the staff changes, so when a macro breaks we already know what changed around it. Our job is to get it running again, fix the cause, and write down what we found.
Our First Four Checks
When a macro fails, we start with four questions. Did Office or Windows update recently? Has the file, or a file it reads, moved? Is it opening from a location Office trusts? Has an account or password it depends on changed? One of those is often the answer, and checking them first gets your team working again sooner.
What Managed Macro Support Changes
A macro your business depends on deserves the same care as any other system. Here is the difference between a macro nobody owns and one that sits inside your managed IT.
Fixed After the Update
Before
The macro button does nothing on Monday morning because Office updated over the weekend.
After
A helpdesk ticket, a diagnosed cause and a fix, with the cause written down for next time.
Trusted Properly, Not Clicked Through
Before
Staff told to click Enable Content on any file that asks, because that is the only way the macro runs.
After
Macros run from trusted locations or as signed code, inside the same security baseline we apply to every client.
Backed Up, Code Included
Before
The only working copy of the .xlsm lives on one desktop, and nobody is sure which version is current.
After
The file kept in a managed, backed-up location with version history, so a bad edit can be rolled back.
Explained in Plain Language
Before
Nobody can say what the macro touches, which files it reads, or what happens if it stops halfway.
After
A short runbook covering what it does, what triggers it, what it depends on and the first steps when it breaks.
Small Changes on Request
Before
A new folder path or an extra field waits for months because nobody wants to open the VBA editor.
After
The change requested through the helpdesk, tested on a copy, then put back into use.
Flagged Before It Fails
Before
A macro relying on an old add-in, a 32-bit control or a former employee’s file path, working until the day it does not.
After
The risk raised with you early. If a rebuild is needed, it is delivered with Regroove, our sister consultancy.
Your Contact for This Service
Clod Feijao, Partner and Director of Client Success
Macro support at Ceifa has a named person accountable for it, not just a queue. Clod looks after client relationships, which includes making sure the macros and spreadsheets your teams depend on are supported, documented and reviewed alongside the rest of your IT.
He does not write the VBA himself. His job is to make sure a failing macro gets fixed properly, that repeat problems are raised with you instead of patched quietly, and that when a tool needs rebuilding, the work is scoped with Regroove, our sister consultancy, and comes back under our support once it is done.
Read Clod’s profileThe Support Log
Every macro we take on moves through the same stages, from the day we find it to the day-to-day support that follows.
Find the Macros You Rely On
We ask each team which macro-enabled files they could not work without, and list them with an owner, a location and what each one is used for.
Check How They Run Today
We look at the Office version and bitness, macro security settings, file locations, references and add-ins, so we know what could break the next time something changes.
Back Up and Secure
Critical files go to a managed, backed-up location with version history. Macros run from trusted locations or as signed code, and editing rights are limited to the people who need them.
Write the Runbook
We document what each macro does, what it depends on and what to try first when it fails, in plain language your staff can follow.
Support, Fix and Adjust
Failures and small change requests go through the helpdesk. We test changes on a copy, then update the runbook so the record stays current.
Review and Plan Ahead
In our regular reviews we flag macros that are getting harder to keep alive. When one needs rebuilding or replacing, we scope it with Regroove and keep supporting the result.
Related support
Macro support is one part of how Ceifa looks after the data your business runs on. When the risk sits in the workbook rather than the code, see Excel spreadsheet support for backups, permissions and documentation. When a macro reads from or writes to a database, see SQL database support and maintenance. For reporting built on that data, see our Power BI dashboards page.
Common Questions
Have a Macro Everyone Is Afraid to Touch?
Tell us which macros your teams depend on. We will show you how Ceifa would back them up, secure them and support them as part of your managed IT, and tell you plainly which ones are close to failing.
Burnaby Head Office: 3999 Henning Dr #402, Burnaby, BC V5C 6P7 | Victoria Office: 300-848 Courtney Street, Victoria, BC V8W 1C4