Migrate from RedEye to Microsoft Dynamics 365 Sales

RedEye's unified Contact with lifecycle stage maps to either Salesforce Lead (for unqualified or unknown lifecycle stage) or Dynamics 365 Contact tied to an Account (for qualified stages). We apply a split rule during scoping based on the customer's RedEye lifecycle stage matrix, migrate Lifecycle Stage to a custom field redeye_lifecycle_stage__c on both Lead and Contact for audit, and resolve the AccountId lookup for Contact records before insert.

RedEye Company records map to Dynamics 365 Account. The company domain becomes the Account Website field and is used as the dedupe key. RedEye's lighter-weight company linkage in its B2C model becomes a full Account with Address, Industry, and NumberOfEmployees fields. Account is created before any Contact import so the AccountId lookup is satisfied at Contact insert.

RedEye Campaigns map to Dynamics 365 Campaign records with channel assignments preserved in CampaignType and Channel fields. Campaign goal metrics migrate to Campaign fields. For campaigns that represent revenue-generating initiatives with closed deals, we also create parallel Opportunity records linked to the Campaign via the CampaignId field. The customer chooses the primary mapping target during scoping based on how they use campaigns.

RedEye behavioural events (website actions, email opens, purchase triggers) migrate as Salesforce Task or Event records linked to the Contact via WhoId. Event timestamp migrates to ActivityDate or StartDateTime. We flag event types that cannot map cleanly to Task or Event subtypes (for example, custom event categories) for custom field storage. Parent-record resolution uses the Contact-to-Lead-or-Contact mapping computed during the first migration phase.

RedEye product catalogue records map directly to Dynamics 365 Product2. SKU migrates to ProductCode, product name to Name, pricing to StandardPrice on the PricebookEntry, and category to a custom field or Product Category picklist. Unlimited product records on both RedEye tiers migrate without volume constraint into Dynamics 365.

RedEye dynamic segments defined by behavioural rules and demographic criteria export as structured rule-set documents. We rebuild equivalent filter logic in Dynamics 365 using Advanced Find views or custom Power Apps canvas apps. Static segments migrate as Contact lists and are linked to the relevant Campaign as CampaignMembers. Segment rebuild is a configuration task for the customer's admin, documented in the handoff package.

RedEye custom contact and event fields require explicit field-to-field mapping with Salesforce field type conversion. Text properties map to Text fields; date fields map to Date fields; multi-select tags map to Multi-Select Picklist. We extract the full RedEye custom field schema during discovery, map each to a typed Salesforce custom field, and deploy the schema into Sandbox before any data import. Custom field API names in Dynamics 365 follow the __c suffix convention.

RedEye contact and campaign tags migrate as values in a Dynamics 365 Multi-Select Picklist field. We flag any tag characters unsupported by Salesforce schema (such as commas within picklist values) and normalise them before import. Tag naming conventions are preserved exactly. Tags used for content classification become Salesforce Topics with TopicAssignment records if the customer uses the native topic model.

RedEye channel assignments at the campaign level do not have a native Dynamics 365 equivalent for non-email channels (SMS, push, social, in-app). We document each channel assignment in the migration handoff with the channel type, RedEye configuration, and recommended Dynamics 365 or Power Automate replacement. Email channel migrates natively; additional channels require manual configuration post-migration.

Campaign assets (images, documents) attached to RedEye campaigns or emails export as files and are re-uploaded to Dynamics 365 SharePoint integration or as ContentDocument records linked via ContentDocumentLink to the parent Campaign or Contact. File hierarchy and naming conventions are preserved to minimise manual re-linking effort.