If you run an HVAC or plumbing company in Boise or the Treasure Valley, "we have backups" usually means one of two things.
Either somebody assumes Microsoft 365 is handling everything, or somebody bought a backup product years ago and nobody has checked what it is actually protecting since.
That is not a backup plan. That is a guess.
For trades companies, backup problems usually stay invisible right up until the day they cost real money. A laptop dies. A dispatcher deletes the wrong folder. A ransomware event hits a workstation that had the only copy of a price sheet. Then the owner finds out the business was only partially recoverable the whole time.
The issue is usually not that the company ignored backups completely.
The issue is that nobody defined what actually matters first.
Key Takeaways
- Most trades companies are backing up some data, but not all of the systems that keep scheduling, billing, and communication moving.
- Microsoft 365 helps, but it does not replace a full data backup and recovery plan .
- The most important backup checklist for HVAC and plumbing shops usually includes dispatch data, shared files, accounting exports, job photos, email, and admin access records.
- If your phones, dispatch process, and office systems are all connected, weak backups turn into an operations problem fast.
- A clean backup plan supports managed IT , cybersecurity , and smoother day-to-day work for field and office teams.
The Wrong Question Most Owners Ask
Most owners ask, "Are we backed up?" The better question is, "If we lost access today, what would we need back first to keep the company running?"
That changes the conversation immediately.
A trades company recovers in layers. Dispatch needs the schedule. Office staff need customer history. Billing needs invoices. Techs need job notes and photos. If nobody has thought through that order ahead of time, the restore process gets slower than it needs to be.
What Usually Needs Protection First
For a Boise HVAC or plumbing shop, these are usually the first things I would verify.
1. Shared company files
This includes estimates, job checklists, install documents, SOPs, vendor forms, warranty paperwork, HR files, and internal templates.
If those documents live partly in SharePoint, partly in OneDrive, and partly on random desktops, your restore path is already messy.
Company files should live in company-controlled locations. Permissions should follow job role. And the business should know which shared locations are critical enough to restore first.
That overlaps directly with Microsoft 365 support in Boise . A lot of backup problems start as file-structure problems.
2. Dispatch and scheduling records
If your company runs on dispatch software, the schedule is revenue.
Even when a cloud platform is the system of record, you still need to think about what supporting data lives outside that platform:
- exported reports
- customer attachments
- route sheets
- price books
- technician notes
- local spreadsheets the office still depends on
When I talk about IT support for HVAC and plumbing companies , this is what I mean. The business stack is not just the app with the login screen. It is the pile of connected files and side processes around it.
3. Accounting and billing data
Your bookkeeping platform may be cloud-based, but the business still often keeps exports, invoices, payroll support files, and reconciliations in shared folders or local systems.
If accounting data is scattered across one owner's laptop and a bookkeeper's desktop folder, that is a weak point.
4. Job photos and field documentation
This is the one a lot of trades companies miss.
Teams collect photos constantly:
- before-and-after job photos
- equipment serial numbers
- install documentation
- damage records
- permit or inspection support
Sometimes those photos sit inside personal phones, text threads, or one employee's cloud account. That is not company backup. That is accidental storage.
If field documentation matters for billing, warranty disputes, or callbacks, it needs a defined home and backup path.
5. Email and shared mailbox access
Dispatch inboxes, billing inboxes, service requests, vendor communication, and customer follow-up often live inside shared mailboxes.
If those mailboxes are messy, orphaned, or accessible from too many unmanaged phones, recovery gets harder and security gets weaker at the same time.
This is one reason I keep pushing owners to treat M365 like business infrastructure instead of just email. I covered the setup side already in Microsoft 365 Setup for Boise Home Services Companies .
6. Admin access and restore credentials
This is the part nobody remembers until something breaks.
Who has admin access to Microsoft 365? Who can sign into the firewall? Who has the backup console login? Where are the recovery codes? Who can work with the ISP, domain registrar, or key SaaS vendors?
If all of that knowledge lives in one person's head, you do not have a resilient business. You have a dependency.
The Microsoft 365 Backup Misunderstanding
I see this constantly: a business moves into Microsoft 365 and assumes the backup problem is handled.
Microsoft 365 is an important part of the environment. It is not a complete backup strategy by itself.
You still need clarity around:
- what data lives in Exchange, OneDrive, and SharePoint
- how deleted or overwritten content is recovered
- how long important data needs to remain available
- what happens when an account is removed incorrectly
- whether the company can restore cleanly after a bad sync, deletion, or account compromise
That is where cybersecurity and backup planning start to overlap. If an account gets compromised or files get encrypted from a synced device, you do not want your first backup conversation happening in the middle of the incident.
What a Practical Restore Plan Looks Like
A restore plan for a trades company does not need to be fancy.
It does need to answer a few blunt questions:
- What systems have to come back first for the office to function?
- What files can wait a few hours or a day?
- Who owns the restore process?
- Who communicates with staff while recovery is happening?
- Which vendors or platforms need to be contacted immediately?
For many small shops, the first restore priorities are:
- email and shared communication
- dispatch and scheduling visibility
- shared operational files
- accounting and billing support data
- lower-priority archives
That order will vary, but the point is to have an order at all.
The Risk of "We Will Figure It Out If It Happens"
That mindset is expensive.
When a company is already under pressure, people make bad restore decisions fast. They restore the wrong machine first. They forget where critical files lived. They assume a SaaS platform has data it does not actually have.
That is exactly how a one-hour problem turns into a two-day mess.
If you are also spending money on lead generation or running an AI Front Desk for trades , weak recovery planning gets even more obvious. More leads do not help much if the business cannot access the systems that route, answer, bill, and document the work.
A Simple Checklist to Review This Week
If you want a fast gut-check, start here:
- List the systems and shared folders the office would need today if a main workstation died.
- Confirm where job photos and field documentation actually live.
- Verify which shared mailboxes matter most and who owns them.
- Check whether backup and admin credentials are documented in a company-controlled place.
- Make sure former employees do not still own important files or access paths.
- Pick the first three systems you would restore if the office had a bad Monday morning.
If those answers are fuzzy, the business is probably more exposed than it looks.
When to Get Outside Help
You probably do not need a giant disaster-recovery project.
You probably do need help if:
- nobody is sure what is backed up
- the backup tool has not been reviewed in a long time
- critical data lives in personal accounts or unmanaged devices
- Microsoft 365 storage is disorganized
- restore ownership is unclear
- the company has grown faster than its processes
That is usually the point where a direct review is cheaper than continuing to trust assumptions.
If you want me to look at your setup and tell you what actually needs protection first, contact Idaho Proper IT . I can review the backup path, the M365 side, and the operational weak points so your HVAC or plumbing company is not trying to solve recovery in the middle of a bad day.