Migrate from ELAINE to Microsoft Dynamics 365 Sales

ELAINE Contacts map to Salesforce Lead (unqualified or early-stage) and Contact attached to an Account (qualified). We use ELAINE's lifecycle stage properties to determine the split, placing contacts with early-stage indicators (subscriber, lead) into Lead and those with sales-qualified stages into Contact with an Account link. The original ELAINE lifecycle stage and any custom contact properties migrate as custom fields on both Lead and Contact for audit and reporting continuity.

ELAINE Target Groups are subscriber segments with optional nested hierarchies. We map them to Microsoft Dynamics 365 Sales Marketing Lists (static or dynamic) attached to Leads or Contacts, or to custom multi-select picklist fields on Contact that preserve segment membership. Complex multi-level hierarchies are flattened during migration because CRM lists are inherently flat structures. We document the full group tree during discovery so the customer's admin can reconstruct hierarchies manually in Dynamics if needed.

ELAINE Email Campaigns map to Microsoft Dynamics 365 Sales Campaign records. Each individual email send within the campaign becomes a Campaign Activity linked to the parent Campaign. Campaign name, description, send date, subject line, content, and attachments migrate as Campaign fields and Notes respectively. Open rates, click rates, bounce rates, and unsubscribe counts from ELAINE have no native Microsoft Dynamics 365 Sales equivalent; we preserve these as custom number fields on the Campaign record and note that full email analytics require reporting through Power BI or an external email analytics layer.

ELAINE Mail Sequences with multi-step triggers, delays, and conditional branches are extracted as step-by-step configuration documents. Microsoft Dynamics 365 Sales Sequences are available only on Enterprise ($105/user/mo) and Premium ($150/user/mo) tiers and support cadence-based outreach with steps, actions, and enrollment rules. If the destination org has the appropriate tier, we evaluate whether the ELAINE sequence logic maps to a compatible Sales Sequence configuration and document the mapping. Complex nested sequences or sequences requiring triggers beyond Sales Sequences scope are documented for manual rebuild by the admin.

ELAINE A/B test configurations with subject line variants, content variants, and send-time variants are extracted and mapped to custom fields on the destination Campaign record (ab_test_type__c, ab_variant_a__c, ab_variant_b__c, ab_sample_size__c, ab_winning_metric__c, ab_result__c). Microsoft Dynamics 365 Sales does not include native A/B testing for CRM campaigns, so test configurations do not replicate as live automation in the destination. We preserve the test metadata so the customer's admin can manually apply winning variants to future campaigns.

User-created custom fields on ELAINE Contacts and Target Groups map to custom fields on Microsoft Dynamics 365 Sales Lead, Contact, or Account objects. Field types (text, choice, date, calculated) are evaluated for equivalent Dynamics 365 field types during schema design. Calculated fields are not replicated as calculated formulas; values are computed pre-migration and loaded as static values, with the calculation logic documented for manual reimplementation in Dynamics 365 as a formula field if required.

Files attached to ELAINE email campaigns or contact records are downloaded and re-associated at the destination. Campaign attachments attach as Notes linked to the parent Campaign record via ContentDocumentLink. Contact attachments attach as Notes linked to the corresponding Lead or Contact. File names and original creation timestamps are preserved. Post-migration, the customer may choose to migrate file storage to SharePoint with document management enabled in Dynamics 365 for long-term governance.

Historical engagement records from ELAINE (opens, clicks, sends, unsubscribes) map to custom activity fields on the Contact or Lead record. Because ELAINE does not store individual email activities as discrete CRM-style activity records, we migrate engagement summary data as custom fields (last_email_sent__c, last_open_date__c, click_count__c, bounce_count__c) rather than as separate Task or Event objects. If the customer has email Send logs or engagement exports with individual activity timestamps, we evaluate mapping them to Dynamics 365 Tasks with a custom engagement type field.