Ask your office manager a plain question: which jobs are waiting on a permit right now?
Watch what happens next. If the answer starts with opening SharePoint, clicking into a folder called Jobs, then a folder for the year, then a folder per customer, then a spreadsheet somebody named "Permits FINAL", your back office lives in a file share. The answer is in there. It takes a while, and it takes the one person who remembers where they put things.
A lot of trade shops end up here, and for a sensible reason. The company already paid for Microsoft's office subscription. SharePoint came with it. Somebody set up folders one weekend, it beat the shared drive on the old server, and it has held the business together since. That was a good call at the time. The trouble is what it turned into.
A folder holds files. A job has a status.
SharePoint is very good at one thing: keeping documents in one place, with versions and permissions. A signed contract is a document. An employee handbook is a document. A photo of a finished panel is a document.
A job is something else. A job moves. It gets called in, quoted, scheduled, worked, closed, invoiced, paid, and sometimes called back under warranty. At each step, somebody needs to know where it stands and what it is waiting on.
A folder cannot tell you that. It can hold the quote PDF, the permit application and the photos, but it has no idea that the permit came back approved on Tuesday and the job can now go on the board. A person has to open it, read it, and remember to move the job forward. When that person is out, the job sits.
That is the pattern to look for. The files are fine. The status of the work is living in people's heads, and SharePoint is where they go to jog their memory.
Signs the file share has become the back office
The same answer lives in two places. A customer's equipment is listed in their folder, in the field tool and in a spreadsheet of maintenance agreements. They disagree, and nobody is sure which one is right.
Questions get answered by a person, not a screen. Which maintenance agreements renew next month? Which invoices went out without the job photos attached? Which techs are due for a license renewal? If each of those gets answered by someone going digging, the back office is a person with good habits.
New hires learn the folder structure before they learn the work. The first week for a new dispatcher or office manager is spent learning where things are kept and what the naming rules are. That is a sign the system is the folder layout, and the folder layout lives in one person's head.
What to move out, and what to leave
The instinct is to replace SharePoint with something bigger. That is usually the wrong first move, and it is how a shop ends up with a second system nobody uses, which I wrote about in You Bought the Software and the Team Went Back to Excel.
The better split is by what the thing is.
Leave in SharePoint: anything that is a finished document. Signed contracts, handbooks, safety manuals, insurance certificates, closed-out job photos, templates. It is good at this, it is already paid for, and your team knows where to find them.
Move out: anything that has a status and changes. Jobs, quotes, permits, maintenance agreements, warranty callbacks, equipment at a customer's address, license and certification dates. These are records, and records belong in a system that knows what state each one is in and can tell you, without anyone digging, what is waiting and on whom.
Where they move to depends on the shop. Sometimes the field service software you already pay for can hold them, and nobody set it up to. Sometimes it is a small internal app built around the way your office actually runs, with SharePoint still sitting underneath for the files. Either way, the test is the same: can the office manager answer "which jobs are waiting on a permit" from one screen, right away, on a day they did not come in?
Start with one question, not a migration
You do not need to move everything at once, and you should not try. Pick the one question that costs your office the most digging each week. For most HVAC, plumbing and electrical shops it is one of these:
- Which jobs are waiting on something (a permit, a part, a customer signature)?
- Which maintenance agreements are coming up for renewal?
- Which completed jobs have not been invoiced yet?
Take that one question and trace where the answer lives today. Every folder, every spreadsheet, every person who has to be asked. That trace is the requirements document for whatever comes next, and it is more useful than any feature list a vendor will hand you.
Then give that one kind of record one home, and make it the only place that step gets updated for a few weeks. If the digging stops, move the next one. If it does not, you have learned something real about where the work actually happens.
Where AI fits
Once the records that move have one home, the useful AI work gets straightforward. A job that has been waiting on a permit for too long gets flagged to the office. A renewal notice drafts itself from the agreement and waits for someone to read it and send it. The photos a tech uploads get attached to the right invoice. None of that works when the status of the job is spread across folders, because there is nothing for it to read.
That is the order: records first, then the automation on top.
If you want a second set of eyes
This is what the first part of the AI Audit looks like. I sit with your office for a few hours, trace a handful of real jobs from phone call to paid, and mark where the answer to a routine question means opening a folder and asking someone. You get a written map of what to leave in SharePoint, what to move, and where to move it first. If it turns out your setup is fine and the fix is a few habits, I will tell you that.
For more on where AI actually earns its place in a trade shop, see what AI can do for a shop like yours.