Migrate from REIPro to Salesforce Sales Cloud

REIPro contacts map directly to Salesforce Contacts. During migration, each contact is linked to its primary company via Contact.AccountId. Contacts without a company assignment in REIPro are placed in a default 'Unassigned Accounts' record or, if they have no associated deals, routed to a Salesforce Lead based on deal history. Owner IDs are resolved by email matching to Salesforce users, with fallback assignments created before the final data load.

During migration, REIPro contacts are evaluated against the association table to determine their Salesforce target. Contacts with no deal linkage are routed to a Salesforce Lead, preserving original details and activity. Contacts that have at least one associated deal are mapped to a Salesforce Contact and attached to the related Account. The split is performed at migration time using live association data, preventing duplicate records.

All REIPro company records are migrated to Salesforce as Account objects. Parent‑child hierarchies maintained in REIPro via the hs_parent_company_id field are translated to Account.ParentId links, preserving the original reporting structure. When multiple related companies exist, the migration collapses them into a single primary AccountId, ensuring each Contact or Opportunity references a valid account without circular dependencies. Unresolved parent references are flagged for manual review before final insertion.

REIPro deal records become Salesforce Opportunities, carrying the deal name, amount, and close date. Each REIPro stage maps to a Salesforce StageName value scoped by RecordTypeId, and probability and forecast categories are reapplied per Salesforce stage metadata. The original owner ID is resolved to a Salesforce OwnerId via email matching, with any unmapped stages flagged for review before the bulk insert.

REIPro's fixed 10-step pipeline is decomposed: pipeline name becomes a Salesforce Sales Process keyed by RecordTypeId, each step number maps to a stage name in Opportunity StageName pick-list per record type. Script and document attachments are exported as Notes linked to the Opportunity.

Because REIPro property records contain investor‑specific data that Salesforce does not store natively, a custom Property__c object is created with fields such as ARV__c, Purchase_Price__c, Rehab_Cost__c, Property_Status__c, Property_Type__c, Lot_Size__c, Square_Footage__c, and Year_Built__c. Each Property__c record links to the related Account via AccountId, allowing contacts and opportunities to reference the property. The admin must deploy the custom fields and set field‑level security before the bulk load.

REIPro's 12 lead source categories—such as Absentee Owner, Pre‑Foreclosure, MLS, BPO, County Records, Vacant Properties, Tax Lien, Estate, Divorce, Job Loss, Bankruptcy, and Trust—are mapped individually to Salesforce's LeadSource pick‑list. When a REIPro source does not correspond to an out‑of‑the‑box Salesforce value, a custom pick‑list entry is created on the Lead object before migration. This ensures that every historical lead source is preserved and visible on Lead page layouts.

REIPro activity history—calls, emails, and meeting logs—is migrated to Salesforce as Task and Event records. Call and email activities become Tasks, while meeting records become Events, each retaining the original timestamp, owner assignment, and parent‑record relationship (Contact, Account, or Property). Notes are transferred to Salesforce Notes, and any document attachments are uploaded to Salesforce Files and linked to the appropriate record. The mapping preserves the full engagement timeline without duplication.

Skip‑trace credit usage from REIPro—including count, date, and source—is logged in a custom Skip_Trace_Log__c object linked to the relevant Contact or Property__c record. Because Salesforce lacks a native credit‑balance concept, the existing REIPro balance is not transferred; each usage event is recorded as an audit entry, preserving the history and allowing teams to attach a new skip‑trace provider after migration.

REIPro direct-mail campaign records (mailer type, send date, response rate) merge into Salesforce Campaigns as campaign members linked to target Contacts or Property__c records. REIPro's Mail Engine settings and template configurations are exported as reference notes for rebuild in a Salesforce-compatible mail-merge tool.