Migrations

See your move before anything moves.

This is the same path a landlord follows inside Aptoria to switch from another property-management system. Pick your current software, see its export steps, and check a CSV's column headers right here. The check runs in your browser; nothing is uploaded from this page.

Aptoria

One file per record type

Properties

Units

Tenants

Leases

Payments

Vendors

Buildium

Azibo

TurboTenant

Migrations

Step 1

Choose your current system

Each source has its own export route and field names.

Step 1

Export your records

Follow the provider-specific steps to download CSV files.

Step 2

Check the headers

Column names are matched to Aptoria fields before any upload.

Step 3

Dry run and stage

In your workspace, rows are validated and staged for review.

Step 4

Reconcile, then decide

You review counts and exceptions before any cutover.

Step 5

One file per record type

Properties

Provider-issued property IDs and location details.

Units

Unit and property relationship IDs.

Tenants

Tenant IDs and contact details.

Leases

Lease, unit and tenant relationship IDs.

Payments

Payment and lease relationship IDs.

Vendors

Vendor IDs and contact details.

Step 2 · Export

Step 3 · Check your headers

Steps 4–5 · In your workspace

Dry run, staging and reconciliation

Dry run

All files are validated together. You see a completion percentage, recoverable fixes and any blocking issues before staging.

Staged batch

Valid rows are staged with a file checksum and per-entity counts. Staging does not change live records.

Reconciliation review

You compare counts, exceptions and unmapped fields, then decide whether to proceed. Nothing cuts over without that decision.

See your move before anything moves.

Where are you moving from?