Migrate from Rule to Microsoft Dynamics 365 Sales

Rule Contacts map directly to Microsoft Dynamics 365 Sales Contact records. Standard fields (firstname, lastname, emailaddress1, telephone1) migrate 1:1. Behavioral attributes and channel preferences from Rule's custom properties map to custom fields on Contact. The Account Lookup (parentcustomerid) must resolve before Contact import; we extract the company name from Rule's company association, create or match an Account record first, then link Contact to Account during import.

Rule Companies export as Account records in Microsoft Dynamics 365 Sales . The company name maps to Account.Name, domain to Account.Website, and industry or segment to Account.Industry if populated. We use company name as the dedupe key during import. If Rule associates multiple Contacts with a single Company, all Contacts link to the same Account after Account creation. Mismatch between Rule's loose company naming and Dynamics' structured Account model is resolved during the mapping phase.

Rule's optional pipeline stage names and order export as configuration metadata and are recreated as Opportunity Stage values in Microsoft Dynamics 365 Sales . Stage probability percentages map to stageprobability on each stage definition. We configure the Business Process Flow in Dynamics to match Rule's deal lifecycle stages if Rule includes a sales pipeline view.

Rule Campaigns (grouping of related automations and aggregate performance metrics) map to Microsoft Dynamics 365 Sales Campaign. Campaign name, type, status, and linked contact counts migrate. Campaign-level engagement analytics (open rates, click rates) are time-bound historical data and may not replay accurately in Dynamics; we migrate campaign metadata and contact counts, noting that the customer's admin should configure campaign influence in Dynamics to attribute pipeline revenue.

Rule contact tags migrate to Dynamics 365 Tags (if the Dynamics org has the modern Tagging experience enabled) or to a custom multi-select picklist field on Contact. Tag values are preserved as comma-separated entries; the customer chooses the target strategy during scoping. Tags used for contact classification rather than segmentation migrate as-is; tags used for dynamic segment membership do not activate as filters in Dynamics without a rebuild in the native segmentation tool.

Rule email engagement events (opens, clicks, bounces, unsubscribes) are exported as activity records and mapped to Microsoft Dynamics 365 Sales activity timeline entries. Open and click events migrate as Note records with a custom engagement_type field annotated to email, preserving timestamp and contact reference. Bounce and unsubscribe events migrate as Task records with Status = Cancelled and custom disposition fields. Whether these appear as native engagement analytics in Dynamics depends on the Dynamics Sales Insights license tier.

Rule's SMS, RCS, and social engagement events are tracked in channel-specific logs separate from email events. We export these as separate Task records with a custom channel_type field (sms, rcs, social) and annotate each entry with the source channel. Task description carries the engagement summary. These records append to the same Contact activity timeline in Dynamics, consolidating Rule's siloed channel data into a unified audit log.

Rule custom fields on Contacts and Companies (dropdown, date, numeric, text, multi-select) map to equivalent custom fields on Dynamics Contact and Account. We create the custom fields in the Dynamics environment via the solution designer before data import. Multi-select fields from Rule require explicit mapping to Dynamics Option Set values; we extract the Rule option list and create matching Option Set labels in Dynamics.

Rule suppression lists (unsubscribed, bounced, blocked contacts) export as a distinct dataset separate from active contacts. We flag suppressed contacts with a custom field (e.g., suppression_status__c) in Dynamics or add them to a Marketing List with suppression semantics. Suppression status does not auto-apply as a Dynamics marketing list rule; it requires manual flag setting or a Power Automate flow to maintain, which we document as post-migration admin work.

Rule user accounts (name, email, role) map to Microsoft Dynamics 365 Sales System User records. We resolve owner assignments on Contacts, Accounts, and Deals by matching Rule owner email to Dynamics User email. Any Rule owner without a matching Dynamics User goes to a reconciliation queue for the customer's admin to provision the corresponding User before record import resumes.