A manufactured or modular home sold this year will still be sitting on its lot in thirty years, and every lender, insurer, appraiser and future buyer who ever touches that home commonly asks for its paperwork: the purchase agreement, the label and serial numbers, the data plate where the home has one, the order build sheet, the delivery and installation records. Most of that file exists as one folder on one Windows computer in the sales office. The backup question every dealer needs to answer honestly is whether a single home's complete record could be pulled up on the day a lender, an appraiser, or a homeowner asks for it, even years after the sale closed.
Everyday Backups provides managed, encrypted cloud backup for Windows computers, with monitoring, restore support, and monthly backup health reporting. Paid plans from $5.99/mo.
A manufactured or modular home dealership's most important data is not one company-wide database. It is dozens or hundreds of individual home files, each one a paper and photo trail that starts the day a unit is ordered and, in practice, never really ends. A homeowner, a lender, or an appraiser can come back asking for a specific document ten or twenty years after the sale. The categories below are what a working dealer should be able to recover, for a single home, from a specific date.
A gap in any one of these categories can turn into a real problem years after the sale: a lender refinancing the home needs the label and serial numbers and cannot find them, an insurer wants the data plate photo and the file is gone, or an appraiser needs the order build sheet to confirm what was originally installed and the dealer who sold the home has no record left to hand over.
CISA promotes the 3-2-1 rule as a simple standard for small-business backup, and it maps cleanly onto a home dealer's two very different kinds of files: this month's active deals, and the growing archive of every home sold before it.
Your working copy is whatever sits on the sales-office PC or your deal software's server today: this month's live deals plus the accumulated archive of homes sold in prior years. A second copy on a local external drive or a second workstation protects against one machine failing. A third copy, off-site in encrypted cloud storage, is what protects the archive, which cannot be recreated by re-scanning anything, from a single event at the dealership taking out both of the first two copies at once.
A home dealer's archive tends to grow every year and rarely gets deleted, so relying on two drives of the same type inside the same PC just means both copies age and can fail together. CISA guidance calls for two genuinely different storage types, for example a local drive for quick access to recent deals and a separate cloud destination for the accumulating archive, so one kind of hardware failure cannot take out both.
Off-site matters more for a home dealer's archive than for almost any other file category on the lot, because a data plate photo or a decade-old purchase agreement cannot be reshot or re-signed if the local copy is destroyed. Cloud backup satisfies the off-site requirement when the data goes to a separate data center rather than an external drive in the same room, and it is the copy that survives a fire, flood, or theft affecting the whole building where the working files and the archive were stored together.
CISA recommends keeping at least one backup copy that is not continuously connected to the network. For a home dealer this matters most for the archive, since years of closed-deal folders sitting on a mapped network drive are exposed to the same ransomware sweep as this week's active files. A cloud-based backup that is not directly mounted on your local network is far less likely to be reached and encrypted alongside a home's original paperwork.
The three items below are specific to how a home dealer's data is actually organized. They are the starting point before anything else in this framework matters, not a complete compliance checklist.
For a broader self-assessment of your current backup posture, see the small-business backup checklist. If your dealership sells titled vehicles alongside manufactured homes, the file environment is distinct: see backup for independent and used car dealerships for the vehicle deal-jacket side. Parties on the land side of a home sale, financing or closing the transaction rather than selling the structure, have their own file environment: see backup for mortgage brokers and backup for title and escrow companies.
Most backup advice is written for files that change constantly: today's deal, this week's inventory count. A home dealer has a second, quieter problem. The purchase agreement you file this month may not be opened again until a refinance, an insurance claim, or a resale pulls it back out ten or twenty years from now, and by then the person asking usually has nothing to go on but a serial or label number written on a piece of paper in their hand. Being able to hand that file over on the spot is a different exercise than backing up this week's sales, and it deserves its own plan.
Two systems generate most of a home dealer's data: whatever runs deals, orders, and inventory on the sales floor, and QuickBooks or a similar accounting platform. Knowing exactly what each one's backup covers, and where the gap is, matters more here than at most small businesses because the record it protects may need to outlive the software itself.
Ask three questions about whatever system runs your sales floor: where on disk does it actually keep its data, is that path included in your backup configuration, and does it get captured cleanly rather than mid-write. A locally installed system usually keeps a database file or folder somewhere on a Windows machine or an on-site server. A cloud-hosted system keeps the working data on the vendor's side, which shifts the question to whatever you export and save locally, such as purchase agreement PDFs, build sheets, and data plate photos.
Either way, the vendor holding your data is not the same as you holding a restorable copy of it. If your deal software can write scheduled exports to a folder you choose, pointing that export at a known path and adding that path to your backup scope is a practical way to close the gap between what the software stores and what you can actually get back.
A home dealer's QuickBooks company file (.QBW) tends to carry floor plan financing, payroll, and years of revenue history in a single file that grows steadily and rarely gets deleted. Intuit's documentation recommends a backup copy stored in a separate location from the original, and specifically warns that backing up to the same machine is not adequate protection on its own.
Two mistakes show up often at small dealerships: the built-in Intuit backup feature writing to a different folder on the same drive as the original, which does not protect against a drive failure, and a portable company file (.QBM) mistaken for a full backup when it is actually a compressed snapshot that can leave out supporting files. For a closer look at QuickBooks-specific backup steps, see QuickBooks backup for small businesses.
CISA and the FTC both flag small businesses as ransomware targets precisely because they tend to have thinner IT defenses than larger companies while still holding records worth extorting over. A home dealer fits that pattern with one added twist: the records at risk are not only this quarter's deals but a growing archive nobody can afford to lose.
For a home dealer specifically, the sharpest risk is not this week's deals; it is the archive. A ransomware event that reaches a network share holding years of closed-deal folders can encrypt every home's purchase agreement, data plate photo, and installation record in one pass, the same way it would encrypt today's paperwork. Unlike a live deal, which can sometimes be reconstructed from a lender's copy or a buyer's memory, a closed home's original file, once encrypted or lost, usually has no second source anywhere outside the dealership. That is what separates a home dealer's ransomware exposure from a business whose records mostly matter for the current fiscal year.
CISA's #StopRansomware guidance points to offline and encrypted backup copies as the main technical way to recover once ransomware has already encrypted production files. The reason offline matters is straightforward: a backup drive that stays mapped to the network, or a sync folder that mirrors changes as they happen, can be swept up in the same attack as everything else. A cloud backup that is not sitting on your local network as a mounted drive is much less likely to be touched by whatever just encrypted the sales-office PC.
For a fuller walkthrough of offline and air-gapped backup copies, and how to build a restore-tested posture for a small office, see ransomware restore readiness.
Backup is a recovery control, not a security control, and it is worth saying plainly: encrypting and backing up a credit application protects your ability to get that file back if it is lost, corrupted, or ransomed, but it does not make the record secure, it does not make it private, and it does not stop anyone from misusing what is inside it. A tested backup shortens a bad week; it does not replace a dealership's separate security and privacy practices, and it is not offered here as a substitute for them.
Yes. Even with a fully cloud-hosted deal or inventory system, your dealership still saves things locally: exported purchase agreement PDFs, data plate photos moved off a phone or camera, scanned installation certifications, QuickBooks files, credit applications. None of that is backed up by your deal software vendor. And separately, the vendor storing your data in their cloud is not the same as you holding an independent copy you can restore on your own schedule if something goes wrong on their end or yours.
Almost always separate, and it is worth confirming rather than assuming. Data plate and label photos are typically saved to a folder on the sales-office PC that has no connection to the deal software's own database. Unless that specific folder has been added to your backup configuration, those images are not covered even if everything inside the deal software is. Given that a data plate photograph documents a marker on a home that may already be sited and skirted, it is not a file you can go back and reshoot.
No. Sync keeps a folder looking the same across devices, which means a deletion, an overwrite, or a ransomware encryption event on one device shows up on the synced copy just as fast. Backup keeps point-in-time versions, so you can reach back to a copy from before the damage happened. For an archive where a single lost home file has no second source anywhere, that version history is not optional. See cloud sync vs. backup for the full comparison.
Two different clocks are running here, and they should not be confused. Day-to-day version history exists to catch problems that are not noticed right away, since ransomware and accidental deletions often surface days or weeks after the fact; 30 days of version history is a reasonable minimum for that purpose. Separately, most dealers choose to keep complete per-home files, the purchase agreement, the label and serial numbers, the data plate photo, for as long as the home could plausibly still be standing, which in practice means indefinitely. How long any particular record needs to be retained is a business decision, and in some cases a legal one, for your own advisors; this page addresses only whether the records you decide to keep can actually be recovered.
Treat it as something to look at today, not at the next weekly check-in. Common causes each point to a different fix: the machine was powered off during the scheduled window, a file was locked by an open application, the drive ran out of space, or a network or login issue blocked the upload. A failure that sits unresolved for weeks means the dealership has no real coverage during that stretch, and if a hard drive dies or ransomware hits in that window, there is nothing to restore from. Alerting on failure, rather than discovering it later, is the baseline fix.
This is one of the more common ways a working backup quietly stops being useful. The job itself may keep running, but if the one person who set it up leaves without writing anything down, nobody else knows what folders are covered, where the data goes, or how to start a restore. Before that person leaves, get three answers written down somewhere other than the machine being backed up: what is covered, where it goes, and how to restore from it. That short document is what keeps the backup investment intact through staff turnover.
Completing without an error only proves data moved somewhere; it does not prove the files came back whole or in a format you can actually use. A practical cadence for a home dealer is quarterly: pick one recent purchase agreement, one data plate photo, and one QuickBooks backup, restore each from a different date, and confirm they open correctly. Combined with the twenty-years-later retrieval test described above, this catches both the technical gaps and the findability gaps with months of lead time before a real request comes in.
No. Everyday Backups is a backup and recovery service. It makes no claim about, and does not address, HUD certification and construction and safety standards, state manufactured housing commission or board licensing, installer certification, SAFE Act or loan originator rules, Truth in Lending or retail installment disclosure obligations, or any dealer record retention requirement. Those are legal and regulatory questions for your own attorney, compliance advisor, or state agency. This page and this service address only the technical question of whether your files can be recovered if a machine fails, a file is deleted, or ransomware strikes.
No. Installation, anchoring, tie-down methods, and wind zone suitability are engineering and installer questions, not backup questions, and this service gives no advice on any of them. Everyday Backups only helps you keep a recoverable copy of whatever installation and anchoring certification documents you already receive and choose to keep on file.
No. A backup is a recovery control, not a security or privacy control. Backing up a credit application means you can restore your own copy of it if a machine fails or a file is lost or corrupted. It does not make that record secure against unauthorized access, and it does not make it private, and it does nothing to prevent someone from misusing the information inside it. Data security, access controls, and privacy protections for credit application and buyer information are separate concerns that a backup service does not address.
It installs on Windows machines, watches for failed or overdue backup jobs and alerts when one happens, keeps version history so a file can be pulled from an earlier point in time, encrypts data in transit and at rest, and sends the copy to off-site cloud storage rather than local media that could be lost in the same event as the originals. It is meant to be set up once and then run quietly in the background, with monitoring standing in for the daily manual check most dealerships do not have time to do. Each Windows machine on the lot needs its own coverage.
Everyday Backups is a backup service, not legal, regulatory, financing, credit, title, lien, real property, tax, appraisal, insurance, or compliance advice. It does not by itself satisfy any record-retention, privacy, consumer-protection, lending, licensing, or other legal requirement applicable to your business, and it makes no claim about HUD certification and construction and safety standards, state manufactured housing commission or board licensing, installer certification, the SAFE Act or loan originator rules, Truth in Lending, or retail installment disclosure obligations. It provides no installation, anchoring, tie-down, or wind zone guidance. A backup is a data recovery tool; it is not a data security or privacy product, and backing up a record such as a credit application does not make that record secure, private, or compliant with any financial privacy rule. No compatibility with any specific deal, order, inventory, or accounting software is guaranteed or implied; verify backup scope and file coverage with your own IT review. References to CISA, FTC, Microsoft, and Intuit documentation are for informational context only and do not constitute endorsement by those organizations. Consult qualified legal, financial, and industry 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