Migrate from Realpage to Salesforce Sales Cloud

Every RealPage property maps to a Salesforce Account. The property name becomes Account.Name, address fields map to BillingAddress, and property-type, year-built, and unit-count data populate custom fields on the Account. The Account's industry field is set to 'Real Estate' to align with Salesforce's standard industry taxonomy.

RealPage units do not have a direct Salesforce equivalent — Salesforce Accounts do not track sub-units natively. FlitStack creates a custom Unit__c object with fields for unit number, floor plan, bedrooms, bathrooms, square footage, and monthly rent. Unit__c is linked to Account via a lookup field. Each unit record belongs to one Account (property).

RealPage residents and leasing prospects become Salesforce Contacts. First name, last name, email, phone, and move-in date migrate directly. The Contact's AccountId is set to the Salesforce Account representing the property where the resident is or was housed. Prospects without a signed lease migrate with a custom Prospect_Status__c flag.

RealPage allows a resident to lease multiple units across multiple properties — an N:N relationship. Salesforce's standard AccountContactRelation handles the Contact-to-Account link, but for multi-unit residents, FlitStack creates a custom Resident_Unit__c junction object storing the specific unit, lease term, and rent amount per association. This preserves the full residency history.

RealPage lease records (start date, end date, monthly rent, security deposit, lease status) have no native Salesforce equivalent. FlitStack creates a Lease__c custom object linked to both the Contact and the Unit__c record. Lease status (Active, Expired, Pending Renewal) migrates as a custom pick-list field. Renewal reminders and rent-change logic require Salesforce Flow to rebuild.

RealPage owner records vary by configuration — some represent property owners (investors), others represent the operating company. Investor owners map to Salesforce Accounts with an Owner_Type__c flag. Operating-entity owners map to Salesforce Users matched by email for owner assignment on Contacts and Units. Your team specifies which owner type applies before migration runs.

RealPage vendors (maintenance contractors, utility providers) map to Salesforce Accounts with a Vendor__c checkbox flag and Vendor_Type__c pick-list (HVAC, Plumbing, Electrical, etc.). Vendor contact persons migrate as Contacts on the vendor Account with a Role__c field identifying their trade. Each vendor Account also stores service area, insurance coverage dates, and W-9 status to support vendor compliance tracking within Salesforce.

RealPage work orders (maintenance requests, make-ready tasks, inspection records) have no Salesforce standard equivalent. FlitStack creates a Work_Order__c custom object linked to the Unit__c record and the assigned vendor Account. Status (Open, In Progress, Completed), priority, and work-order type migrate as custom pick-list fields. Maintenance scheduling and assignment automations require Salesforce Flow to rebuild.

RealPage's Common Area Maintenance (CAM) recovery and utility billing records are property-specific accounting entries. These migrate as custom Utility_Recovery__c records linked to the Account, storing expense pool, recovery amount, billing period, and tenant allocation. The accounting logic (actual vs. estimated billing) does not transfer and requires a rebuild in Salesforce or an ERP integration.

RealPage payment history and GL ledger entries migrate as custom Payment__c records linked to the Contact and Lease__c. Fields include payment date, amount, payment method, and status. Full accounting reconciliation requires a connection to an ERP like NetSuite or QuickBooks — Salesforce is not a double-entry accounting system. Payment data migrates for historical reference, not as active financial records.