Migrate from Rainbow CRM to Salesforce Sales Cloud

Rainbow CRM exports Contacts as flat records. We split them into Salesforce Lead and Contact based on any lifecycle or status indicator present in the export. Rainbow CRM does not have a native Lead object, so the split logic is defined during scoping: typically unqualified records map to Lead and records with an associated Deal map to Contact. The original email, phone, address, and company association preserve. Any lifecycle stage value found in the export migrates to a custom field rc_lifecycle_stage__c for audit.

Rainbow CRM Companies map directly to Salesforce Account. We import Accounts before Contacts so that AccountId can be resolved at Contact insert time. The Company name becomes Account Name, and any domain or website field in the export populates the Account Website field for deduplication reference.

Rainbow CRM Deals map to Salesforce Opportunity. The deal amount, close date, and description transfer directly. Deal owner resolves to Salesforce OwnerId via email match against the User table. The Deal-to-Account association resolves to Opportunity.AccountId by matching the associated Company name in the Account import.

Rainbow CRM exports Deals with its own internal stage labels that do not match Salesforce stage conventions. We present a stage mapping table during scoping and apply the agreed mapping in the transform step before the first Opportunity batch. Each mapped stage gets a probability percentage that we carry from the source or derive from the customer's current pipeline distribution. Stage remapping is reversible in Salesforce after import.

If the Rainbow CRM export contains multiple Deal pipelines or record types, we create corresponding Salesforce Record Types on Opportunity and assign a Sales Process per pipeline that scopes the available stage values. Page Layouts are assigned per Record Type so that deal fields relevant to each pipeline display correctly for the assigned sales team.

Rainbow CRM Leads export as a separate object from Contacts but may share email addresses with Contact records. We deduplicate at import time by email and flag any duplicate email conflicts for customer review before writing to Salesforce. Lead source, status, and any score value in the export map to standard Salesforce Lead fields.

Rainbow CRM Owners (assigned user on Contact, Company, Deal, and Activity records) resolve to Salesforce User by email match. Owners without a matching Salesforce User enter a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId references are required on Opportunity and Contact, so this step gates subsequent phases.

Rainbow CRM Tasks export as flat records with title, due date, and description. Assignee resolution requires a cross-reference against the User mapping. We map task status, priority, and due date to the equivalent Salesforce Task fields. Rainbow CRM does not export assignee IDs, so unresolved owners map to a designated placeholder User until the admin confirms.

Rainbow CRM call activity exports in a denormalized format. We reconstruct call records as Salesforce Task with TaskSubtype set to Call. Call duration, disposition, and any notes in the export transfer to custom Task fields. Activity timestamp preserves as ActivityDate to maintain the timeline order.

Rainbow CRM email activity exports as denormalized records. We reconstruct them as Salesforce EmailMessage records (the email content) linked to a Task record (the activity timeline entry). WhoId points to the matched Lead or Contact; WhatId points to the related Opportunity or Account. Subject, body, and direction (sent/received) transfer from the export fields.

Rainbow CRM notes and comments export as flat records. We import them as Salesforce Note records linked via ContentDocumentLink to the parent Contact, Lead, Account, or Opportunity. Note title and body transfer from the export. If the export embeds any file references in notes, we flag them for manual re-upload since attachments do not export directly.

Rainbow CRM exposes a subset of custom fields in its export format. We inspect the export schema during discovery and compare against the customer's field inventory. High-value custom fields that appear in the export map to Salesforce custom fields (__c) of equivalent type. Custom fields absent from the export schema require manual extraction coordination or are flagged as not migratable from the documented export. We note each gap before committing to scope.

Rainbow CRM does not expose file attachments or document records through its documented export format. Any linked files referenced in Deals, Contacts, or Notes must be migrated separately via direct database access if available, manual re-upload to Salesforce Files, or a file-sharing handoff. We flag every record with an attachment reference so the customer can assess manual re-upload scope.

If the Rainbow CRM export includes product or item records associated with Deals, we map them to Salesforce Product2. Standard Price Book entries are created during migration to enable OpportunityLineItem associations. Product code, name, and description transfer from the export fields.