Migrate from Real Estate 7 to Salesforce Sales Cloud

Real Estate 7 stores all people records in a single contacts table. FlitStack AI splits them: active client records (status = Customer or Client) migrate to Salesforce Contact; early-stage prospects (status = Lead or Inquiry) migrate to Salesforce Lead. The split preserves the original status value in a custom field so you can audit the original classification after migration.

Real Estate 7 stores the brokerage or client company name as a contact property. Each unique company name becomes a Salesforce Account record. Contacts link to Accounts via the AccountId lookup field. If a contact has no associated company, we create a default 'Individual Client' Account to satisfy Salesforce's required lookup on Contact.

Real Estate 7 stores property listings as a WordPress custom post type with plugin-specific meta fields for price, type, status, address, bedrooms, and bathrooms. Salesforce has no standard property object. FlitStack AI creates a Property__c custom object with fields for every listing attribute — Listing_Price__c (currency), Property_Type__c (pick-list), Listing_Status__c (pick-list), Address__c (compound), Beds__c (number), Baths__c (number), SqFt__c (number), MLS_Number__c (text). The WordPress post ID is stored as Source_System_ID__c for traceability.

Each Real Estate 7 transaction record maps to one Salesforce Opportunity. The Opportunity Name concatenates the property address and client name for readability. The Amount field carries the offer price or sale price. CloseDate maps from the transaction close date in the source. OwnerId is resolved by email match against Salesforce users — unmatched agents are flagged for your admin to assign before the migration runs.

Real Estate 7 transaction statuses (Inquiry, Showing, Offer Made, Under Contract, Closed, Lost) do not exist as native Opportunity Stage values. We create a custom Listing_Status__c pick-list field on Opportunity and map each source value to the corresponding destination pick-list value. Your Salesforce admin pre-creates these pick-list values before data loads — we deliver the mapping sheet as part of the migration plan.

The Real Estate 7 transaction-property relationship is a foreign key linking the transaction to a WordPress post ID. We translate this to an Opportunity.Property__c lookup pointing to the migrated Property__c record. This preserves the link between the deal and the listing so agents can navigate from the Opportunity directly to the Property__c record in Salesforce.

Real Estate 7 activity records — showing reminders, call logs, follow-up tasks, and meeting notes — migrate as Salesforce Task records for actions and Event records for calendar-bound activities. Original created dates, due dates, and assigned owners are preserved. The Task WhatId links to the parent Opportunity or Property__c record using the source relationship metadata.

WordPress notes and comment records attached to a contact, property, or transaction migrate as Salesforce Notes (Body field, parented to the target record). File attachments — listing photos, contracts, disclosures — are downloaded from the WordPress media library and re-uploaded as Salesforce Files (ContentVersion + ContentDocumentLink) attached to the parent Property__c or Opportunity record.

Real Estate 7 agent and broker user accounts exist as WordPress users. We match them to Salesforce users by email address. For agents with no Salesforce user account, we flag their records before migration so your admin can either create the Salesforce user or assign those records to a fallback owner. No record lands without a resolved OwnerId.

Real Estate 7 workflow rules, automated follow-up sequences, and email drip campaigns stored in WordPress option tables have no Salesforce equivalent and cannot be migrated directly. We export the workflow definitions as a structured JSON document that your Salesforce admin can use as a reference spec when rebuilding equivalent Flows. Reports and dashboards similarly require rebuild in Salesforce Reports & Dashboards — the underlying Opportunity and Property__c data migrates, but the report layouts do not.

Real Estate 7 stores any plugin-added custom fields in WordPress post meta. We inventory all custom meta keys present in the source export, create matching custom fields in Salesforce on the appropriate object (using the __c suffix convention), and map the values during load. Field types are inferred from the source data format — text strings become Text fields, numeric values become Number or Currency, and date values become Date fields.

Every migrated record — Contact, Lead, Property__c, Opportunity, Task — receives a Source_System_ID__c text field populated with the original Real Estate 7 WordPress ID. This field serves two purposes: it enables delta-run de-duplication (FlitStack detects records already migrated by matching this ID) and it provides an audit trail linking each Salesforce record back to its source.