Migrate from Zurple to Salesforce Sales Cloud

Zurple contacts do not require a parent company, but Salesforce requires AccountId on Contact for most standard fields. We create Account records from Zurple company data (or from contact.company if no company record exists) and link the Contact to it. Primary company assignment uses the most-recently-modified rule or your specified preference.

Zurple contacts at early stages (New Lead, Attempting Contact) route to Salesforce Lead. Contacts that have reached Showing Scheduled or Offer Made stage route to Salesforce Contact. The split is configurable based on your Zurple stage values and your Salesforce lead-conversion threshold.

Zurple company records map directly to Salesforce Account. Company name maps to Account.Name, website to Account.Website, phone to Account.Phone. Industry values require value-mapping against Salesforce's standard Industry pick-list since Zurple uses a real estate-specific industry taxonomy. Any custom fields on the Zurple Company object become custom fields on the Account using the __c suffix convention.

Zurple's lead stages (New Lead, Attempting Contact, Showing Scheduled, Offer Made, Client) map value-by-value to Salesforce Lead Status. If you use the legacy deal object, those stages map to Opportunity StageName values scoped by record type. We preserve stage-entry timestamps as custom datetime fields for reporting continuity.

Zurple stores saved search criteria, preferred property types, price range, and bedroom/bathroom counts as properties on the contact. These require custom fields on Contact (Property_Type_Interest__c, Price_Range_Min__c, Price_Range_Max__c, Bedroom_Count__c, Bathroom_Count__c, Saved_Search_JSON__c). We create these in your Salesforce org before data loads.

Zurple conversation threads (automated nurture emails and lead responses) migrate as Salesforce Tasks with Subject='Zurple Automated Nurture' and Type='Email'. Original send timestamps, open events, and click events are preserved as custom fields (Last_Nurture_Open__c, Last_Nurture_Click__c). This preserves the engagement history without rebuilding the sequence logic.

If your Zurple account uses a separate deals object (transaction records linked to contacts), those migrate as Salesforce Opportunities. Deal name becomes Opportunity.Name, deal amount becomes Opportunity.Amount, close date becomes Opportunity.CloseDate. The parent contact links via OpportunityContactRole. Deal custom fields map to Opportunity custom fields using the __c suffix convention, and stage values map to Opportunity.StageName pick-list values scoped by record type.

Zurple owner IDs resolve to Salesforce users by email match. Unmatched owners are flagged before migration—you either invite them to Salesforce first or reassign their records to a fallback user. Owner resolution happens during the pre-migration audit phase, and the resolution report is delivered to your admin for action before the migration run begins. No record lands in Salesforce without a resolved OwnerId.

Zurple file attachments on contacts or deals re-upload to Salesforce Files (ContentDocument/ContentVersion model). File size limits apply—Salesforce default is 25MB per file. Inline images in Zurple notes are downloaded, rehosted as Salesforce Files, and linked to the parent record. Files are associated using the ContentDocumentLink object, and the original Zurple file name is preserved in the ContentVersion.Title field for traceability.

Zurple's behavior-triggered email sequences cannot be exported in a format that auto-loads to Salesforce Flow. We export your sequence definitions (trigger conditions, email content references, timing rules) as a structured document your Salesforce admin uses to rebuild in Flow. The rebuild is not included in the data migration scope.