Copyright © 2026 Everyday Backups · everydaybackups.com · Secure cloud backup for small business & personal files
A field-service business runs on years of accumulated data: every customer's equipment history, every recurring maintenance agreement, every dispatch record, every technician note and photo, and every invoice going back to the beginning. Most of that data lives on one or two Windows computers in your office. The backup question every contractor needs to answer honestly is whether they could pull up the service history for a specific customer's unit, a signed maintenance contract, or a parts order record on the day a machine fails, a technician's laptop gets stolen, or ransomware locks everything down.
Everyday Backups provides managed, encrypted cloud backup for Windows computers, with monitoring, restore support, and regular backup health reporting. Paid plans from $5.99/mo.
An HVAC, plumbing, or electrical business builds its operation on years of accumulated customer and equipment records. Unlike a paper-based shop of twenty years ago, that institutional knowledge now exists almost entirely as digital files on the office Windows machine, a dispatcher's workstation, or a shared network folder. The list below covers what a working field-service business should be able to recover, from a specific date, when a hardware failure or a security incident demands it.
A gap in any one of these categories can become serious in a specific scenario. If a longtime customer calls about a unit that was serviced three years ago and the service history cannot be located, the technician arrives without context. If a maintenance agreement customer disputes coverage and the signed contract file has been lost, the business is negotiating without documentation. If QuickBooks data from the previous tax year is gone after a hard drive failure, that history cannot be reconstructed.
The situations below are the practical moments when a backup matters or a backup gap becomes a crisis. Each one has a different trigger, but they share a common outcome when no independent off-site backup exists.
A failed hard drive on the main dispatch workstation means no access to the current schedule, no customer service history for the day's jobs, and no way to pull up maintenance agreement terms for calls that come in. If the machine also held the only copy of the QuickBooks file, the accounting gap compounds the operational one. A backup means you recover the data; without one, you rebuild from scratch.
CISA and the FTC both identify small service businesses as ransomware targets. When ransomware runs, it typically encrypts all accessible files on the local machine and any network shares mounted at the time. A cloud sync folder replicates the encrypted versions within seconds. A backup that is not continuously connected to your network is the copy that survives with usable data intact. Without it, recovery means paying a ransom with no certainty of results, or rebuilding years of customer and equipment records from nothing.
A technician's laptop may hold field photos, downloaded work orders, local copies of customer records, and cached data from dispatch software. If none of that data syncs back to the office and the laptop is not backed up independently, it is gone when the device is gone. Laptop theft is one of the more common data loss events for field-service businesses because the devices travel to job sites, vehicles, and customer locations daily.
A well-intentioned file cleanup, a wrong-folder deletion, or an application update that corrupts a local database does not require a dramatic hardware event to cause real data loss. Cloud sync propagates the deletion or overwrites the corrupted file immediately. A backup with version history lets you recover the file as it existed before the deletion or corruption, from a point in time before the problem occurred. Sync alone offers no such recovery path.
When someone who has managed the office for years departs, they often take institutional knowledge about where data is stored and how it is organized. Files saved to personal desktop folders, local copies of customer correspondence maintained outside the main system, and spreadsheets used to track specific accounts may never transfer to the incoming person. A backup that captures everything on the machine, regardless of folder structure, preserves what is there even if the departing employee's personal organization approach is not obvious to anyone else.
A customer disputes a diagnosis from a service call eight months ago. The technician's notes from that date, the equipment readings captured at the time, and the work order showing what was recommended are the only documentation. If those records exist only in the dispatch software database and no backup was running during that period, the documentation needed for the conversation does not exist in a retrievable form.
The 3-2-1 rule is a straightforward framework promoted by CISA and used widely in small-business backup guidance. For an HVAC, plumbing, or electrical contractor, here is what it looks like applied to the files that actually matter in this business.
Your working copy on the office PC or server counts as one. A second copy might be a local external drive or a secondary workstation. A third copy, off-site in encrypted cloud storage, is the copy that protects against a local disaster affecting both of the first two copies at once. All three copies have to exist before the failure event for the rule to help.
Keeping backups only on the same type of storage, such as two drives in the same machine or on the same local network, does not provide meaningful redundancy against hardware failure or a building event. CISA guidance calls for at least two different storage types, for example a local drive and a separate cloud destination, as distinct and independent layers of protection.
Off-site means physically separated from your office or shop. Cloud backup satisfies this requirement when the data is sent to a separate data center rather than just an external drive in the same room. The off-site copy is the one that matters most when everything at the office location is affected at once, whether that is a fire, flood, theft, or a ransomware attack that hits every connected device on the network.
CISA specifically recommends maintaining at least one backup copy that is not continuously connected to the network. Ransomware increasingly targets connected backup systems as part of the same encryption sweep that hits production files. A cloud backup that is not directly mounted on your local network provides a layer that ransomware cannot reach and encrypt alongside your primary data, which is the version most likely to survive a ransomware event with usable files intact.
The checklist below reflects CISA small-business backup principles and FTC small-business cybersecurity guidance, applied to the file environment of a working field-service contractor. This is a starting framework for backup decisions, not legal, regulatory, or compliance advice.
For a broader self-assessment of your current backup posture, see the small-business backup checklist. For ransomware-specific preparation, see ransomware restore readiness.
Two software categories generate the bulk of a field-service contractor's critical data: the field-service or dispatch platform and the accounting system. Understanding what your backup does and does not cover for each is essential before you assume you are protected.
Field-service and dispatch platforms used by HVAC, plumbing, and electrical contractors store their data in different ways depending on the software. Some install a local database on a Windows server or workstation in the office. Others operate as web-based platforms where the primary database lives on the vendor's servers rather than your machines. The key questions to answer for your backup configuration are: where does the software store its data files on your Windows machine, are those files included in your backup scope, and are they captured in a consistent state when the application is not actively writing to them.
If your dispatch software is cloud-based with data primarily on the vendor's servers, the local backup question shifts to what you save locally from that system: exported work order PDFs, customer reports downloaded to the office PC, field photos that sync to a local or network folder, and any other files written to Windows machines in your office. Those locally stored files remain your responsibility to back up independently. The vendor's copy of your data in their cloud is not a substitute for your own backup of what lives on your machines, and vendor data retention policies can change.
Some dispatch platforms allow you to configure automatic export paths or scheduled data exports that write to a specific local folder. If your software has this capability, setting up an export to a known folder path and including that folder in your backup scope is a practical way to ensure service history and customer records are covered alongside your other files.
Many HVAC, plumbing, and electrical contractors use QuickBooks for revenue tracking, job cost accounting, payroll, and tax preparation. QuickBooks company files (.QBW) can grow to several gigabytes, are frequently stored on a single office desktop or network share, and are the source of truth for the business's complete financial history. Intuit's own documentation recommends maintaining backup copies of QuickBooks data files in a separate location from the original, and specifically notes that backing up only to the same machine is not adequate protection against hardware failure.
Common QuickBooks backup oversights at small contracting businesses include the company file stored on one machine with no second copy, the Intuit automatic backup feature saving to a different folder on the same drive as the original, and portable company files (.QBM) treated as complete backups when they are actually compressed snapshots that may not include all supporting files. A complete backup of QuickBooks for a contractor covers the company file itself, the backup copy that QuickBooks may write to its own backup folder, and any exported reports or payroll files the business saves separately.
For a detailed look at QuickBooks backup practices, see QuickBooks backup for small businesses. Intuit's documentation, referenced there, is the authoritative source for QuickBooks-specific backup configuration steps.
Many contractors have OneDrive, Dropbox, or a similar sync service running on their office machines and assume that sync protects their business data. The distinction between sync and backup matters significantly in the situations where you actually need to recover something.
Cloud sync mirrors the current state of your files on the device to a cloud destination. When a file changes on your machine, the change replicates to the cloud, usually within seconds or minutes. When a file is deleted, the deletion replicates. When ransomware encrypts a folder of customer records, the encrypted versions overwrite the cloud copies before you have a chance to notice the attack. At that point, both the local copy and the cloud sync copy are encrypted, and the sync service has preserved nothing useful.
Backup retains point-in-time copies with version history. You can restore files as they existed at a specific date and time in the past, before the deletion, before the corruption, or before the ransomware ran. That version history is what makes backup genuinely useful in a recovery event, as opposed to sync, which can only give you the current state of the file, whatever that current state happens to be.
Microsoft's own OneDrive documentation describes Personal Vault and version history features, but these are not a substitute for an independent backup with a defined retention window and monitoring. The version history available through OneDrive is limited by duration and plan, and the restoration interface is not designed for recovering a business's complete data set after a significant incident. See cloud sync vs. backup for a full comparison of what each service actually does and does not protect.
The FTC and CISA both publish guidance specifically noting that small businesses, including field-service and trade contractors, are targets of ransomware campaigns. The reason is practical: small businesses often have less IT infrastructure than large organizations, making them easier to compromise, while still holding customer data and financial records that create pressure to pay a ransom rather than lose years of business history.
For an HVAC, plumbing, or electrical contractor, the factors that make ransomware particularly consequential include all service history and customer equipment records concentrated on a small number of Windows machines, QuickBooks accounting covering years of job cost and revenue data stored locally, maintenance agreement files and contracts with no off-site copy, and typically no dedicated IT staff checking backup health daily.
CISA's #StopRansomware guidance identifies offline and encrypted backup copies as the primary technical recovery mechanism when ransomware has encrypted production files. The critical point is that a backup connected to the same network as the infected machines, or a sync folder that replicates changes in real time, may itself be encrypted before the attack is detected. A backup that is not continuously mounted on your local network is the copy most likely to survive with usable data intact.
For a complete breakdown of what a ransomware-capable backup posture looks like for a small office or field-service environment, see ransomware restore readiness. The guidance there walks through why offline and air-gapped copies matter, what restore testing looks like in practice, and what questions to ask about your current backup setup before an incident occurs.
Ransomware recovery is not only a technology question. Even with a solid backup in place, a ransomware incident typically means some period of downtime while systems are cleaned and data is restored. A backup does not eliminate downtime, but it is the difference between recovering from a bad week and potentially losing years of customer records, equipment histories, and financial data with no path back. A backup you have tested and confirmed works is worth substantially more than one you have never restored from.
Yes, for two distinct reasons. First, even with a cloud-based dispatch platform, your business almost certainly saves files locally to Windows machines: work order PDFs you export, field photos that land in a local or network folder, maintenance agreement contracts stored in an office folder, QuickBooks accounting files, and customer correspondence. Those locally stored files are not backed up by the dispatch software vendor. Second, the vendor storing your data in their cloud is not the same as you having an independent backup of that data that you control and can restore from on your own timeline. Vendor data retention policies, subscription terms, and access rules can all change. Your own backup is a separate protection layer.
The most common discovery moments are a hard drive failure on the office dispatch PC, a ransomware incident that encrypts multiple machines at once, and a customer dispute where the technician notes or signed work order from a past date cannot be found. Each of those events surfaces gaps that were invisible while the business was running normally. The gap is real whether it is discovered or not; discovering it in a calm moment with time to fix it is much better than discovering it mid-crisis when the data is already gone.
It depends on how your specific software stores that content, and this is worth verifying precisely rather than assuming. In many configurations, field photos are stored in a local or network folder path that is separate from the dispatch software's primary database. Technician notes entered into the software may be in the database, but photos captured on tablets may not sync to any shared location. For businesses that rely on before-and-after documentation for billing and dispute resolution, confirming exactly where each type of file ends up, and then ensuring backup covers each destination, is a practical first step.
No, and the difference matters significantly for ransomware protection and accidental deletion. Cloud sync mirrors the current state of your files. If a file is deleted, overwritten, or encrypted by ransomware, that change replicates to the sync destination, often within seconds. Backup retains point-in-time copies with version history so you can restore files as they existed before the damage. Microsoft's OneDrive documentation describes version history features, but those are limited by duration and plan, and are not designed as a replacement for a managed backup with a defined retention window and monitoring. See cloud sync vs. backup for a complete comparison.
CISA guidance recommends maintaining enough backup history to recover from incidents that are not discovered immediately. Ransomware and file corruption are often not noticed for days or even weeks after the event that caused them. A backup window of 24 to 48 hours is almost never sufficient for a working business. Thirty days of version history is a practical minimum. Some field-service businesses choose to retain longer histories for completed job records, signed maintenance agreements, and customer equipment records that might be referenced in a dispute months or years after the original service date.
A backup job failure should get immediate attention, not be deferred to a weekly review. The first step is understanding why it failed: the machine was off during the scheduled backup window, a file was locked by a running application, available disk space ran out, or a network or credential issue prevented the upload. Each of those has a different resolution path. If backup failures go unnoticed for an extended period, the business is operating without coverage, and a failure or ransomware event during that window has no recovery path. Backup monitoring that sends an alert on failure is the baseline way to avoid discovering a months-long gap only at the moment you need to restore.
Institutional backup knowledge leaving with one person is one of the more common ways a backup that was once configured and working gradually becomes unreliable. The backup may continue running, but no one in the business knows what it covers, where the data goes, or how to start a restore. The practical mitigation is to write down the answers to three questions while that person is still available: what is backed up (which machines, which folders), where does the backup data go (which service, which account), and how do you initiate a restore. Those three answers, stored somewhere accessible to the owner or another manager, preserve the value of the backup investment through personnel changes.
CISA recommends periodic restore testing as a distinct activity from verifying that backup jobs completed. A completed backup job confirms that data was transferred, not that the files are intact and recoverable in the format you need. For a field-service contractor, a quarterly spot-restore is a practical cadence: select a sample of files from different categories (a customer service history export, a maintenance agreement PDF, a QuickBooks backup file) from different backup dates, and confirm you can retrieve and open each one. This surfaces scope gaps, file-locking issues, and process gaps months before you need the backup in an actual recovery event.
Everyday Backups installs on Windows machines, monitors backup job health, sends alerts when a backup fails or goes overdue, maintains version history so you can recover files from a prior point in time, encrypts data in transit and at rest, and stores backups in off-site cloud infrastructure rather than local media that could be affected by the same event as your primary machines. The service is designed to be configured once and then run automatically in the background, with monitoring and health reporting so you know the backup is working without checking it manually each day. For contracting businesses with more than one Windows machine, such as a dispatch PC and an owner's office computer, each machine requires its own backup coverage.
If technicians use their phones to capture field photos or access customer records, and if those photos or records are saved only to the device without syncing to a shared office location, then the device holds unique data that is lost if the phone is damaged or stolen. Everyday Backups covers iPhone, iPad, and Android devices in addition to Windows, so device-level backup is available for the mobile devices your team uses in the field. The starting point is tracing exactly what data lives on each device and whether that data exists anywhere else.
Whether you want to check your current situation on your own first or talk it through with someone who can give you a second set of eyes, there is a starting point that fits.
The backup risk check at everydaybackups.com/a/backup-risk-check.html asks a short set of questions about your current setup and tells you where the gaps are. No signup required. It takes about two minutes and gives you a clear picture of where you stand right now.
If you would rather talk through your specific setup, our team offers a free 15-minute Backup Risk Check. We look at what you have, identify the gaps, and give you honest guidance on what to fix first, whether or not you use Everyday Backups to do it. Schedule at everydaybackups.com/schedule or call us at 850-980-3691.
Everyday Backups is a backup service, not legal, regulatory, or compliance advice. It does not by itself satisfy any record-retention, privacy, consumer protection, or other legal requirement applicable to your business. No compatibility with any specific field-service management platform, dispatch software, accounting platform, or other application is guaranteed or implied; verify backup scope and file coverage with your own IT review. Mention of software categories such as field-service management software, dispatch software, or accounting software is for illustrative purposes only and does not constitute endorsement of or claimed compatibility with any specific vendor or product. References to CISA, FTC, Intuit, and Microsoft documentation are for informational context only and do not constitute endorsement by those organizations. Consult qualified legal and IT advisors for requirements specific to your business.
Everyday Backups runs on Windows, iPhone, iPad, and Android. Set it once; it backs up automatically, encrypted, off-site. Paid plans from $5.99/mo.
Prefer to talk to a person? Call 850-980-3691
Want a second set of eyes? Schedule your free 15-minute Backup Risk Check with our team
Copyright © 2026 Everyday Backups · everydaybackups.com · Secure cloud backup for small business & personal files