Migrate from Rezora to Microsoft Dynamics 365 Sales

Rezora contacts with a confirmed property interest or transaction history map directly to Dynamics 365 Contact records. The contact's primary email, phone, name, and address fields translate 1:1. Rezora's agent-owner ID resolves to a Dynamics 365 OwnerId by email match — unmatched owners are flagged before the migration commits records.

Rezora contacts that have opened emails or clicked property links but have no closed transaction are candidates for the Dynamics 365 Lead entity. FlitStack routes contacts without a confirmed deal association into Lead, preserving all Rezora engagement metadata as custom fields. Leads can be qualified to Contact when a deal is confirmed — field mappings support that flow.

Rezora company records — typically the brokerage name and office-level details — map to Dynamics 365 Account. The Account record becomes the parent for all Agent-contact records that belong to that brokerage. Industry field uses Rezora's industry value mapped to the Dynamics 365 Industry pick-list value-by-value.

Rezora stores property listings with address, price, status, and listing-agent association. Dynamics 365 Sales has no native property-listing object. FlitStack creates a custom Dataverse table (Property_x0020_Listing) with fields for address, list price, status, and a lookup to the Account representing the brokerage. A second lookup links the listing to the listing agent's Contact record.

Rezora drip campaigns enroll contacts in multi-step nurturing sequences. Dynamics 365 Sales has no native drip-enrollment object. FlitStack preserves the enrollment state (e.g., Step 3 of 5, Paused, Completed) as a custom text field on Contact. Campaign membership in Dynamics is separate and requires rebuilding the trigger logic in Power Automate.

Rezora tracks opens, clicks, property views, and form submissions per contact. These aggregate into a composite engagement score. FlitStack migrates the score as a custom Number field on Contact and surfaces individual activity counts (email opens, link clicks) as additional custom Number fields for reporting continuity.

Rezora engagement events (email opened, link clicked, property viewed) become Dynamics 365 Task records with Subject describing the event, Description capturing the asset name, and custom fields for timestamp and campaign name. Original engagement timestamps are preserved; the Task's CreatedOn field records when the activity landed in Dynamics.

Rezora tracks where contacts originate (agent referral, website sign-up, open house, partner portal). These are mapped to the Dynamics 365 Lead Source pick-list values. Non-standard Rezora referral values that have no Dynamics equivalent are preserved as a custom pick-list field (Referral_x0020_Source__c) for reporting segmentation.

Rezora agents who send campaigns become Dynamics 365 Users with a matching email. Their agent profile (name, phone, title) also migrates as a Contact record so the agent appears in Dynamics reports. OwnerId on all Rezora-owned records resolves to the matched Dynamics User.

Rezora files attached to property listings (listing photos, disclosures, contracts) re-upload to SharePoint document libraries associated with the custom Property_x0020_Listing record. The regarding lookup connects each document to its parent listing. File size limits (default 50MB per file in Dataverse) are respected during re-upload.