Migrate your Realpage data

Units are the core inventory object in RealPage. Each unit carries lease status, market rent, and amenities. We migrate units 1:1 with standard fields intact; any property-level custom fields are mapped as supplemental columns in the export.

Residents are tied to active leases and carry contact details, payment history, and balance. We map resident records including lease association and outstanding balance into the destination as standard contact or tenant objects.

Leases include start/end dates, rent amounts, security deposits, and associated tenants. We migrate lease records with their fiscal terms intact; lease document attachments are preserved as binary blobs alongside the record.

Work orders track maintenance requests tied to units and residents. The field schema varies between OneSite and Propertyware editions. We map to the destination maintenance/ticket object and flag any custom status values that require enumeration mapping.

Vendor records include contact info and AP account labels. RealPage's vendor structure uses a flat list with role-based account access restrictions. We map vendors and their associated AP labels but flag any vendor records restricted by user role that may not appear in a standard export.

General Ledger entries are exported via the GL Detail report. RealPage's export formatting includes subtotal rows and headers that must be stripped. We clean and normalize line items, preserving account codes, amounts, and posting dates for fiscal continuity.

Commercial operating expense recovery reports require three exports (Recovery Reconciliation, GL Detail, Rent Roll) combined and cleaned. The exact navigation paths vary by RealPage version and license tier, so we confirm access during scoping.

Utility billing uses submeter data or ratio allocations per unit. We migrate allocation percentages and billing history but flag any submeter readings that require integration with the destination's utility tracking module.

Resident screening data from LeasingDesk is held as a separate consumer report. We migrate screening metadata (applicant name, result, date) but do not transfer the underlying credit/tenant history file, which must be re-pulled from the screener directly.

Knock CRM leads and prospect records sit in the leasing module. We extract lead records with source attribution and lifecycle stage, mapping them to the destination CRM's equivalent lead or contact object.

Documents—lease agreements, notices, inspection photos—are stored per unit or resident. We migrate attachment references and binary files, but large document repositories may require a separate file transfer step beyond the standard record export.