Migrate from Right On Interactive to Microsoft Dynamics 365 Sales

Contacts migrate 1:1 to Microsoft Dataverse Contact records. The lifecycle stage assignment from Right On Interactive maps to a custom field (e.g., roi_lifecycle_stage__c) since Microsoft Dynamics 365 Sales has no native lifecycle stage concept. We capture the full stage label set during discovery (stage names like Prospect, MQL, Evangelist vary by account configuration) and create an explicit mapping table before any data is written. All standard contact fields (name, email, phone, address, company association) migrate directly.

Lifecycle stage names are account-configured custom fields in Right On Interactive, not fixed platform schema values. Each stage label maps to a custom picklist or text field on the Dataverse Contact record (roi_lifecycle_stage__c). We preserve the original stage label set during discovery so that stage names carry over exactly. Microsoft Dynamics 365 Sales Process stages are separate from lifecycle stage and track deal progress, not contact journey position.

Right On Interactive's 3D scoring breaks engagement into behavioral, demographic, and firmographic sub-scores. We export all three sub-scores as individual custom number fields on Contact (roi_score_behavioral__c, roi_score_demographic__c, roi_score_firmographic__c). The aggregate score lands in the native score field or a custom aggregate field. This preserves analytical value while maintaining compatibility with Dynamics 365 segmentation tools.

Account records migrate 1:1 to Microsoft Dataverse Account. Firmographic data used in 3D scoring (industry, employee count, revenue range) migrates as standard Account fields or custom fields. Account is created before Contact import so the AccountId lookup is satisfied at the moment of Contact insert. The dedupe key is the account name or domain where available.

Opportunities migrate to Microsoft Dataverse Opportunity. The pipeline stage assignment maps to a Microsoft Dynamics 365 Sales Process and Record Type. Owner resolves by email match to the destination User table. Any Opportunity with an unresolved OwnerId goes to a reconciliation queue for the customer's admin to provision before import resumes. Historical closed-won and closed-lost dates preserve the original values.

Engagement events including email opens, link clicks, form submissions, and social interactions migrate as Dataverse Activity records (Task, Email, and PhoneCall entities) linked to Contact. Each activity record preserves the original timestamp to maintain the chronological timeline. Migration uses the Dataverse API with batch chunking (maximum 1,000 records per request for Microsoft Dynamics 365 Sales Professional, 100,000 calls per 24 hours on Enterprise) and exponential backoff on throttling. Large engagement histories require careful batch sizing and retry logic.

Campaign records migrate to Dataverse Campaign. Campaign member associations migrate as CampaignResponse or CampaignMember records linked to the associated Contact. Active campaign execution state requires reactivation on Dynamics 365 post-migration. Campaign budgets, program assignments, and multi-channel metadata transfer as custom fields on the Campaign record.

Lifecycle-based email automations cannot export as executable rules. We produce a detailed migration playbook documenting each automation's trigger conditions, filter logic, action sequence, and delay rules. The customer's marketing team rebuilds equivalents in Power Automate (triggered by Dataverse record changes) or Copilot Studio agents. Running both systems in parallel during a validation window is recommended before cutover.