Migrate from Rainbow CRM to Microsoft Dynamics 365 Sales

Rainbow CRM Contacts export as flat CSV records with name, email, phone, and address fields. We map these directly to Microsoft Dynamics 365 Sales Contact fields. Lifecycle stage is not a native Rainbow CRM field and will not appear in exports. Parent Account resolution uses the company name field to match against imported Account records; any Contact with an unmatched company name is flagged for manual review before the batch commits.

Rainbow CRM Companies export as flat records. We import them first, before Contacts, to enable accountid lookup resolution on Contact insert. The company domain from Rainbow's export populates the Account Website field. Any duplicate Account names are deduplicated by appending a numeric suffix and flagged in the reconciliation report.

Rainbow CRM Deals export with internal pipeline stage labels that do not match Microsoft Dynamics 365 Sales stage names. We present a stage mapping table during scoping, apply the agreed mapping before the first import batch, and set Opportunity StageProbability values from Rainbow's deal probability percentages rounded to the nearest integer. Each pipeline in Rainbow maps to a Microsoft Dynamics 365 Sales Record Type.

Rainbow CRM Leads export as a separate object from Contacts. We import Leads before Contacts to avoid duplicate email conflicts. Where a Lead email matches an existing Contact email, we flag the conflict in the reconciliation report and the customer's admin decides whether to merge, convert, or keep both records. Lead Status from Rainbow maps to Microsoft Dynamics 365 Sales Lead Status.

Rainbow CRM Tasks export as flat records without assignee IDs. We map task titles, due dates, and descriptions to Microsoft Dynamics 365 Sales Task fields. Assignee resolution requires a cross-reference against the imported User list by email match; tasks without a matched User are assigned to the migration-admin user and flagged for reassignment in the reconciliation report.

Activity history exports from Rainbow CRM in a denormalized flat format with no typed activity subtype. We inspect the export schema to identify activity type indicators, split records by type, and reconstruct them as typed Salesforce records: calls as Task with TaskSubtype=Call, meetings as Event, emails as EmailMessage, and standalone notes as Note. We resolve the WhoId (Contact or Lead) and WhatId (Account or Opportunity) from the denormalized export fields before insert.

Rainbow CRM exposes a subset of custom fields in its documented export format. We inspect the export schema during discovery and flag any custom properties that do not appear in the raw file. For high-value custom fields absent from export, we request a manual supplemental export or coordinate a direct data extraction where possible. Custom fields that appear in export are mapped to Microsoft Dynamics 365 Sales custom fields created during schema design.

Rainbow CRM does not expose file attachments or document records through its documented export format. Any linked files must be re-uploaded manually to Microsoft Dynamics 365 Sales SharePoint integration or attached directly to records post-migration. We flag the attachment gap in the discovery report and note that the customer should download the full attachment archive from Rainbow before the migration date.