Migrate from Rizer to Microsoft Dynamics 365 Sales

Rizer Contacts with referral attribution and lifecycle stage tags map to Dynamics 365 Lead or Contact based on a qualification rule defined during scoping. Unqualified influencer and creator contacts (top-of-funnel) map to Lead; Contacts with a confirmed deal or project association map to Contact attached to an Account. We preserve the original referral source, attribution window, and lifecycle stage as custom fields on both the Lead and Contact for post-migration reporting. The split rule is applied as a transform step before any record is written to Dynamics.

Rizer Companies linked to Contacts map to Dynamics 365 Account. The Company name becomes the Account Name field and the domain becomes the Website. We resolve the Contact-to-Account lookup relationship during the Contact insert phase by ensuring Account records are created before Contact records. If Rizer Companies have no Contacts attached, they are imported as standalone Accounts with a flag indicating no linked contacts.

Rizer Deals map to Dynamics 365 Opportunity. The deal stage maps to StageName, the pipeline assignment maps to a Record Type and Sales Process configured in Dynamics before migration, and the deal amount maps to Amount. Closed-won and closed-lost reasons from Rizer custom properties become LossReason and Win Reason fields on the Opportunity. We resolve the AccountId and OwnerId (via email-matched User lookup) before Opportunity insert to satisfy the required relationships.

Rizer's built-in referral attribution (source field, attribution window, conversion event) has no native Dynamics 365 equivalent. We create custom fields on the Contact and Lead objects (referral_source__c, attribution_window__c, conversion_date__c) and write the referral values as text or date fields during the Contact/Lead insert. The referral attribution report is preserved for the customer's marketing team to continue attribution analysis in Microsoft Dynamics 365 Sales using those custom fields.

Rizer workflow sequences (property-triggered email sequences attached to lifecycle stages) are not migrated as code because the Dynamics 365 equivalent (Salesforce-style Flow or Sales Engagement) requires a different trigger model. We extract every active workflow with its name, trigger conditions, delay rules, and action sequence and deliver this as a written inventory document. The customer's Dynamics 365 admin or a Microsoft partner rebuilds the automations post-migration.

Rize time-tracking Clients (from the separate rize.io product) are top-level entities that map to Dynamics 365 Account. If the Client has an associated contact person in Rize, that person migrates as a Contact linked to the Account. The Rize Client and Rizer Social Contact export are separate API passes with separate credentials, and the migration plan handles them as independent scopes with a reconciliation step to match any Rize Client to an existing Rizer Social Company record.

Rize Projects belong to Clients and contain Tasks. If the customer's Dynamics 365 environment includes Project Operations or Business Central, Projects map to msdyn_project (Project). Otherwise, Projects map to a custom Project object or to Opportunity records with a project_type__c custom field flagging them as project records rather than sales pipeline deals. We determine the target structure during scoping based on the customer's licensed Dynamics modules.

Rize Tasks nested under Projects map to Dynamics 365 Task. Rize subtasks (represented as a boolean or count field in Rizer rather than a discrete object) are expanded into separate Task records in Dynamics with a parent_task__c lookup where Dynamics supports subtask hierarchies. Task status, due date, and assignment migrate directly.

Rizer and Rize Team Members map to Dynamics 365 User records by email match. We extract all distinct owner and assignee references from Contacts, Deals, and Projects and match them against the destination User table. Any Team Member without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before the record import resumes.

Rizer tags applied to Contacts and Workflows are flat string lists. We inspect the tag taxonomy and map tags to either Dynamics 365 multi-select picklist fields (for contact classification) or Topic/Tags (for content association). The customer chooses the tag strategy during scoping based on whether tags are used primarily for sales segmentation or for content attribution.