Migrate from Delivra to Microsoft Dynamics 365 Sales

Delivra Contacts map to Salesforce Lead or Dynamics 365 Lead based on lifecycle stage. Contacts with a lifecycle stage indicating a qualified buyer (customer, evangelist) map to Dynamics 365 Contact attached to an Account. Contacts with early-stage lifecycle values map to Lead. We preserve the original Delivra lifecycle stage in a custom field delivra_lifecycle_stage__c on both Lead and Contact for audit and reporting continuity.

Delivra Company records map directly to Dynamics 365 Account. The Delivra company domain becomes the Account Website field and serves as the dedupe key during import. Account must be created before Contact import so the AccountId lookup relationship is satisfied at Contact insert time.

Delivra Custom Tables with a 1:1 relationship to a Contact (e.g., a Subscription record linked one-to-one) map to a Dataverse custom entity with a lookup field to Contact. We create the destination custom entity in the customer's Dataverse environment, define the lookup field, and import the data using the Dynamics 365 Bulk API with parent-record resolution.

Delivra Custom Tables with a 1:many relationship (one Contact, many Subscription records) map to a Dataverse custom entity where each row carries a Contact lookup. We denormalize the foreign key reference, create one Dataverse record per Delivra row, and resolve the Contact lookup by email or contact ID at migration time. The parent Contact must be migrated before the child custom entity rows.

Delivra Custom Tables with many:many relationships require an intersection entity in Dataverse to replicate the junction. We extract the junction table from Delivra, create two Dataverse custom entities plus a many-to-many relationship via a link entity, and migrate junction rows after both primary entities exist. This adds a mapping phase and a validation step that is not required for flat data models.

Delivra Campaign records map to Dynamics 365 Campaign with CampaignName, status, targeting criteria, and channel information preserved. Delivra's SMS and multi-channel campaign targeting translates to Campaign Channel (Email or Other). Campaign member responses and engagement history migrate to CampaignResponse or to custom engagement fields on the related Contact.

Delivra email templates built in the drag-and-drop editor export as HTML and, where possible, as JSON structure. We convert HTML templates to Dynamics 365 Email Template format (text and HTML). Templates with dynamic content blocks and conditional personalization require manual rebuild in Dynamics 365's template editor, which we document with before-and-after screenshots and field reference notes.

Delivra's standard and advanced lead scoring models use point values assigned to contact attributes and behaviors. We export the full scoring model including rule definitions, point values, and thresholds. Microsoft Dynamics 365 Sales Premium includes AI-based lead scoring; for Standard tier, we document the model as a Power Automate flow specification and provide a field mapping to Dynamics 365 Contact that the admin uses to configure scoring in Power Automate.

Delivra segment definitions with filter conditions based on contact properties map to Dynamics 365 Marketing List (static or dynamic) or to a Dataverse View. Dynamic segments require a Power Automate flow or manual filter rebuild because Dynamics 365 Marketing Lists use FetchXML rather than Delivra's condition-builder syntax. We deliver a segment inventory with field mappings and condition equivalents.

Delivra click tracking, open tracking, and engagement history associate with contact records. We migrate aggregate engagement metrics as custom fields on the Contact record (e.g., last_email_opened_date, total_email_opens, total_email_clicks). Detailed engagement logs can be stored in a Dataverse custom entity if the customer needs the full timeline preserved, but the standard Microsoft Dynamics 365 Sales timeline does not accept third-party engagement data natively.