Migrate from Realpage to Twenty CRM

RealPage prospects and contacts migrate to Twenty People records. Email, phone, job title, and name fields map directly. RealPage's leasing agent assignment resolves to a Twenty workspace member by email match. Prospects without email land in Twenty with a manual-flag note for follow-up.

RealPage company and property records map to Twenty Companies using a direct migration approach. Property name becomes the Company.displayName field. Property address information maps to the company's address fields including street, city, state, and postal code. Website and industry data are preserved where populated in the source system. Parent-child property hierarchies are preserved using Twenty's company relation fields to maintain organizational structure.

RealPage lease deals migrate as Twenty Opportunities, preserving all deal-critical information. The deal amount from RealPage maps directly to Opportunity.amount. Lease stage values (Active, Pending, Closed) map via a value mapping to a Twenty Opportunity stage pick-list that is configured before import begins. The close date from the lease term maps to Opportunity.closeDate for pipeline forecasting accuracy.

RealPage resident communication logs including call notes and email summaries migrate as Twenty Tasks attached to the corresponding People record. Original timestamps from the communication are preserved in Task.dueAt and agent names are maintained in Task.assignee. Task.body carries the full communication summary text from RealPage for complete leasing history.

Property site visit notes and leasing meeting summaries from RealPage migrate as Twenty Notes attached to the related Company or People record. Note.body preserves the complete text of each visit or meeting record. Note.date is set to the original visit date extracted from RealPage to maintain accurate historical timeline context.

RealPage custom fields on prospects — such as lead source, property interest type, or budget range — require pre-creation in Twenty Settings → Data Model before import. Each custom property maps to a correspondingly typed custom field on People. Field types must match (text → text, number → number, select → select).

RealPage lease deal custom fields (unit type, lease term length, move-in date) need custom field creation in Twenty's Opportunity object before migration. These are created via Settings → Data Model → Opportunities → Add Field. Data then loads via CSV mapping.

RealPage owner IDs and leasing agent assignments are resolved by email against Twenty workspace members. Unmatched owners are flagged and assigned to a designated fallback workspace member before migration runs. This resolution prevents orphan records and maintains referential integrity in Twenty's relational model.

RealPage prospect-to-property associations map to the People → Company relation in Twenty. The People record holds a companyId pointing to the related Company record. If a prospect is associated with multiple properties, the primary property becomes the companyId; secondary associations are noted in a custom field.

RealPage lease deal-to-prospect associations map to Opportunity → People relations in Twenty. The Opportunity record holds a peopleId pointing to the lead or contact who owns the deal. This association preserves the deal context and prospect relationship within Twenty's pipeline view interface.

RealPage lease documents and attachments are not included in CSV exports. FlitStack AI re-uploads identified documents to Twenty as file records linked to the relevant Opportunity or Company. Document re-upload is a manual step confirmed during the sample migration review before full cutover.