Migrate from Agillic to Salesforce Sales Cloud

All Agillic Recipients map to Salesforce Contact (not Lead, because Agillic has no concept of an unqualified prospect — every Recipient is a person record regardless of engagement stage). We preserve the original Agillic Recipient ID in a custom field agillic_recipient_id__c and any lifecycle-equivalent custom property (e.g., subscription_status, customer_type) in a custom field agillic_lifecycle__c for segmentation and reporting. AccountId is resolved via the Company-to-Account mapping before Contact insert.

Agillic Recipients may carry a company association as a custom property or via a Global Data Table relationship. We map this to Salesforce Account with the company name mapped to Account.Name and the company domain (if present) mapped to Account.Website for deduplication. Account is created before Contact import so the AccountId Lookup is satisfied at insert time.

Agillic Activity records of type send, open, click, and bounce map to Salesforce Task records. The Activity type becomes a custom Task field activity_type__c (picklist: SEND, OPEN, CLICK, BOUNCE, DELIVERED, UNSUBSCRIBED). The original Agillic Activity timestamp migrates as ActivityDate for timeline ordering. Flow Execution ID migrates to a custom field flow_execution_id__c on Task.

SMS events migrate as Task records with a custom field sms_direction__c (SENT, DELIVERED, REPLIED) and sms_content__c carrying the message body. If Salesforce Service Cloud SMS integration is active, we map to the native MessagingSession object; otherwise, Tasks with custom SMS fields serve as the archive.

Agillic event-triggered activities (e.g., webinar registrations, abandoned cart triggers, custom event types) map to Salesforce Event records. The event name maps to Event.Subject, the event timestamp maps to Event.StartDateTime, and event metadata migrates to custom Event fields. We preserve the Flow Execution ID on Event as flow_execution_id__c.

The Flow Execution ID uniquely identifies each campaign run in Agillic. We carry it as a custom field on every migrated Activity record (Task and Event) so that analysts can group records back to specific campaign executions post-migration. This requires the Flow Execution ID to be enabled in Agillic Settings > System Settings > Export > Activity Exports before we pull historical data.

Agillic Flows are automation logic stored as internal execution configurations with no documented export endpoint. We export Flow names, associated trigger events, and the count of executions per Flow during migration. We deliver a written Flow inventory document that lists every active Flow with its trigger type, conditions, actions, and a recommended Salesforce Flow equivalent (record-triggered, scheduled, or screen flow). The customer's admin or a Salesforce partner rebuilds them post-migration.

Agillic Global Data Tables are custom relational structures referenced within Flows. We export the table schema (column names, data types) and all row data. In Salesforce, we create a custom object with an API name matching the Global Data Table name plus a __c suffix, and custom fields matching each column. Lookup relationships between Global Data Tables are recreated as Lookup or Master-Detail relationships on the destination custom objects.

Each row in an Agillic Global Data Table becomes a Salesforce custom object record. We resolve any lookup references to Recipients (via Recipient ID to Contact mapping), other Global Data Tables (via the destination custom object IDs), and carry the original row identifier in a custom field original_row_id__c for audit.

Agillic email, SMS, and push templates carry dynamic field mappings and HTML content. We export template content, subject line placeholders, and dynamic field references. HTML templates require conversion to Salesforce EmailTemplate format (with merge field syntax updated from Agillic to Salesforce merge field format). We do not perform the HTML conversion as a code task; we deliver a template migration document and the customer refactors with their email developer or an implementation partner.

Agillic Reusable Content Blocks (modular HTML/text fragments) export with their content and metadata. In Salesforce, these map to ContentAsset records (for reusable assets) or are documented as ContentBlockKey references for use within Salesforce Marketing Cloud Email Studio. Recombination in the destination CMS or email platform requires content refactoring outside migration scope.

Agillic audience segments synced to Google and Meta are documented as segment definitions with membership criteria. We deliver an audience migration document that specifies each segment's logic (criteria, operators, values) and recommend recreating equivalent segments in Salesforce Data Studio, Account Engagement (Pardot) Dynamic Lists, or Salesforce Campaign Audiences depending on the customer's destination stack.

Agillic Owner references on Recipient, Activity, and Flow Execution records map to Salesforce User by email match. Any Owner without a matching User in the destination org is held in a reconciliation queue for the customer's admin to provision before record import resumes.

The Agillic Recipients Export feature generates a full snapshot file of all recipient records with current field values. We use this as the primary baseline for Contact migration and reconcile against API-fetched records to catch any updates between API polling cycles.