Migrate from Agillic to Microsoft Dynamics 365 Sales

Agillic Recipients with a subscriber or prospect lifecycle stage map to Microsoft Dynamics 365 Lead. Recipients with a confirmed buyer, customer, or evangelist lifecycle stage map to Dynamics 365 Contact tied to an Account. We compute the split at migration time using the customer's recipient property values, and preserve the original Agillic lifecycle stage in a custom field agillic_lifecycle_stage__c on both Lead and Contact for audit and reporting continuity.

Agillic Company records — whether stored as a dedicated entity or embedded in Recipient fields — map to Microsoft Dynamics 365 Account. The Company name becomes Account.Name, city and country map to BillingCity and BillingCountry, and postal code maps to BillingPostalCode. Account is created before any Contact import so that the CustomerId lookup relationship is satisfied at the moment of Contact insert.

Agillic's Recipients Export feature generates a structured file of all recipient records and their current field values. We use this as a baseline for full-contact migrations, then reconcile against API data for any fields not included in the export format. The export file feeds directly into the Dynamics 365 Data Management framework or Dataverse bulk import.

Every Agillic send, open, click, bounce, SMS delivery, and event trigger stored as an Activity record maps to a Dynamics 365 Task (for email, SMS, and task-type activities) or Event (for meeting and event-type activities). The Agillic activity type, timestamp, recipient ID, and channel are preserved as Task fields, and the WhatId or RegardingObjectId points to the migrated Contact or Lead.

Agillic's Activity Export bundles all events for a given date range across channels into a structured file. We schedule exports spanning the customer's entire history, parse the file into Task and Event rows, and bulk-import via the Dataverse bulk import API. If Flow Execution ID was enabled, we preserve it in a custom field agillic_flow_execution_id__c on the Activity record for journey reconstruction.

The Flow Execution ID uniquely identifies each Agillic campaign trigger instance and is appended to Activity Exports only when explicitly enabled under Settings > System Settings > Export > Activity Exports. We store this ID in a custom field on Task and Event in Dynamics 365 so that activity records can be matched back to specific Agillic campaign runs. If this setting was off during the export period, the Flow Execution ID data is permanently absent and cannot be reconstructed.

Agillic Global Data Tables are custom relational data structures referenced within Flows. We export table schemas and all row data, then create equivalent custom entities in Dataverse with the same column structure and data types. Lookup relationships between tables become Dataverse lookup fields on the custom entity. The customer rebuilds any data table query logic as Dataverse views or Power Apps canvas components post-migration.

Agillic Content Blocks are modular HTML or text fragments used across templates. We export block content and metadata as Web Resources in Dataverse. Recombination in Dynamics 365 email templates or Power Automate approval notifications requires content refactoring. HTML blocks migrate as text strings; the customer's marketing or admin team rebuilds the visual placement in Dynamics 365 email templates.

Agillic Templates define layout and dynamic content fields for email, SMS, print, and push channels. We export template content and field mappings as reference documents. HTML-based templates require conversion to the destination system's template format. Dynamics 365 email templates are rebuilt as Email Template records; SMS templates migrate as Power Automate approval message definitions or custom entities.

Agillic Owner records map to Microsoft Dynamics 365 User by email address. We resolve each Owner referenced on a Recipient, Activity, or Global Data Table record and match to the destination User. Owners without a matching User go to a reconciliation queue for the customer's admin to provision before record import resumes.