Migrate from Zavvie Power Buyer to Salesforce Sales Cloud

Direct map. Each Zavvie Buyer Profile becomes a Salesforce Contact. Salesforce requires an AccountId on most Contact records — if the Buyer has no associated Property record, we attach to a default 'Unassigned Account' or create one per buyer. The migration preserves original timestamps, owner assignments, and custom properties so post-migration Salesforce reports reflect the full buyer profile lifecycle.

Direct map. Each Property Listing becomes a Salesforce Account. Zavvie's property address maps to Account.BillingAddress. If a property has no street address (e.g., MLS-only records), it maps to Account.ShippingAddress or a custom address field per your naming convention. All original timestamps, listing agents, and source identifiers are preserved in the migrated Account record for reporting continuity.

Cash Offer maps to Salesforce Opportunity. Zavvie fields like Offer_Amount__c, Offer_Status__c, and Expiration_Date__c become custom Opportunity fields (Power_Buyer_Source__c = 'Zavvie' for traceability). Opportunity Type is set to 'Power Buyer Cash Offer' via value mapping. Each migrated Opportunity retains its original Zavvie creation date, owner, and stage-entry history for full audit continuity.

Zavvie allows one buyer to make multiple offers across multiple properties, and one property to receive offers from multiple buyers — a many-to-many relationship. Salesforce handles this via Account Contact Relations (for the buyer-as-contact / property-as-account link) plus a custom Power_Buyer_Offer__c junction object for Power-Buyer-specific attributes.

Zavvie Power Buyer stages (Pre-Approval, Offer Made, Offer Accepted, Under Contract, Closed, Post-Closing) have no Salesforce standard equivalent. We create a custom pick-list field Deal_Stage__c on Opportunity and map values one-by-one. Stage-entry timestamps map to custom datetime fields for audit continuity.

Zavvie custom properties on Buyer Profiles (e.g., Buyer_Tier__c, Preferred_Lender__c, Down_Payment_Pct__c) become Salesforce custom fields on Contact. Each field is created in Salesforce Setup before migration loads. Field type (pick-list, currency, percent) is inferred from the source data values, and the original field label and help text from Zavvie are preserved in the Salesforce field description for admin reference.

Zavvie custom properties on Property Listings (e.g., Listing_Source__c, Days_On_Market__c, MLS_Number__c) become Salesforce custom fields on Account. All __c fields require pre-creation in Salesforce Setup before the data migration runs. Field types are inferred from the source data values to ensure data integrity during the load.

Zavvie custom properties on Cash Offers (e.g., Offer_Type__c, Inspection_Waived__c, Seller_Concession__c) become Salesforce custom fields on Opportunity. We preserve the original field label and help text from Zavvie in the Salesforce field description for admin reference. Each custom field is pre-created in Salesforce Setup before migration loads to ensure schema consistency.

Buyer-facing activities logged in Zavvie (call logs, email threads, meeting notes) migrate as Salesforce Tasks (for calls and emails) and Notes (for free-text notes). Original timestamps, owners, and parent-record links (ContactId, OpportunityId) are preserved to maintain full activity history continuity in Salesforce.

Zavvie users and agents resolve to Salesforce Users by email address match. Unmatched users are flagged before migration — your team either provisions Salesforce accounts first or assigns records to a fallback owner. No Opportunity or Contact lands in Salesforce without an OwnerId.

Files attached to Buyer Profiles or Property Listings in Zavvie are downloaded and re-uploaded as Salesforce Files (ContentDocument / ContentVersion). Each file is linked to the corresponding Contact, Account, or Opportunity record. Original file names and upload timestamps are preserved in the ContentVersion metadata for full document traceability after migration.