Migrate from Sierra Interactive to Salesforce Sales Cloud

Sierra Contact records map directly to Salesforce Contact records. The primary company association becomes AccountId — Sierra contacts without a company link attach to a designated 'Unassigned Account' placeholder record. Secondary company associations require Account Contact Relationships created after primary Contact records are inserted.

Sierra Lead records (contacts with lifecycle_stage = 'Lead') map to Salesforce Lead records. Lead Status maps through a value-mapping table (New, Working, Nurturing, Unqualified) that your admin approves. Source field and rating information carries over as custom or standard fields on the Salesforce Lead object.

Sierra Company records map to Salesforce Account records with Name, Website, Phone, Industry, and billing address fields transferred directly. Parent-company hierarchies in Sierra map to the Salesforce Parent Account field. Offices in Sierra with broker-level records can map to a separate Salesforce custom object or to Account records flagged with a Type field.

Sierra Listings translate to Salesforce Opportunities because Salesforce has no native property object. The Listing object fields (address, price, status, property type, MLS number) map to a combination of Opportunity standard fields and custom fields (Listing_Status__c, Property_Type__c, MLS_Number__c). Each listing's primary agent becomes the Opportunity OwnerId.

Closed transactions in Sierra (status = Sold or Closed) map to Opportunity records with Amount populated from the sale price and StageName set to 'Closed Won'. Transaction details (commission, closing date, buyer's agent, seller's agent) store as custom fields on the Opportunity or on a linked Transaction custom object if the relationship is many-to-one.

Sierra Action Plans do not migrate to Salesforce. FlitStack exports Action Plan templates as JSON files containing step definitions, trigger conditions, and timing rules so your Salesforce admin can rebuild equivalent sequences in Flow, Salesforce Sales Engagement, or a third-party tool. The export is delivered before the data migration runs so rebuild work can start in parallel.

Sierra Tasks assigned to contacts or listings map to Salesforce Tasks with Subject, Status, Priority, ActivityDate, and WhoId/WhatId preserved. Each task's WhoId maps to the Salesforce Contact or Lead record, while WhatId links to the related Opportunity for listing-specific tasks. Completed tasks carry their original completion date in the LastModifiedDate field. Uncompleted tasks maintain their original due dates and owner assignments, ensuring continuity of follow-up activities across the platform transition.

Sierra Notes migrate to Salesforce Notes (not the legacy Note object). The Title, Body, ParentId, and owner fields transfer directly. Rich-text formatting in Sierra notes is preserved as HTML in the Salesforce Note Body field where the target org supports rich-text notes.

Sierra Saved Searches store buyer criteria (price range, location, bedrooms) as structured records. Salesforce has no native equivalent. FlitStack migrates Saved Search records to a custom Salesforce object (Saved_Search__c) with criteria fields mapped to custom text or pick-list fields. Saved Search ownership resolves by email match to Salesforce users.

Sierra User records resolve to Salesforce User accounts by email address match. Active Sierra agents must have Salesforce User licenses provisioned before migration so their records can assign OwnerId correctly. Inactive or archived Sierra users are flagged; their records assign to a designated fallback owner in Salesforce or remain unassigned pending admin review.

Sierra Office records representing brokerage locations map to Salesforce Account records with Type = 'Brokerage'. Office-level contact associations (agents assigned to an office) migrate as Account Team Members or as Role-based sharing rules depending on the target org's sharing model. Office-level settings and preferences do not migrate as they are Sierra configuration, not data.

Files attached to Sierra Contacts, Listings, or Transactions download and re-upload to Salesforce Files (ContentVersion/ContentDocument). File size up to 25MB per file migrates directly; files exceeding Salesforce's limit are flagged for manual handling. Inline images in notes extract and rehost as Salesforce Files linked to the parent record.