Where is my home-record backup? Understanding PropertyOS exports, Files, and iPhone backup

A home record saved in an app, a file exported to Files, and a backup of the iPhone are not interchangeable. To know where you will find your PropertyOS information later, identify what the operation creates, which location receives it, and what is required to use it again. The word “saved” alone does not answer those three questions.

PropertyOS says users can export or back up their home record and that external backups go to a Files folder they select. It also states that no account is required and there is no Eternity Labs cloud. Those are the starting facts, not a promise that every file is automatically copied elsewhere or can be restored through any route. Current PropertyOS presentation.

Imagine that I am considering replacing my iPhone and want to understand how I have preserved my home documents first. This is a fictional planning example. I have not exported a real PropertyOS record, restored a device, or tested a backup for this article. The guide offers a way to ask precise questions without inventing undocumented screens or file formats.

Which result do I actually need?

Before choosing an operation, I would finish one sentence: “Later, I want to be able to…” The ending matters. Reading one document, continuing to edit a complete home record, and restoring a phone after replacement are different goals.

In the example, I want to continue using the organized record, with its context, after moving to another phone. A readable copy of one document would be useful, but it would not by itself establish that every room, equipment relationship, and event can be reconstructed.

If I only wanted to read the information on another screen, I might need a different output. I would examine the export choices actually offered rather than assume that all exports have the same contents. The public description does not specify a universal format or a complete migration sequence.

Choosing the result first prevents a common misunderstanding: accepting an operation because its name sounds reassuring. “Export completed” is useful information only when I know what was exported and how that output serves my goal.

Four terms I would keep distinct

I would use these definitions while reading the available controls. They explain the questions, not the exact labels inside PropertyOS.

An export might be suitable for reading without being suitable for restoring an editable record. A backup may require the appropriate application rather than behave like an ordinary document. I would establish those properties from the actual operation and documentation, not from the filename alone.

The most useful distinction is between having something I can see and having a recovery method I understand. Both can matter, but they are different forms of verification.

Files is a place to browse locations, not one storage destination

When an app asks me to choose a folder in Files, I would read the location above that folder. Two folders with similar names can belong to different storage providers. Remembering only “I put it in Files” leaves out an essential part of the address.

Apple identifies On My iPhone as local device storage and iCloud Drive as a location whose files synchronize through iCloud. Files can also show connected storage and supported third-party providers. These are features of Apple's file interface, not a list of destinations independently tested with PropertyOS. Apple's guide to finding files.

In the fictional move to a new phone, that distinction changes my next question. If the destination is local to the existing phone, how will I access the file when that phone is unavailable? If I choose a cloud-backed location offered by the system, have I verified the file there under the intended account?

Neither folder name answers every question about completed transfer, later access, or compatibility. I would inspect the actual result rather than assume that selecting a destination proves the whole preservation process finished successfully.

“No Eternity Labs cloud” does not describe every Files provider

The PropertyOS listing says there is no Eternity Labs cloud and that the user chooses the folder for an external backup. Those statements can coexist with the user choosing a location that belongs to another service, where that location is available. The provider selected in Files has its own role.

For example, I would not describe an output placed in iCloud Drive as “kept only on this iPhone” merely because PropertyOS performs document analysis locally. Where analysis runs and where I choose to store an output are separate facts.

The same care applies to privacy wording. The current product description discloses limited pseudonymous product analytics without home content, as well as on-device OCR and document analysis. I would preserve that distinction instead of summarizing the app as collecting no data whatsoever. PropertyOS App Store description.

My choice of a backup destination should therefore be deliberate. I would use a location I recognize and can access again, while checking the controls offered by the current app and system. This guide does not certify a storage provider or prescribe one service for every household.

The note I would keep beside a preservation operation

For the fictional preparation, a short note could record the app version, the date, the operation selected, the intended scope, and the destination. I would copy the actual wording shown when it matters rather than improve it into a promise the interface never made.

I might write: “Prepared a preservation file for the home record; destination checked in the chosen Files location; recovery procedure still to confirm.” This sentence is an example of my note, not an operation performed or a status supplied by PropertyOS.

I would also make clear which moment the file represents. If I add new documents afterward, the earlier output should not silently become my description of the current record. Its date helps me understand the gap between what I preserved and what I continued to change.

A useful name can include a neutral description and date without exposing a full street address. I would choose wording I can recognize later. A succession of files named “final,” “new final,” and “latest” makes it unnecessarily difficult to tell what each one represents.

Seeing a file and proving recovery are different checks

After an operation, I would leave the application's current view and locate the output through Files. That verifies something concrete: I can find an item at the destination I intended. It does not prove that the output includes every part of the working record or that a new installation can use it.

If it is a documented readable export, I would inspect the available content and compare a few items with the source record. If it is a backup package, I would not rename its extension or force it into an unrelated app because it lacks an ordinary preview. I would look for the appropriate documented recovery instructions.

The public PropertyOS description establishes export and backup capabilities but does not give me a complete restoration procedure or a list of supported interchange formats. I cannot turn that short description into a tested promise about restoring this fictional household record on another phone.

For a move that depends on recovery, I would resolve that question while the original record is still available. I would not use the only working copy as an experiment. An unsupported restoration attempt would tell me less than getting the required steps and prerequisites clear first.

What does the iPhone's own backup add?

Apple describes iCloud Backup as preserving device information that is not already regularly synchronized with iCloud. Its explanation includes app data and distinguishes that process from services such as iCloud Drive, where files synchronize separately. What iCloud Backup includes.

This gives me a reason to inspect the backup settings and status of the actual phone. It does not let me state, without that inspection, that every PropertyOS attachment in this example is present in a successful device backup. General platform documentation and a verified backup of a particular phone are different evidence.

I would keep three questions separate: did I create an application output, did the chosen file location receive it, and what does the device backup cover? Completing one of those steps does not automatically answer the others.

I would also avoid confusing a synchronized folder with a historical copy I can restore from any date. The existence of a file across devices is not, by itself, a guarantee of every earlier version or recovery scenario. I would consult the relevant service's current instructions for those specific needs.

The support question I would prepare before changing phones

If the recovery route remains unclear, I would prepare a focused question: “I use PropertyOS version [actual version] and want to continue my existing home record on another iPhone. Which operation should I use, what does its output include, and which documented steps read that output on the destination device?”

I could add the name of the selected operation and the general type of destination, without attaching the home's documents. If a version or format matters, I would provide the real information. The placeholders are deliberate; they must not be filled with invented observations.

This is a locally prepared example, not a message sent, a guaranteed support response, or a hidden restore feature. Its value lies in connecting a specific intended result with the facts still missing.

After clarification, I would keep the answer with the version and date it concerns. I would not assume an old explanation applies unchanged to every future release. Nor would I treat restoring a purchase as the same operation as restoring a data file: one concerns access rights, while the other concerns the record itself.

How the current access terms affect this plan

The US and French listings checked on September 16, 2026 show PropertyOS 1.0.1 for iOS 18 or later. Non-subscribers receive seven complete days of access from the first opening of this version, without an automatic subscription or automatic charge.

Afterward, continued access requires choosing a monthly or annual auto-renewable Premium subscription handled by Apple. The listing says existing records remain stored if Premium ends and return after subscribing or restoring purchases. There is no lifetime purchase in the current offer. Current PropertyOS listing.

That statement about retained records does not establish an independent backup or a migration completed on a different device. I would also avoid promising which export controls remain usable in an expired-access state when the public description does not specify them.

For my fictional change of phone, I would check the relevant access conditions before relying on a future operation. Keeping data, being entitled to open it, locating an external file, and understanding recovery are four related questions that still deserve distinct answers.

A useful decision ends with a location and a next step

I would finish this preparation when I can name the working record, the purpose of the output I created, the location I checked, and the recovery information I have or still need. “Everything is backed up somewhere” would not be a satisfactory note to myself.

If the immediate task is only to improve the underlying document packet, the PropertyOS scanning and OCR guide deals with readable pages and reviewed information. Preservation cannot repair an incomplete source document; it carries forward what I actually organized.

For the wider arrangement of rooms, equipment, and records, the PropertyOS home-record guide provides the context. Here, my next step would follow the unanswered question: inspect the destination, verify the output's purpose, or obtain the documented recovery procedure before making the original unavailable.