Migrate from Zillow Premier Agent to Microsoft Dynamics 365 Sales

Zillow Premier Agent stores individual contact records with name, email, phone, and address. Each maps directly to a Dynamics 365 Contact record. The primary AccountId lookup requires an Account record to exist first — we create a placeholder Account for contacts without a company association, then link them after Account creation.

Zillow contacts with a lead status of 'New' or 'Attempted contact' route to Dynamics 365 Lead records. Contacts that have progressed to 'Appointment set' or beyond are created as Dynamics 365 Contacts directly with the associated Account. The split rule is configurable — your team chooses which Zillow statuses map to Leads vs. Contacts.

Zillow Premier Agent stores a company or brokerage name as a text field on the contact record. We map this to the Dynamics 365 Account.Name field. If the Account does not exist in Dynamics 365, we create it first so the Contact.AccountId lookup resolves correctly during migration.

Zillow's lead-status pick-list values — New, Attempted contact, Spoke with customer, Appointment set, Contract sent, Active, Closed — map value-by-value to Dynamics 365 Lead Status pick-list entries. Your admin defines the target Lead Status values in Dynamics 365 before migration so we can apply the correct mapping table.

Zillow's internal contact statuses (New, Attempted contact, etc.) have no direct equivalent in Dynamics 365's standard Contact schema. We create a custom pick-list field (zillow_contact_status__c) on the Contact entity to preserve the original Zillow status for reporting continuity after migration.

Zillow Premier Agent tracks follow-up timestamps and message history as part of the contact record. We extract these as Dynamics 365 Tasks with a Subject of 'Zillow Follow-up' and the original Zillow follow-up timestamp preserved. Tasks are linked to the parent Contact record by ID.

Any text messages or notes stored within the Zillow contact record migrate as Dynamics 365 Notes attached to the Contact. Original message timestamps and sender information are preserved in the Note body. This preserves the buyer communication history for agents who used Zillow messages as their primary follow-up channel.

Zillow Premier Agent advertising spend is organized by ZIP code with monthly budgets. Since Dynamics 365 has no native advertising budget entity, we create a custom Account-level field (zillow_advertising_zip__c and zillow_advertising_budget__c) to preserve this reference data for billing reconciliation after migration.

Zillow Premier Agent assigns contacts to individual agent accounts. We resolve each agent's Zillow ID to a Dynamics 365 SystemUser by email match. Unmatched agents are flagged before migration — your team either creates their Dynamics 365 user accounts first or assigns their records to a fallback owner for post-migration redistribution.

Zillow Premier Agent does not store file attachments natively. Any documents shared through Zillow messages are preserved by re-uploading to Dynamics 365's SharePoint integration or as Notes attachments on the Contact record. We provide a checklist of files to re-upload based on the contact list.

Dynamics 365 sets the CreatedOn timestamp at migration load time, which does not reflect when the contact was originally captured in Zillow. To preserve the authentic lead creation date, we create a custom datetime attribute (zillow_original_createdate__c) on the Contact entity. This field receives the original Zillow created_date value so reporting can display the true contact history timeline from the point of first capture rather than from the migration event.

Dynamics 365 Lead and Contact records do not natively track the originating platform. We add a custom text field (zillow_source__c) to every migrated record with a value of 'Zillow Premier Agent' so you can filter reports by the original lead source without relying on manual tagging.