Migrate from Property Shell to Salesforce Sales Cloud

Property Shell Contact maps directly to Salesforce Contact. Name, email, phone, address, and job title transfer as direct field copies. Salesforce requires an AccountId for most contacts — contacts without a primary company link get attached to a default placeholder Account.

Property Shell leads that are not yet qualified buyers route to Salesforce Lead. Contact records that have an active Deal attached or are flagged as 'Customer' type route to Salesforce Contact. The split rule is applied at migration time based on the contact's associated deal status in Property Shell.

Property Shell Company maps to Salesforce Account with a direct field copy for name, domain/website, industry, employee count, and annual revenue. Parent-company hierarchies in Property Shell map to Account.ParentId; the parent record must migrate first to avoid foreign-key errors. We verify parent-child relationships before migration to ensure proper hierarchy mapping.

Property Shell's native Property object has no Salesforce equivalent. We create a custom Property__c object with __c fields for property_name, status, price, property_type, address, and lot_details. The property is then linked to the related Opportunity via a lookup field Property__c on the Opportunity object.

Property Shell Deal maps to Salesforce Opportunity. Deal name becomes Opportunity.Name, amount becomes Amount, close date becomes CloseDate, and owner resolves by email match to Salesforce users. The deal's pipeline and stage map to a Salesforce Sales Process keyed by RecordType.

Property Shell pipeline stage values (e.g., 'Enquiry', 'Contracts Sent', 'Settled') map value-by-value to Salesforce StageName pick-list values. We apply probability percentages and forecast categories per stage during migration. Stage-entered timestamps are preserved in custom datetime fields for reporting continuity. The mapping includes all custom stages defined in Property Shell.

Property Shell contract documents download and re-upload as Salesforce Files (ContentVersion + ContentDocumentLink to the Opportunity). File size limits of 25MB per file apply. Original contract file names and upload dates are preserved as metadata on the Salesforce File record.

Property Shell notes map directly to Salesforce Notes (the newer Enhanced Note object). Original timestamps and note-body text transfer. Rich-text formatting in Property Shell notes is preserved as HTML content in Salesforce Note.Body. We ensure that all formatting, links, and embedded content are preserved during the migration.

Property Shell file attachments on records re-upload to Salesforce Files with ContentDocumentLink linking back to the parent Contact, Account, or Opportunity. The original file name and create date are preserved as Salesforce metadata on the ContentVersion record. We validate file types and sizes during the migration to ensure compatibility with Salesforce storage limits.

Property Shell custom fields on any object — strata details, floor plan codes, lot dimensions, release IDs — migrate as Salesforce custom fields (FieldName__c). The field type (text, picklist, number, date) is preserved. Lookup fields in Property Shell map to Salesforce lookup or master-detail relationship fields after the related object is migrated.

Property Shell owner IDs resolve to Salesforce users by email address match. Unmatched owners are flagged before migration — your team either creates Salesforce users for them first or assigns records to a fallback owner. No record lands in Salesforce without a resolved OwnerId.

Property Shell nurture journeys, lead funnels, and buyer lifecycle automations have no Salesforce Sales Cloud native equivalent. We export the automation definitions (trigger conditions, action steps, timing rules) as a structured rebuild reference document for your Salesforce admin to implement in Flow or a third-party marketing automation tool.