Backup For
Oil & Gas Land, Mineral & Royalty Companies

The ownership record a mineral and royalty company cannot afford to lose

A small mineral and royalty acquisition office, a landman shop, or a non-operated working-interest owner keeps most of its working files as scans, spreadsheets, and PDFs on one or two Windows computers. There is no factory floor and no storefront inventory behind this kind of business. The record itself, built tract by tract and owner by owner, is the product. The categories below are what should be recoverable, from a specific date, when a title question comes up, an operator disputes a decimal interest, or the office computer stops working.

• Recorded deed and assignment scans pulled from county courthouse records for each tract and each ownership interest
• Oil and gas lease copies and complete lease files, including amendments, extensions, and ratifications
• Division orders issued by operators establishing each owner's decimal share of production
• Title runsheets and chain-of-title abstracts documenting the recorded history behind an ownership position
• Ownership and decimal-interest spreadsheets tracking who owns what share of which tract
• Royalty and revenue statements received from operators showing production volumes and payment detail
• Well files and production histories, kept and used here strictly as operational business data, not engineering work product
• Purchase and sale agreements documenting acquired or divested mineral and royalty interests
• Offer letters and correspondence with mineral owners during acquisition negotiations
• County-courthouse research copies: the underlying deed book, probate, and instrument copies a runsheet is built from
• Accounting records and QuickBooks company files covering acquisition costs, revenue, and payments to owners

A gap in any of these categories tends to surface at an inconvenient moment: when an operator's revenue statement needs to be matched against a decimal interest calculated two years ago, when a purchase and sale agreement needs to be pulled to confirm exactly what interest was acquired in a tract, or when a title question requires the original courthouse research copy that a runsheet was built from, not just the runsheet's conclusion.

Why a lost workfile here is different: research you re-buy, not a document you re-download

Most small businesses that lose a folder of files can, at worst, recreate the underlying work from scratch with time and effort. A mineral and royalty company's ownership record is a different kind of loss, and it is worth stating plainly because it is the reason this page exists.

The value of this business is its assembled title and ownership record, and much of that record was purchased once already. A title runsheet or a chain-of-title abstract is not simply typed information. It represents a landman's trip to a county courthouse, hours spent pulling deed books and probate files, real per-page copy fees paid at the counter, and the professional judgment applied to organize what was found into a usable record. That work has already been paid for once, in time and in real dollars, by the time it lands as a scanned PDF on an office computer.

Losing that record does not mean re-downloading a file. It means re-buying the research. If a hard drive fails or a ransomware attack encrypts the office machine holding your deed and assignment scans, your runsheets, and your county-courthouse research copies, there is no vendor to call and no download link to click. The only path back is sending someone to the same courthouses to pull the same instruments and rebuild the same runsheet, at the same cost, before the office is even back to where it started. That makes the county-courthouse research copies behind a runsheet, not only the finished runsheet itself, worth a deliberate place in backup scope. The finished runsheet is the conclusion; the underlying deed, probate, and instrument copies are the evidence it was built from, and they are just as expensive to replace.

Why this is not title and escrow work, land surveying, or engineering

A mineral and royalty acquisition company sits near several other businesses that also work with land records, but the work itself, and what needs to be backed up, is genuinely different in each case.

Different from title and escrow work. A title and escrow office works a single closing file that opens and closes within weeks: a specific real estate transaction with a title commitment, a settlement statement, and a closing package that reaches a defined end point. See our title and escrow backup page for that scenario. A mineral and royalty company's ownership record is not a closed file. Chain of title on a single tract can trace back through decades of deeds, wills, and prior assignments, and it keeps accumulating new instruments, new heirs, and new decimal-interest recalculations for as long as the minerals are held. Ownership traced over generations, rather than a transaction that closes and is done, is the core difference.

Different from land surveying. A land surveyor's files are field survey measurement data: boundary surveys, plats, GPS and total station data, and field notes generated by physically measuring a tract. See land surveyor backup for that side of land work. A mineral and royalty company's core record is recorded ownership research pulled from courthouse deed books, lease files, and division orders, not measurements taken in the field. The two kinds of work sometimes touch the same tract, but the underlying files are not the same category of data.

Different from an engineering firm. There is no design authorship in what this page covers. An engineering firm produces original design work, drawings, calculations, and modeling that did not exist before an engineer created them. A mineral and royalty company's well files and production histories are treated here strictly as operational business records, the production numbers and revenue detail that determine what an interest is paying, not engineering design or reservoir modeling work product.

Where backup gaps hide at a mineral and royalty acquisition office

• Land or lease management software treated as the only copy. Your land or lease management system, division order system, or mineral management platform (named here only as software categories, not as an endorsement of any specific product or a compatibility claim) holds a copy of your data under its own systems, which is not the same as an independent backup you control. If the system is cloud hosted, its database lives on the vendor's servers, not on your office computer, and is not something a local backup service reaches. What matters is any runsheet, spreadsheet, scan, or export your team saves locally.
• Ownership and decimal-interest spreadsheets overwritten with no history kept. Some offices save the current decimal-interest spreadsheet over the previous version. If that folder is not part of a backup with version history, an earlier decimal calculation simply does not exist anymore once overwritten, which matters if a revenue statement needs to be checked against an interest as it stood at an earlier date.
• Courthouse research scans saved without a second copy. Landmen and researchers often scan deed books, probate files, and prior instruments to a shared drive or a folder on the office PC, with no confirmation that folder is backed up. This is the folder that matters most given how expensive it is to recreate.
• OneDrive or Dropbox sync mistaken for backup. Cloud sync mirrors whatever is currently on your device. If a file is deleted, corrupted, or encrypted by ransomware, that change propagates to the synced copy too, often within seconds. See cloud sync vs. backup for a complete comparison.
• Division orders and well files saved to one machine. A single landman's laptop often holds the working set of division orders, lease files, and production histories for active projects, with no second copy anywhere until archived, if ever.
• QuickBooks file stored only on one machine. Acquisition costs, revenue received, and payments to mineral owners are often kept in a single office PC's accounting file with no second copy anywhere. Intuit's own documentation specifically notes that backing up only to the same machine is not adequate protection.
• Backup media stored at the same office it is meant to protect. An external hard drive kept beside the office PC offers no protection against fire, water intrusion, theft, or a storm affecting the whole building at once, a real consideration for offices across the Gulf South. The 3-2-1 rule below covers how an off-site copy addresses this.
• Staff or landman turnover removing backup knowledge. Small land offices often rely on a mix of employees and contract landmen. When the person who set up backup, or who knows which folders hold the courthouse research, moves on, that knowledge often leaves with them.

Understanding the 3-2-1 backup rule for a mineral and royalty office

The 3-2-1 rule is a straightforward framework promoted by CISA and widely used in small-business backup guidance. Applied to a small mineral and royalty acquisition office, here is what it looks like against the files that actually matter.

A backup standard for mineral and royalty company operators

The checklist below reflects CISA small-business backup principles and FTC small-business cybersecurity guidance, applied to the file environment of a small mineral and royalty acquisition office. This is a starting framework for backup decisions, not legal, tax, title, or investment advice, and it does not tell you what records any authority requires you to keep.

• Map every machine in the office. List every Windows computer on site: the principal's desktop, a landman's laptop, and any shared workstation with local runsheet, lease, or accounting files. For each one, ask what data lives there that is not copied anywhere else. That list defines your minimum backup scope.
• Include your courthouse research and runsheet folders explicitly. These scans are often saved outside your land or lease management system, named here only as a software category and not as an endorsement of or a compatibility claim about any specific product, in a separate folder organized by county or by tract. That folder needs to be explicitly included in your backup configuration rather than assuming the system provides an independent copy you can restore from.
• Add ownership and decimal-interest spreadsheets to backup scope with version history. These working spreadsheets are updated frequently as new instruments are found or new heirs are identified. Version history lets you recover an earlier decimal calculation if a revenue statement needs to be checked against an interest as it stood at a prior date.
• Retain enough version history to reach back through a full acquisition and revenue cycle. CISA guidance notes that ransomware and accidental deletions are often not discovered for days or weeks after the event, so a 24 to 48 hour backup window may not reach a clean, pre-incident copy.
• Encrypt backup data in transit and at rest. Purchase and sale agreements and offer correspondence include personal and financial details for mineral owners and counterparties.
• Monitor backup jobs and receive failure alerts. A backup job that fails silently leaves you with no current coverage and no warning, particularly during an active acquisition push.
• Test restores on a regular schedule. A practical cadence is a quarterly spot-restore: pick a runsheet, a division order, a decimal-interest spreadsheet, and a QuickBooks file from different dates, and confirm you can retrieve and open them.
• Document who handles recovery. Someone in the office should be able to answer three questions without searching: what is backed up, where does it go, and how do you start a restore, which matters more given how often small land offices rely on contract landmen.

A separate but important note belongs here plainly: the recorded instruments themselves live at the county courthouse, and this page does not change that. Your company remains solely responsible for its own regulatory, tax, and contractual recordkeeping obligations. Everyday Backups is a general file-backup service, not a legal, compliance, or records-management tool, and a backed-up copy of a scanned deed, lease, or runsheet has no bearing on the recorded original.

For a broader self-assessment of your current backup posture, see the small-business backup checklist. For ransomware-specific preparation, see ransomware restore readiness. If your business is a residential or commercial closing operation rather than a mineral and royalty acquisition business, see backup for title and escrow companies instead. For accounting-file specifics, see accounting and bookkeeping backup or QuickBooks backup for small businesses. And for a general framework behind all of this, see the 3-2-1 backup rule explained.

Land and lease management software, and QuickBooks: what backup actually covers

Two categories of software generate the bulk of a small mineral and royalty office's daily records: whatever land, lease, or division order system the office uses, and its accounting platform. Understanding what your backup does and does not cover for each is essential before you assume you are protected.

Ransomware and the mineral and royalty office

The FTC and CISA both publish guidance specifically noting that small businesses, including businesses with accumulated ownership and financial records, are targets of ransomware campaigns. The reason is practical: small businesses often have less IT infrastructure than large corporations, making them easier to compromise, while still holding records that create pressure to pay a ransom rather than lose years of research.

For a small mineral and royalty office, the factors that make ransomware particularly consequential are: runsheets, lease files, and courthouse research concentrated on one or two Windows machines, QuickBooks accounting covering years of history stored locally, no backed-up copy of ownership and decimal-interest spreadsheets, and typically no dedicated IT staff checking backup health daily. Everyday Backups is a data recovery tool, not a security product, and it does not prevent ransomware from occurring, nor does it promise an office can keep operating while systems are down.

CISA's #StopRansomware guidance identifies offline and encrypted backup copies as the primary technical recovery mechanism when ransomware has encrypted production files. A backup connected to the same network as the infected machines, or a cloud 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 small mineral and royalty office, a ransomware event does not just cost time, it can cost the courthouse research fees and landman hours that built your runsheets in the first place, if no independent backup exists. See ransomware restore readiness for a complete breakdown of what a ransomware-capable backup posture looks like. What a backup changes is whether there is a path back at all, rather than losing years of ownership research outright.

Hurricane season across the Gulf South

Independent mineral and royalty companies, landman firms, and small non-operated working-interest owners with offices across Mississippi, Louisiana, and Texas operate in a region where hurricane season is not a hypothetical. A storm that threatens an office building also threatens the computer sitting a few feet from a window, and that computer typically holds the runsheets, lease files, division orders, and ownership spreadsheets for the entire operation.

Backup addresses one piece of that risk: the data. If the office computer is damaged, flooded, or lost during a storm, an off-site, encrypted backup means the records on it still exist somewhere the storm never reached. Backup does not protect the office or anything physical, it makes no insurance-related claim of any kind, and it is not a substitute for a hurricane preparedness or evacuation plan. It covers one part of storm readiness: making sure the ownership record your business is built on survives even if the machine holding it does not. See hurricane season business file backup for more on preparing files ahead of storm season.