Migrate from REIPro to Twenty CRM

REIPro stores investor contacts with name, email, phone, and mailing address. These map directly to Twenty's People object. Property investment contacts may include seller names and phone numbers without email — all fields migrate. Original create dates are preserved as a custom datetime field since Twenty's CreatedAt is set at migration time.

REIPro property records include the owner's legal name and address, which function as a company record in CRM terms. The property address becomes the Company address in Twenty. Multiple deals can reference the same owner — we deduplicate by owner name and address before creating Company records.

REIPro deals are anchored to a property address and include deal stage, offer amount, purchase price, ARV estimate, repair estimate, and equity calculation. These migrate as Twenty Opportunities linked to the corresponding Company (seller) and Person (investor contact). Deal stage maps to Opportunity stage via value-mapping.

REIPro's 10-step workflow tracker assigns each deal a step number (1–10) that represents its position in the investment process. Twenty has no native step-number field on Opportunities. We preserve the step number as a custom field (Deal_Step__c) on the Opportunity and export a step-definition JSON for the admin to reconstruct in Twenty's workflow builder.

REIPro's 12 nationwide lead sources (absentee owner, pre-foreclosure, bank-owned, etc.) are stored as metadata on each property record. Twenty has no native lead-source field. We preserve the lead source category as a custom select field (Lead_Source_Category__c) on Opportunity and note that active skip-trace credits do not transfer.

REIPro calculates estimated equity, after-repaired value (ARV), repair cost estimate, and offer price for each property deal. These are stored as numeric fields on the deal. We map them to custom Number fields on Twenty's Opportunity object: Estimated_ARV__c, Repair_Cost_Estimate__c, Estimated_Equity__c, and Offer_Price__c.

REIPro provides skip-trace credits that return owner phone numbers and additional contact data. This derived data does not have a native equivalent in Twenty. We preserve skip-trace results as a Note attached to the relevant People record or as a custom phone field (Skip_Trace_Phone__c) where email match is confirmed.

REIPro's Direct Mail Engine stores campaign definitions and mailing history tied to property records, including campaign name, target list size, send date, and postage method used. Twenty CRM has no native campaign-tracking or direct-mail object, so these records lack a structured home in the target system. We export campaign names, send dates, and mailing list references as a Note attached to the associated Opportunity. This preserves the audit trail for historical reference and allows your team to review past mailing activity per deal, though it does not replicate the active campaign management functionality that REIPro provides.

REIPro provides MLS comparables for properties in all 50 states. This is reference data rather than transactional CRM data. We store the most recent comp summary (comparable address, sale price, date) as a Note on the Opportunity rather than as structured fields, since Twenty has no native comps object.

REIPro team members (Standard up to 3 users, Team up to 12) are matched to Twenty Workspace Members by email address before migration. Unmatched owners are flagged for the admin to invite to Twenty first. All deal and contact records require an owner assignment in Twenty.

REIPro logs follow-up calls, email interactions, and notes tied to each deal. These migrate as Twenty Tasks (for calls and emails) or Notes (for free-form notes). Original timestamps and owner assignments are preserved. The task type maps via a custom select field on the Task object.

REIPro supports custom fields added by the user on deal records. Each custom field is evaluated by type — text, number, date, select — and created as a matching custom field in Twenty through Settings → Data Model before the import runs. Fields must exist before CSV import.