Migrate from Real Intelligence to Microsoft Dynamics 365 Sales

Direct 1:1 map. Dynamics 365 Contact requires an AccountId for most business workflows, so contacts without a primary company are attached to a designated placeholder Account or assigned per your predefined default rule at migration time. All standard fields such as name, email, phone, and address are transferred directly; any contacts missing required fields are flagged in the pre‑migration audit for manual correction before the batch commits.

Direct 1:1 map. Dynamics 365 Account supports parent‑account hierarchies via ParentAccountId, preserving structures such as subsidiaries and divisions. Each Real Intelligence company becomes an Account; name, domain (as Website), industry code, employee count, revenue, and address fields transfer. Accounts without a parent are inserted with a null ParentAccountId, while branch companies inherit the hierarchy, and any circular references are flagged in the pre‑migration audit for resolution before the batch loads.

Direct 1:1 map for unqualified or in‑progress leads. All lead fields such as name, email, phone, company, and source transfer to the D365 Lead entity. Leads already closed‑won or closed‑lost are migrated as Contacts under the corresponding Account with a closed Opportunity, preserving original status and close date. Leads qualified during migration follow the standard D365 lead‑qualification workflow to generate a Contact and Opportunity automatically.

Direct 1:1 map. Dynamics 365 Opportunity requires an AccountId (parent customer) and optional ContactId for the primary stakeholder. All standard deal fields—name, amount, close date, owner, and description—transfer directly. Stage values map to D365 StageName categories (Qualify, Develop, Proposal, Negotiation, Closed), with probability percentages taken from the D365 Sales Process definition. If the source deal includes a probability, it is stored in a custom field for reference.

Real Intelligence pipeline configurations with custom stages transform into D365 Sales Process stages. Each pipeline in Real Intelligence becomes a D365 Sales Process, with stage order and probability percentages re‑applied per your source configuration. Custom stage names are preserved as labels; if a stage lacks a matching D365 category, we create a stage label. Stage transitions and probabilities are verified in the pre‑migration audit to ensure forecast accuracy after go‑live.

Direct map to D365 Email entity. Original send timestamp, from/to addresses, CC/BCC, subject line, and body transfer to the Email record. Email direction (inbound/outbound) is stored in the Direction field, and the status reflects sent/received state. Attachments are re‑uploaded as Note or Attachment records, with Regarding linking to the parent Contact or Account; files larger than 10 MB are flagged for SharePoint or OneDrive integration before the batch loads.

Direct map to D365 PhoneCall. Duration, direction (inbound/outbound), subject line, outcome notes, and phone numbers transfer to the PhoneCall record. The Regarding field points to the primary Contact or Account; if the call involves multiple participants, additional relationships are created as related Activities. Call outcomes such as answered, voicemail, or missed are stored in the Outcome field for reporting.

Direct map to D365 Appointment. Start time, end time, subject, location, required and optional attendees, and meeting notes transfer to the Appointment record. The Regarding field links to the primary Contact or Account; if the meeting is online, the Teams or Skype link is preserved in the OnlineMeetingUrl field. Recurring meeting patterns are noted for manual reconstruction in D365 Calendar if not supported.

Direct map to D365 Annotation (Notes). The note text, creation timestamp, and author information transfer to the Annotation record; any rich‑text formatting is converted to plain text or HTML depending on D365 storage capabilities. Embedded images or file references are preserved as attachments linked to the note. The IsPrivate flag is honored, restricting visibility to the original owner unless shared explicitly in D365.

Real Intelligence custom objects requiring custom entity creation in Dynamics 365 via the maker portal or solutions. Custom tables in D365 use publisher-prefixed schema names (new_ or your publisher prefix) and may need relationship definitions to link to standard entities.

Real Intelligence custom fields that have no standard D365 equivalent become new_ prefixed custom fields on the target entity. Field type mapping: text to Single-Line Text, number to Whole Number or Decimal, date to Date and Time, pick-list to Option Set.

Owner resolution by email matching against D365 SystemUser table. The match is case‑insensitive and ignores whitespace. Unmatched owners are flagged in the pre‑migration audit report with the original email and record count; your team either assigns a fallback owner or provisions a new D365 user. For audit purposes the original owner email is stored in a custom field on the record.

File attachments are downloaded from Real Intelligence and re‑uploaded to D365 as Attachments (for emails) or Notes (for other entities) with the Regarding field linking to the parent Contact, Account, or Opportunity. File name, MIME type, and size are preserved; any duplicate filenames are renamed to avoid overwrite. Attachments exceeding 10 MB are redirected to SharePoint or OneDrive, with a URL stored in a custom field on the parent record.

Real Intelligence tags or category labels map to a custom Option Set field in D365 where each unique label becomes an option with its display text preserved. If a tag set exceeds 50 unique values, the migration switches to a custom text field to avoid Option Set limits, and a mapping table is provided for reference.