Migrate from Zavvie Power Buyer to Microsoft Dynamics 365 Sales

Zavvie partner brokerages map directly to Dynamics 365 Accounts. We map the brokerage legal name, primary contact email, office address, and license number. Brokerages with multiple offices in Zavvie may have separate partner records that collapse into one Account with child Account records for each office location.

Individual agents associated with a brokerage partner map to Dynamics 365 Contacts. Each Contact links to the parent Account (brokerage) via the AccountId lookup. Agent role in Zavvie (listing agent, buyer's agent, transaction coordinator) maps to a custom Contact field, since Dynamics 365 Sales does not have a native agent-role concept.

Each active or historical property listing in Zavvie becomes a Dynamics 365 Opportunity. The listing address maps to the Opportunity address fields or to custom address fields on a custom Listing__c table. Listing status (Active, Under Contract, Closed) maps to Opportunity StageName values with a custom status field capturing the full Zavvie listing lifecycle.

The home seller (Zavvie client) maps to a Dynamics 365 Contact record. The seller's name, phone, email, and move-in/move-out timeline map to standard Contact fields. For couples or co-owners listed in Zavvie, each individual gets a separate Contact record linked to the same Opportunity.

Individual cash offers from iBuyers and investors have no native equivalent in Dynamics 365 Sales Opportunity records. We create a custom CashOffer__c Dataverse table linked to the parent Opportunity (Listing) via a lookup. The table captures offer amount, buyer name, offer date, acceptance status, and applicable fees. This preserves the granular offer-level detail that Zavvie surfaces in its offer reports.

Buy-before-you-sell bridge transactions in Zavvie represent a distinct product type with its own fee schedule, lender terms, and close timeline. We map these to a BridgeTransaction__c custom table linked to the Opportunity, capturing bridge amount, origination date, bridge fee, and final sale close date. Standard Opportunity fields (Amount, CloseDate) capture the final transaction close for reporting.

Zavvie offer reports are PDF or CSV exports generated per listing showing all offers side-by-side. We export these as Attachments on the corresponding Dynamics 365 Opportunity. This preserves the comparative offer view for audit and compliance purposes without requiring a custom report rebuild in Dynamics 365.

iBuyer entities and investor firms that submit offers in Zavvie map to Dynamics 365 Account records (type = Investor). These Accounts appear on the related CashOffer__c records. The Account captures the iBuyer's legal name, market, and offer terms that repeat across multiple listings.

Closed Zavvie transactions map to Dynamics 365 Opportunities with StageName = 'Closed Won'. The close date, final sale price, and agent commissions from Zavvie migrate to Opportunity fields or custom fields on the Opportunity for historical reporting continuity. Original Zavvie transaction IDs are preserved in Source_System_ID__c.

Zavvie logs agent activities such as listing submissions, offer reviews, and client communications. These migrate as Dynamics 365 Tasks (for dated activities) or Notes (for free-text logs) attached to the relevant Opportunity or Contact. Original timestamps and agent ownership are preserved.

Zavvie tracks fee schedules per transaction including iBuyer fees (0–3% of offer amount) and bridge product fees. These map to a TransactionFee__c custom table linked to the Opportunity, capturing fee type, amount, calculation basis, and payment status. Standard Dynamics 365 Finance or Business Central integration can replace this post-migration.

Zavvie partner-specific settings such as white-label branding, offer routing rules, and integration credentials do not migrate. These include custom UI labels, automation triggers, and API tokens that are stored in Zavvie's configuration store. After migration, administrators must manually recreate these settings in Dynamics 365 via the Power Platform admin center, reconfigure security roles, and repoint integration endpoints using Azure Active Directory app registrations before go‑live.