Help center
Getting started
Importing from another property manager
How to preserve a source export and prepare clean records now, what Aptoria’s planned migration review checks, and why the old system stays your source of truth until tenant and lease imports open.
The short answer
Today you can add your properties and units to Aptoria. Importing tenants, leases, and balances from another property manager is planned, and migration review staging is limited to an approved design-partner cohort. Prepare clean source records now, keep the untouched export, and keep the old system as your source of truth until a migration into Aptoria is available and you have reconciled balances, documents, and active leases.
Start from the migration guide
If your portfolio lives in another system, preserve the untouched export before transforming anything. The launch review order is Buildium, TurboTenant / Azibo, CSV, OFX / QuickBooks Web Connect (.qbo); the next source-specific adapter work is DoorLoop, RentRedi, Avail, Stessa. Other catalog profiles document a managed-export route, not a certified live adapter.
Current PMS routes normalize supported exports into content-bound review staging with recorded hashes and review evidence. Approval does not create or change live portfolio records; a separately implemented, authorized, reconciled cutover is still required. Keep work-order media, documents, screening records, payment mandates, bank history, credentials, and any unsupported fields as separately inventoried source evidence rather than flattening or silently dropping them.
Normalize the complete source bundle into review staging
Migration review staging is limited to an approved design-partner cohort. In it, the guarded PMS mapper accepts supported property, unit, tenant, lease, payment, and vendor records only when stable source IDs and relationship IDs close. It stages normalized records for review and holds sensitive or unsupported fields by name; it does not create live portfolio records.
Before relying on any target, check stable source IDs and closed property → unit → tenant → lease relationships; active lease terms, opening receivables, payments, credits, and unapplied cash; security deposits tied to tenant detail and to trust-liability evidence; source closing totals bridged to target opening totals and bank evidence; and the unmodified source files, held fields, exceptions, reviewer sign-off, and a plan for returning to the old system. A separate quick property/unit CSV screen adds basic property and unit rows to your workspace, but that convenience screen is not a historical PMS migration and is not evidence that a ledger reconciled.
Reconcile tenancy and money before any future cutover
Opening balances are controlled carry-forward evidence, not substitutes for payment history. Reconcile receivables, credits, unapplied cash, returned payments, and one-off adjustments at the same cutoff. Security deposits must agree both to tenant-level detail and the applicable trust-liability/bank evidence; they must never be treated as rent income.
Payment methods and autopay mandates do not transfer through these files, and online rent collection and autopay in Aptoria are planned. Keep the former system or a retrieval-tested archive available through stabilization, and decide in advance what would make you return to it.
Frequently asked questions
Related articles