Migrate from Agillic to Nutshell

Agillic Recipients map to Nutshell Contacts (API noun: Contact; UI noun: Person). Every standard recipient field (email, first name, last name, phone) maps to Nutshell Contact fields. Custom recipient properties defined in the client's Agillic schema are enumerated during discovery and created as Nutshell custom fields before migration. The Agillic Recipient ID is preserved in a custom field agillic_recipient_id__c for reconciliation.

Agillic Companies map to Nutshell Accounts (API noun: Account; UI noun: Company). The Company name maps to Account.name, and the postal address maps to Account.address fields. Nutshell Accounts have a simpler address structure than Agillic's; complex multi-line or multi-address records are consolidated to the primary address.

Agillic Recipients are linked to Companies via a many-to-one relationship. In Nutshell, Contacts are linked to Accounts via the accountId field. We resolve the accountId reference during migration so that every Contact is attached to its parent Account before the Contact import phase completes.

Agillic Deals map to Nutshell Leads for unqualified prospect records and to Opportunities for qualified deals. If the Agillic Deal has an associated Company and a clear sales-readiness flag, we assess whether it maps to a Lead or to an Opportunity. For straightforward migrations where all Agillic Deals represent active sales opportunities, we map directly to Nutshell Opportunity records.

Agillic Deals with a defined stage and close date map to Nutshell Opportunity. Deal name maps to Opportunity.name, deal amount to Opportunity.amount, expected close date to Opportunity.promised_date, and deal stage to Opportunity.status. Nutshell's deal pipeline columns map to the Opportunity.status picklist values.

Agillic email engagement records (send, open, click, bounce) migrate to Nutshell Task records. Each Task carries the original Agillic activity type in task_type, the timestamp in due_date, and the recipient email in description. Nutshell's API does not store full email content — we migrate activity metadata and the activity description as a structured text note rather than as a full email message body.

Agillic call activity records map to Nutshell Task with task_type set to Call. Call duration from Agillic is stored in a custom Nutshell field call_duration__c. Activity timestamps migrate as due_date to preserve the activity timeline ordering against the parent Contact.

Agillic meeting activity records map to Nutshell Event. The event title migrates as name, the meeting start time as starts_at, and the end time as ends_at. Location data migrates to the Event's location field. Attendee lists from Agillic meeting records are stored in a custom notes field if the count is within Nutshell's field limits.

Agillic Flow Execution IDs and the associated campaign metadata (flow name, execution date, recipient count) are preserved in a structured custom field agillic_flow_executions__c on the Contact record. This maintains the cross-reference for teams that need to tie activity records back to specific Agillic campaign runs, even though Flows themselves do not migrate.

Agillic Global Data Tables (custom relational data structures used within Flows) are exported as schemas and row data, then mapped to Nutshell custom objects. We pre-create the destination custom object and fields in Nutshell via the API before importing data. The table-to-object mapping is documented during scoping, and the customer chooses whether to maintain the relationship structure or flatten it into custom fields on the Contact.