Data portability means more than downloading a PDF or receiving a folder of CSV files. A portable export preserves the records a landlord needs to continue operating: stable property and party identifiers, leases and attachments, tenant-ledger transactions, balances, work history, vendors, approvals, timestamps, and the relationships among them. The format must be documented well enough for another system or person to interpret.
A usable export distinguishes current state from history. A tenant balance without the charges, payments, returns, and adjustments behind it is not a portable ledger. A work-order list without photos, messages, vendor evidence, or status dates is not a portable maintenance record. Files should carry an export cutoff, schema or field definitions, time zone, encoding, and a manifest that explains what is included and what the provider cannot export.
For example, an owner receives properties.csv, tenants.csv, and transactions.csv. The files open, but unit identifiers differ across tables and negative amounts are undocumented. The data is technically downloadable yet not safely portable. A mapping document and referential-integrity check are required before those rows can recreate leases or balances in a destination system.
Test portability before cancellation or an emergency. Export a small representative sample, verify that attachments open, join keys resolve, totals reconcile, and access controls cover the transfer. Portability does not guarantee a destination supports every feature. It gives the owner a complete, intelligible source package from which documented migration decisions can be made.
Minimum viable export package
The package should let a reviewer reconstruct both current operations and the history behind material balances.
•
Data dictionary, file manifest, export cutoff, time zone, and encoding.
•
Stable IDs linking properties, units, leases, people, transactions, and work.
•
Original documents and attachments with filenames or hashes tied to their records.
•
Transaction history rather than opening balances alone.
•
Known exclusions, transformations, and provider-specific fields.
Scenario: the export passes but the joins fail
Every CSV is syntactically valid, yet 14 payment rows reference unit IDs absent from the unit file. The correct outcome is an exception report and corrected export, not silently assigning the payments to the property-level suspense account.
Portability test before commitment
Ask a provider to export one lease, its complete ledger, one work order with attachments, and the related audit history. The test reveals whether “export available” means operational continuity or only summary reporting.
Related tools & guides
Editorial ownership
Written and maintained by the Aptoria editorial team
Repository and source review completed July 28, 2026. Aptoria reviews scope, source fit, examples, limitations, links, and publication gates. This record does not claim attorney, CPA, lender, appraiser, or other independent professional sign-off.
Primary and authoritative sources
Related terms
AI & autonomy
Property management system of record
The designated property-management source whose current records are authoritative for each defined class of operational data.
AI & autonomy
Migration reconciliation
The evidence-based comparison that proves material records and control totals survived a property-management system migration.
AI & autonomy
Provider receipt
A durable record from an external service showing what request it accepted, rejected, or completed under a provider-assigned identifier.
From definition to done
Aptoria runs the routine work behind these terms — rent, books, and screening — inside limits you set. Free for your first unit.
Start free