Migrate from Engage Messaging to Microsoft Dynamics 365 Sales

Engage Messaging Contacts migrate to Microsoft Dynamics 365 Sales Contact records. The phone number field maps to Telephone1 on Contact. Opt-in status migrates to a custom field em_opt_in__c (boolean) and to EmailOptOut or DonotPhone flags as appropriate. Custom Contact properties (beyond phone, email, name) map to custom fields on Contact created in the destination org before migration. Deduplication uses email as primary key with phone as secondary.

Engage Messaging Conversation threads do not map directly to a single Dynamics 365 object. We split each conversation into individual Activity records: inbound and outbound message exchanges become EmailMessage records (for threaded email-style display) or Task records (for activity timeline ordering), with the original thread ordering preserved by setting ActivityDate to the source timestamp. The Contact lookup resolves via phone number match on the Contact record created in step one.

Individual SMS, MMS, and RCS messages migrate as EmailMessage records in Dynamics 365. Direction (inbound/outbound) maps to DirectionCode, timestamp maps to CreatedOn, and message body maps to Description (for SMS text). Delivery status from Engage Messaging is preserved as a custom field em_delivery_status__c on the EmailMessage because Dynamics 365 does not natively track SMS delivery status on EmailMessage records.

Engage Messaging tags applied to Contacts migrate to a custom multi-select picklist field on Contact (em_tags__c) if tag volume is under 50 unique values. For larger tag sets, we recommend Salesforce Topics with TopicAssignment records linked to Contact. The customer chooses the strategy during scoping. Tags do not carry over as a native CRM tagging system unless Topics are enabled.

Engage Messaging Contact Segments export as criteria lists (tag combinations, engagement thresholds, date ranges). These criteria cannot be transferred as executable segment logic to Microsoft Dynamics 365 Sales . We export the segment definitions as a written criteria document listing each segment name, its member Contacts, and the defining rules. The customer's admin recreates segments as Static or Dynamic Marketing Lists in Dynamics 365 or as custom Contact fields.

MMS media files (images, audio, video) are downloaded from Engage Messaging storage separately from message text. We attach each file to the corresponding EmailMessage record as an EmailAttachment or create a Note record with the file attached via NoteAttachment. File size must comply with Dynamics 365 attachment limits (maximum 32 MB per attachment). Large video files may require compression or may be stored in SharePoint with a link placed in the Activity record.

Engage Messaging dedicated and toll-free number metadata (number value, type, status) is exported as a mapping document but cannot be transferred to Dynamics 365 because phone numbers in D365 are Contact fields, not standalone provisioned resources. We provide a re-provisioning checklist identifying every active Engage Messaging number that needs replacement with a new SMS provider number post-migration. The Contact Telephone fields (Phone, Telephone1, Telephone2, MobilePhone) are populated from the source Contact record independently of number provisioning.

Message sequences, triggers, delays, and conditional branches in Engage Messaging do not export as executable logic. We export the sequence structure (trigger event, message steps, delays, conditions, opt-out paths) as a written mapping document with step-by-step descriptions and screenshots. The customer's admin or a Dynamics 365 partner rebuilds the equivalent logic in Salesforce Flow or in Dynamics 365 Customer Insights - Journeys for real-time journey orchestration. Automations are out of scope for direct migration.