Migrate from Delivra to Salesforce Sales Cloud

Delivra Contacts with a lifecycle stage of subscriber, lead, or marketing qualified lead map to Salesforce Lead. Delivra Contacts at sales qualified or customer stage map to Salesforce Contact tied to a Salesforce Account. We compute the split using Delivra's lifecycle_stage and current_status properties at migration time, and preserve the original Delivra lifecycle stage in a custom field delivra_original_lifecycle__c on both Lead and Contact for audit and reporting continuity.

Delivra Custom Tables with a 1:1 relationship to Contact (such as a demographic extension table or address book) map to a Salesforce Custom Object with a lookup field pointing to the Contact record. We create the Custom Object __c API name to mirror the Delivra table name, set up the Contact lookup field, and migrate every row with the Contact's Delivra contact_id preserved as an external ID for lookup resolution.

Delivra Custom Tables with a 1:many relationship (one Contact to many related records, such as subscriptions, policies, or properties) map to a Salesforce Custom Object with a lookup to Contact. The Contact is created first, then each related Custom Table row is imported with the Contact lookup resolved via the external ID. We preserve the relationship hierarchy by denormalizing the foreign key as a text field on the Salesforce record for audit.

Delivra Custom Tables with many:many relationships (such as contacts linked to multiple products or events) require a junction object in Salesforce. We extract the junction table, create a Salesforce Custom Object representing each side of the relationship, and build a Custom Object junction with two lookup fields. This is the most complex Custom Table scenario and requires a dedicated mapping phase during scoping.

Delivra Campaign records map to Salesforce Campaign. The campaign name, status (active, draft, archived), targeting criteria, and associated contact list membership migrate as Campaign records with CampaignMember records linking to the migrated Contacts. Campaign content (email body, subject line) is extracted as HTML and attached as a ContentDocument to the Campaign for reference.

Delivra Segments are defined by filter conditions based on contact properties and behaviors. We extract the segment criteria for each list and document them as a written filter specification. Segments cannot migrate as live Salesforce Campaigns because Salesforce Campaigns use manual CampaignMember adds rather than dynamic filter-based membership. We create the equivalent Salesforce Campaign per segment and document the original filter logic for the customer's admin to re-implement using Salesforce Reports as campaign audiences.

Delivra's lead scoring models (demographic and behavioral point values) migrate as custom numeric fields on the Salesforce Lead or Contact object. The scoring values transfer as raw numbers. Salesforce's native Lead Scoring product (a paid add-on available from Professional tier) is the recommended replacement for ongoing scoring logic, and we include a written recommendation for the customer's admin to evaluate it post-migration.

Delivra Users map to Salesforce User records. We resolve Delivra owners by email match against the Salesforce destination org's User table. Any Delivra owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active versus inactive status is preserved in a custom field on User.

Delivra email engagement history (sends, opens, clicks, replies) migrates to Salesforce EmailMessage records (email content) linked to a Task record (activity timeline entry). The WhoId on Task points to the migrated Lead or Contact; WhatId points to the related Campaign or Account. Engagement timestamps are preserved by setting ActivityDate to the original Delivra engagement timestamp.

Delivra click tracking data (URL clicked, timestamp, contact) migrates as custom Task fields on the associated email engagement record. For high-volume click histories, we aggregate per-contact click counts into a custom field (total_clicks__c) to avoid record explosion, and store a summary record as a Campaign Activity note.

Delivra form submission events migrate as Salesforce Task records with TaskSubtype = Submit and a custom field form_name__c carrying the original Delivra form identifier. Submission timestamp migrates as ActivityDate. If the form was part of a Delivra workflow, the workflow is documented in the handoff inventory rather than recreated in Salesforce.

Delivra email templates built with the drag-and-drop editor migrate as Salesforce Email Templates. We extract the template HTML and body content, convert it to Salesforce-compatible HTML, and create EmailTemplate records. Complex templates with conditional content or dynamic snippets require manual review and may need re-building in Salesforce's Lightning Email Template builder. We flag any template that cannot be auto-converted during the template audit phase.