Migrate from Agillic to Zoho CRM

Agillic Recipients are the primary person record and may represent both prospects and customers depending on the client's segmentation. We split Recipients into Zoho CRM Lead (for unqualified or marketing-stage records identified by communication-preference flags) and Contact (for records that have entered a sales process). The split rule is defined during discovery against the client's recipient lifecycle stages. We preserve the original Recipient ID and any lifecycle stage identifier in custom fields agillic_recipient_id__c and agillic_lifecycle_stage__c for audit traceability.

The Recipients Export file generated from Agillic (a full snapshot of all recipient records and current field values) serves as the authoritative baseline for the migration. We cross-reference it against the REST API export to identify records with missing or null values that need reconciliation before Zoho import.

Standard recipient fields that map to Zoho Lead include: First Name, Last Name, Email, Phone, Mobile, Title, Company, Address, City, State, Country, Postal Code, and Source. These map directly to the corresponding Zoho Lead standard fields. The agillic_recipient_id__c custom field holds the original Agillic Recipient ID for record matching and reconciliation.

Agillic Recipients with a company association map to a Zoho Contact linked to an Account. We extract the company name from the Recipient's organisation property, create or match the Zoho Account by name, then insert the Contact with AccountId resolved. This ensures the Account-Contact hierarchy required by Zoho CRM is satisfied at insert time.

Every Agillic custom recipient property enumerated during discovery is created as a Zoho CRM custom field on either Lead or Contact before migration begins. Field types are mapped: string properties become Single Line fields; multi-value properties become Multi-Select; date/datetime properties become Date or DateTime fields; boolean properties become Checkbox fields. The full list of custom fields and their Zoho field IDs is documented in the field mapping appendix delivered before production migration.

Agillic Global Data Tables are custom relational structures referenced within Flows. We export table schemas (column names, data types, relationships) and all row data. In Zoho CRM we create Custom Modules with matching field definitions, then populate the rows. Custom Modules in Zoho support lookup relationships to standard modules (Accounts, Contacts, Deals) so the table-recipient relationship is preserved.

Agillic email Activity records (send, open, click, bounce, delivery confirm) migrate to Zoho CRM Tasks with TaskSubtype = Email. The activity type (sends, opens, clicks) is stored in a custom field activity_type__c. Email subject and body content migrate to the Task Subject and Description fields respectively. The Flow Execution ID is stored in a custom field flow_execution_id__c for campaign attribution.

Agillic SMS Activity records (send, delivery, reply, opt-out) migrate to Zoho Task records with a custom field sms_status__c holding the delivery state and sms_content__c holding the message body. The recipient is linked via the WhoId pointing to the migrated Contact or Lead.

Agillic event-triggered Activity records (behavioural triggers, webhook events, point-of-sale events) have no direct Zoho equivalent. We migrate these as Zoho Tasks with a custom field event_type__c holding the Agillic event name and event_payload__c holding a JSON representation of the event attributes. This preserves the event context for audit and journey reconstruction.

Agillic Flow Execution IDs uniquely identify each campaign run and are appended to Activity Exports when the Flow Execution ID setting is enabled. We create a Zoho Custom Module called Flow Execution Audit with fields: Flow Name, Flow Execution ID, Trigger Event, Start Timestamp, End Timestamp, Recipient Count, and Status. Each Activity record in Zoho links back to this module via the flow_execution_id__c custom field.

Agillic Profiles aggregate all known data about a recipient across touchpoints and are equivalent to the enriched Recipient record. We treat Profile data as the Recipient with enriched attributes from Activity and custom data tables, mapping to the Zoho Contact record with all aggregated properties stored as custom fields on the Contact.

Agillic audience segments exported to Google and Meta contain member lists and segment logic. We export the segment definitions (segment name, filter criteria, and member count) into a Zoho Custom Module called Audience Segments. Member-to-contact linkage is preserved via the recipient email address. The segment filter logic is documented in the handoff for manual rebuild in Google Audience Manager or Meta Business Manager.

Agillic Recipients store an owner reference. We resolve Agillic owner email addresses against Zoho CRM Users. Owners without a matching Zoho User are held in a reconciliation queue for the customer's admin to provision before record import resumes. Active status of the Zoho User determines whether the OwnerId is set to an active or inactive Zoho User.

Agillic export format settings (delimiter type, date format, timestamp timezone, file extension) are documented from the client's Settings > System Settings > Export configuration. These inform the CSV format we produce for Zoho's native import wizard or API ingestion, ensuring field delimiters and date formats match Zoho's expected import format.