Migrate from Zillow Premier Agent to Salesforce Sales Cloud

Zillow does not expose a bulk historical data export API

Zillow's Tech Connect and Partner APIs are designed for real-time, inbound lead push from Zillow to a CRM — not for bulk extraction of existing contact records. Agents who have accumulated contacts over years in Zillow Premier Agent cannot pull a complete export through a documented endpoint. FlitStack works around this by authenticating as the Zillow Partner, querying the Zillow API for each contact record individually via paginated API calls, and reconstructing the full contact dataset before mapping to Salesforce. This process is scope-intensive and requires read access to the Zillow account being migrated. If the Zillow API returns rate-limited responses or incomplete records, the migration plan documents exactly which fields are available and which require manual re-entry. This limitation is disclosed upfront during discovery.

Zillow contact statuses do not map 1:1 to Salesforce lead or opportunity stages

Zillow Premier Agent uses a linear, flat contact-status model: New → Attempted Contact → Spoke with Customer → Appointment Set → Showing Homes → Listing Agreement → Active Listing → Submitting Offers → Under Contract → Closed → Nurture → Trash. Salesforce separates prospects (Lead), clients (Contact + Account), and deals (Opportunity), with stage values scoped per Sales Process and Record Type. There is no automatic 1:1 mapping — 'Showing Homes' in Zillow has no native Salesforce equivalent and requires a custom Opportunity record type and stage value configured by your admin before the migration runs. We deliver the stage-mapping plan before data lands so the Salesforce schema is ready.

My Agent relationships require manual rebuild in Salesforce as Account Contact Relations

Zillow's My Agent feature assigns a specific buyer contact to a specific Premier Agent across all Zillow listings the buyer browses. Salesforce has Opportunity Contact Role for contact-to-opportunity buyer roles, but no general-purpose 'agent assignment' object at the contact level. We preserve the My Agent relationship data (agent email, listing address, relationship date) as a custom Zillow_My_Agent_Role__c field on the Lead for reference. Rebuilding the actual relationship — for example, creating Account Contact Relations or custom junction objects that link the buyer Contact to the agent Contact in Salesforce — requires your admin to define the target schema and is not automated by the migration.

Zillow buyer browsing insight data is read-only reference information, not CRM data

Zillow's My Agent feature surfaces a buyer's Zillow browsing activity — which listings they viewed, search criteria, saved homes — as a dashboard inside Zillow Premier Agent. This data is displayed by Zillow's front end but is not stored as a structured field in the contact record available via API. We capture whatever URL or identifier Zillow exposes for the buyer's insight panel as a Zillow_Buyer_Insight_URL__c custom URL field on the Lead. The actual browsing history, search criteria, and listing interactions do not transfer — agents lose this behavioral context unless they manually capture it before migration.

Zillow Flex fee and billing data cannot migrate and must be rebuilt outside Salesforce

Zillow Flex is a transaction-based referral model where the agent pays Zillow a percentage (up to 40% per the 2025 litigation settlements) of their commission upon closing. This is a financial obligation and referral tracking construct that has no equivalent in Salesforce's CRM model. We do not migrate Flex fee schedules, referral attribution, or billing history. If your brokerage tracks referral fees paid to Zillow, that data must be maintained in a separate financial system or spreadsheet. FlitStack does not migrate any billing, payment, or commission-sharing data.