Migrate from Referrizer to Microsoft Dynamics 365 Sales

Referrizer Contacts map directly to Dynamics 365 Contact records. We preserve firstname, lastname, email, phone, address, custom fields, labels, and visit history during extraction. For contacts that represent businesses rather than individuals, we may create a parent Account first and link the Contact to it. Multi-select label assignments from Referrizer migrate to a custom multi-select picklist field on Contact or to TopicAssignment records depending on the customer's segmentation preference. Location association is preserved as a custom field if the destination org does not use the Sites entity.

Referrizer custom fields are key-value properties on the Contact record. We enumerate all custom field names and data types via the GET /contacts endpoint during scoping, then provision matching custom fields on the Dynamics 365 Contact entity before migration. Number fields, date fields, and text fields map directly. Multi-select or checkbox custom fields map to Dynamics multi-select picklist or boolean fields. Any custom field that has no equivalent Dynamics type is documented and placed in a custom field namespace on Contact.

Referrizer Pipeline stages map to Dynamics 365 Lead Status values or to Opportunity stages depending on the customer's sales process. If Referrizer contacts include a lead qualification status, we map that to the Dynamics Lead entity with a custom field capturing the original Referrizer pipeline stage name. Lead records are created before Contact records to allow WhoId resolution during activity migration.

Referrizer Deals map to Dynamics 365 Opportunity records. The deal amount, close date, stage name, and owner map to estimatedvalue, estimatedclosedate, stageName, and ownerid respectively. If Referrizer uses multiple pipelines, we create corresponding Opportunity Record Types and Sales Processes in Dynamics 365 before migration. The Deal-to-Opportunity association with the parent Contact and any linked Company is resolved via WhoId and WhatId lookups during the load phase.

Referrizer Regular and Automated campaigns map to Dynamics 365 Campaign records. Campaign type, status, scheduled dates, and target audience (contact list) migrate. We do not migrate campaign HTML content or templates; these are documented separately for the customer's marketing team to rebuild in Dynamics 365 Marketing or a comparable email platform. Campaign member responses (sent, delivered, opened) migrate as CampaignMember records with Status values mapped from Referrizer engagement metrics.

Referrizer Offers and referral relationship data do not have a native Dynamics 365 equivalent. We export offer codes, reward structures, and referral link associations as related records. Depending on the customer's data model, we create a custom ReferralOffer entity in Dataverse with a lookup to Contact, or we store the referral relationship as structured notes on the Contact record with a custom field for the referral type. The customer chooses the approach during scoping.

Referrizer loyalty points are stored as numeric custom fields on contact records rather than as a distinct object. We separate these fields from standard contact properties during transformation and remap them to a custom number field on the Dynamics 365 Contact entity named loyalty_points_balance__c. The customer may alternatively choose to integrate Dynamics 365 Customer Insights - Journeys for a native loyalty program; we document the migration approach and flag that any loyalty tier or points redemption rules require rebuild in the destination system.

Referrizer review request history (which contacts received requests, when, and to which platform) is stored as activity data on the contact record. We export this as a list of activity entries and load into a custom ReviewRequest entity in Dataverse linked to the Contact, or as structured notes with a custom field for the review platform (Google, Yelp, Facebook). We do not migrate actual reviews or ratings as these reside on third-party platforms and are not stored in Referrizer.

Referrizer contact activity feed events including campaign opens, link clicks, and UTM tracking data migrate as Note records on the Contact in Dynamics 365. Each activity entry is stored as a Note with a custom field capturing the activity type, timestamp, and source (campaign name). We do not migrate Smart Inbox conversational threads as no public API endpoint exposes this data. The Note-based approach preserves a historical record for audit purposes without requiring the activity timeline to be reconstructed from incomplete source data.

Referrizer team member records (name, email, role) migrate as a lookup table against the Dynamics 365 destination org's User records. We match by email address. Any Referrizer owner without a matching Dynamics User is placed in a reconciliation queue for the customer's admin to provision before record import resumes, as OwnerId references are required on most standard object loads.