Migrate from PropertySimple to Salesforce Sales Cloud

PropertySimple contacts map directly to Salesforce Contacts. Salesforce requires an AccountId (lookup to Account) for most contacts — PropertySimple contacts without a primary company association are attached to a default 'Unassigned Accounts' placeholder record, and the original company association is preserved in a custom field for reconciliation.

PropertySimple companies map to Salesforce Accounts. Parent‑child brokerage hierarchies are preserved using the Parent Account field. Multi‑company contacts (N:N associations) collapse to one primary AccountId with the remaining affiliations stored as Account Contact Relationships. Company type, billing address, and phone map to the corresponding standard fields; any duplicate companies are merged using email domain deduplication before insertion.

PropertySimple deals map to Salesforce Opportunities. Each deal’s amount, close date, and owner are transferred to the corresponding Opportunity fields. Deal pipeline stages map to Salesforce StageName values through a custom mapping table tied to Record Types; this ensures that probability, forecast category, and stage‑specific pick‑list values are applied correctly. Listing associations are preserved via a custom Listing_Id__c field that links the opportunity to the Listing__c record.

PropertySimple pipelines become Salesforce Sales Processes tied to Record Types. Each pipeline in PropertySimple requires its own Record Type, isolating StageName pick‑list values, probability weights, and forecast categories per business unit. The migration creates the Sales Process records, assigns the correct Record Type to each Opportunity, and updates the opportunity metadata so reporting and forecasting match the original pipeline structure.

PropertySimple listings have no direct Salesforce equivalent, so we create a Listing__c custom object. The object holds MLS number, property address, listing price, status, and listing date with the __c suffix. Each listing links to the seller Account via Seller_Account__c and to the agent Contact via Agent_Contact__c, with a lookup field tying it to the related Opportunity. Listing status values map to a custom pick‑list on Listing__c for consistent reporting.

PropertySimple agent records resolve by email match against Salesforce Users. Unmatched agents are flagged before migration — the team either provisions Salesforce user accounts first or assigns their records to a fallback owner. Active/inactive status on the PropertySimple agent record maps to Salesforce User.isActive.

PropertySimple engagement records (calls, emails, meetings) map to Salesforce Tasks (for calls and emails) and Events (for meetings). Original timestamps, owners (resolved by email), and parent-record links to Contact or Opportunity are preserved. Marketing touchpoints (social engagement) migrate as Notes with a custom engagement-type field.

PropertySimple file attachments—listing photos, contracts, and other documents—are re‑uploaded as Salesforce Files (ContentDocument/ContentVersion). Each file is linked to its parent record (Account, Contact, or Listing__c) via ContentDocumentLink. The default 25 MB per‑file limit applies; larger files are flagged for manual upload or chunking. Inline images embedded in notes are extracted, re‑hosted as separate Files, and re‑attached, preserving original timestamps and owner information.

PropertySimple custom properties on any object require Salesforce custom fields. Fields receive the __c suffix, and data type is mapped (text → Text, number → Number, picklist → Picklist). Multi‑select pick‑lists in PropertySimple map to Salesforce multi‑select pick‑lists with value‑by‑value validation.

PropertySimple's ZIP‑code exclusivity and territory marketing data has no native Salesforce equivalent. We preserve ZIP‑code assignments as custom fields on Account (for territory) and Campaign (for marketing campaigns), allowing Salesforce admins to build territory reports and campaign attribution from the migrated data.

PropertySimple social posting configurations and automation sequences do not migrate. These must be rebuilt in Salesforce using Flow, or teams acquire a social media automation AppExchange app (e.g., Social Studio). FlitStack exports the configuration as a reference JSON for the rebuild team.

PropertySimple incoming inquiries that have not been converted to contacts map to Salesforce Leads. Lead source, inquiry date, and property interest fields migrate as custom fields on Lead. Once the inquiry converts, the Salesforce Lead converts to Contact + Opportunity with the Listing__c association preserved.