Migration guide · Rentvine
Migrating from Rentvine: what the work actually looks like
A bounded, export-by-export migration with the counts and balance tie-outs agreed in writing before anything is imported — written as guidance, with the honest limits stated where they belong.
How you get your data out.
Rentvine documents an open REST API for its accounts, so the extraction runs against your own account with API credentials an administrator creates and scopes to the migration. Page sizes, rate limits and retry behavior are confirmed against the current Rentvine documentation when the migration is scheduled, not assumed from a first response.
Before anything moves
What is agreed in writing first.
- Agree the scope in writing: the manager scope, properties, units, leases, applications, people, work orders, and the accounting period included.
- Have an administrator create the API credentials, record the account subdomain and the agreed read-only extraction scope, and keep the credentials with the person responsible for the extraction until they are rotated or revoked after the pull.
- Agree the financial scope in writing. Open balances plus a defined year-to-date period may be appropriate; it is not an automatic promise to migrate all historical transactions, bills, or documents.
The sequence
The migration, in the order it happens.
Export the portfolio skeleton
Pull properties, then units. These establish the mapping of properties, units, ownership and source record identities that every later step hangs off.
Export people and applications
Pull applications and the agreed people and resident data. Resolve duplicate or withdrawn applications before transforming anything into resident and lease rows.
Export leases and open operations
Pull leases with their terms, residents and units, then the agreed work orders. Review open work separately from closed history, and keep an exception list for attachments and notes that have no agreed destination.
Export the money in scope
Pull the accounting records needed for open balances, deposits and the other agreed cutover amounts, and reconcile them against the lease-level ledger before preparing opening balances.
Transform with an ID map, and import one slice first
Transform the extraction into the schemas the importers accept, with a source-ID map and a reviewable preview where available. Import one property — or another agreed small slice — first, confirm counts, and review exceptions before expanding.
Tie out, then cut over
Agree the activity window, take a final lease and accounting snapshot for the in-scope open leases, and reconcile each open balance to the source ledgers and reports. Only after the tie-out is accepted turn on collection in Tenant Office. Running both systems active without a tie-out can double-bill a resident.
On the Tenant Office side
What happens here, and what it leaves behind.
- Imports you run in Tenant Office keep the identifiers the records arrived with, and each import leaves a read-only reconciliation report — counts and exceptions — before any business record is written.
- A point-in-time CSV export of your portfolio, with those retained source keys and import provenance, stays available at any time. Your records remain yours to take away, with no exit fee.
Honest caveats
What this guide cannot promise.
- An open API on the source side is not an integration on ours. There is no Rentvine-to-Tenant Office connector in this path, and an API pull does not automatically import every transaction, document, or custom field.
- Last-modified timestamps support an agreed repeat pull, not continuous synchronization, and not proof that historical records were complete.
- A successful import preview is not proof that every historical transaction, document, or external payment instruction migrated. Acceptance is for the agreed scope, agreed together, before old workflows are switched off.
- A field that has no agreed destination is a review item, never an invented value and never something silently dropped.
This guide is derived from our own migration playbook for Rentvine, whose operational facts were checked against sources read in October 2026. Pricing, exports, plan terms and vendor behavior can change; verify them again when a migration is scheduled. Rentvine and its product names are trademarks of their respective owners, and Tenant Office is an independent product, not affiliated with or endorsed by them.
Keep reading
See it working
The honest way to evaluate a migration path is to walk one work order through, end to end, in the workspace.