Migrate from eTrigue to Microsoft Dynamics 365 Sales

eTrigue Prospects map directly to Microsoft Dynamics 365 Contacts in most scenarios. Standard fields (name, email, company, phone) migrate cleanly via CSV. We resolve the company name into an Account lookup during import, creating the Account first if it does not exist. Prospects with no email or no company name route to a Lead record instead, since Dynamics 365 requires a Lead for unqualified contact records. The source Prospect ID is preserved in a custom field etrigue_prospect_id__c for audit and cross-reference.

eTrigue Campaigns map to Microsoft Dynamics 365 Campaign records. Campaign name, start and end dates, status, and budgeted cost migrate as standard Campaign fields. We use the Campaign entity in Dataverse to preserve campaign attribution data. Note that Dynamics 365 marketing automation features (Dynamics 365 Marketing app) are separate from Sales; campaign response tracking and nurture workflows require the marketing module or a Power Automate rebuild.

eTrigue Prospect Activity History records (page views, email opens, form submissions, campaign responses) migrate to Dynamics 365 Activity records attached to the Contact or Lead. We map activity type to a custom activity-type field since Microsoft Dynamics 365 Sales uses Task and Event as generic containers. Timestamps migrate as ActivityDate for timeline ordering. High-volume activity histories use the Dataverse Bulk API with chunking to avoid timeout.

eTrigue's five Lead Score sub-components (Campaign Score, Activity Score, Source Score, Relationship Score, Buy Time Score) each export as separate numeric fields on the Prospect record. We create five custom fields on the Contact and Lead entities in Dynamics 365 (etrigue_campaign_score__c, etrigue_activity_score__c, etrigue_source_score__c, etrigue_relationship_score__c, etrigue_buy_time_score__c) and import each value independently. The composite total is preserved in a sixth field etrigue_lead_score_total__c. The customer rebuilds composite scoring logic as a calculated field or Power Automate flow post-migration.

The 3D Lead Scoring model enriches standard scoring with content-type engagement weighting. We export the 3D score as a composite value and note that Microsoft Dynamics 365 Sales does not have a native equivalent. We create a custom field etrigue_3d_score__c to carry the composite value, and flag any content-type weighting rules that the customer's admin should incorporate into Microsoft Dynamics 365 Sales AI Lead Scoring or a Power Automate rebuild.

eTrigue supports Boolean, Text, and other custom field types defined under Settings > Prospect Settings > Prospect Fields. Boolean fields store a true/false with custom labels per value. We handle type mapping (Boolean to Two Option in Dynamics 365, Text to Single Line of Text, etc.) and preserve the custom field labels as field display names in the destination. Custom field API names in Dynamics 365 use the etrigue_ prefix for disambiguation. We validate picklist values against the Dynamics 365 field metadata before import to avoid rejection.

eTrigue Content Types classify prospect engagement with content categories and export as tag or label values. We migrate these as a multi-select text field etrigue_content_types__c on the Contact or as text tags in a dedicated field. Microsoft Dynamics 365 Sales does not have a native tag object at the Contact level; the customer chooses whether to use a multi-select picklist or a plain text field during scoping.

eTrigue landing pages and progressive form definitions do not have a direct equivalent in Microsoft Dynamics 365 Sales . We export form field definitions and map them to a configuration document for the customer to implement in Microsoft Dynamics 365 Sales web-to-lead, Dynamics 365 Marketing forms, or a Power Apps portal. The page styling and layout do not migrate; these are rebuilt post-migration by the customer's web or marketing team.