Migrate from Realpage to Nutshell

RealPage tenants and prospects map to Nutshell People. The primary challenge is preserving the unit association — we store the unit reference as a custom text field (Lease_Unit__c) on the Person record so teams can still identify which unit a contact is tied to.

RealPage properties and buildings map to Nutshell Companies. The property address becomes the Company address, and property type classifications (residential, commercial, mixed-use) are stored as custom fields. For multi-unit properties, each unit can be linked via a custom Unit_Count__c field on the Company record. Owner information migrates as the primary contact on the Company record, preserving the relationship between the property manager and the ownership entity.

Units do not have a standalone equivalent in Nutshell. For lease-tracking purposes, we create a Company record per property and store unit identifiers (unit numbers, floor, type) as a custom multi-value field or link them via a custom object if the tenant-to-unit relationship needs to remain queryable.

RealPage lease agreements map to Nutshell Deals. The lease value (rent × lease term) becomes the Deal amount. Lease start and end dates map to custom date fields (Lease_Start__c, Lease_End__c) since Nutshell Deals use a single CloseDate field. The deal stage reflects lease status: Open, Under Negotiation, Executed, or Expired.

Property owners in RealPage are people with a company affiliation. We map them as a Nutshell Person linked to a Company record representing their ownership entity. This preserves the person-level contact and the company-level entity for reporting on owner portfolios.

RealPage maintenance tickets migrate as Nutshell Tasks with Type='Maintenance'. Original ticket subject, description, priority, created date, and assigned technician are preserved. The related unit or tenant is noted in the task description for traceability. Any maintenance-specific workflows like auto-assignment rules, escalation timers, or vendor dispatch sequences do not migrate and must be rebuilt using Nutshell's task triggers and automation sequences.

RealPage payment history has no direct equivalent in Nutshell's CRM model. We attach payment summaries as Notes on the Person and Deal records for historical reference, but financial transaction data should remain in RealPage's accounting module or be exported separately for reconciliation.

Standard communication activities in RealPage (calls, emails, meetings) map 1:1 to Nutshell's Activity types. Timestamps, subject, description, and related contact/person links are preserved during migration. Owner is resolved by email match between the RealPage staff record and the Nutshell user account to maintain accurate activity attribution after migration.

RealPage staff records map to Nutshell users by email resolution. If a RealPage staff member has no matching Nutshell user, their records are assigned to a fallback owner flagged for admin review before migration finalizes. This prevents data orphaning while ensuring your team can verify and correct any unresolved ownership assignments during the pre-migration review phase.

RealPage tenant-specific custom fields such as rental history flags, guarantor info, and background check status become custom fields on Nutshell People. We create these fields in Nutshell during schema setup before data loads, and map values using value-by-value assignment for pick-list fields to preserve data integrity and maintain the original context of tenant information across the migration.

RealPage lease-specific custom fields (e.g., CAM charges, pet policy, renewal options) map to custom fields on Nutshell Deals. The transformation requires type-aware mapping — date fields to date fields, currency fields to currency fields — to maintain reporting integrity in Nutshell.

RealPage lease documents and related files are re-uploaded as attachments on the corresponding Nutshell Deal record. File size limits in Nutshell (25MB per file) apply; larger files are flagged for chunked upload or alternative storage reference. Document naming conventions are preserved to maintain traceability to the original RealPage lease record throughout the migration process.