Migrate from Agillic to Twenty CRM

Agillic Recipients map directly to Twenty CRM Contacts. The Recipient's email address is the primary dedupe key and maps to Contact.email. All standard recipient fields (first name, last name, phone, address) map to their Twenty CRM equivalents. Each client's custom recipient properties require enumeration before mapping — we extract the full property list via the Recipient API and create matching custom fields in Twenty CRM before import.

Agillic Recipients linked to a company context map to a Twenty CRM Person record associated with a Company record. We resolve the company association by extracting any company identifier from the Recipient's custom properties or Global Data Table joins and linking to the Company record during import.

Agillic Global Data Tables are custom relational structures referenced within Flows. We export table schemas and all row data. Each table maps to a Twenty CRM Custom Object. Table rows import as Custom Object records with lookup relationships to the relevant Contact, Company, or Opportunity where the join logic is resolvable from the source data.

Agillic Activity records of type send (email sends, SMS sends) map to Twenty CRM Tasks with the activity type recorded. The original send timestamp becomes the Task due date or activity date. The Flow Execution ID is preserved as a custom field for audit trail when enabled in Agillic's export settings.

Agillic Activity records of type open map to Twenty CRM Activity timeline entries. The open timestamp preserves the engagement date. Multiple opens per email generate multiple activity entries, each with the original timestamp.

Agillic Activity records of type click map to Twenty CRM Activity timeline entries with the clicked URL preserved in a custom field if Twenty CRM supports it, or as a text note on the activity record. The click timestamp is preserved.

Agillic bounce Activity records map to Twenty CRM Activity timeline entries with bounce type (hard/soft) and bounce reason preserved. Bounce records flag the Contact's email validity and can trigger an email verification workflow in Twenty post-migration.

Agillic SMS delivery Activity records map to Twenty CRM Tasks. Delivery status (delivered, failed, undelivered) migrates as a custom field or task status. SMS content migrates as a note attached to the activity record.

Agillic custom event Activity records (triggered events, behavioural events, point-of-sale events) map to Twenty CRM Tasks with the event type preserved in a custom field and event metadata stored as a text note. We flag these for manual verification post-migration because event taxonomy varies per Agillic client configuration.

The Flow Execution ID (when enabled in Agillic's Activity Export settings) is preserved as a custom field on the Activity record or as a Tag in Twenty CRM. This enables matching activity records back to specific campaign runs without native Flow integration in the destination platform.

Agillic Profiles aggregate all known data about a Recipient across touchpoints. We treat Profile data as equivalent to a Contact record enriched with attributes from Activity and Global Data Table joins. All enriched attributes map to Twenty CRM Contact custom fields.

Agillic audience segments exported to Google and Meta are documented as Segment definitions. We capture the segment membership criteria and recreate them as Tags or Groups in Twenty CRM. The actual audience sync requires rebuilding in Twenty's integrations or a third-party sync tool post-migration.