Migrate from Act-On to Nutshell

Act-On Contacts map directly to Nutshell Person records. Standard fields (name, email, phone, address) transfer cleanly. We resolve the Contact's associated Company to a Nutshell Account during import and link Person.customFields.accountId to the corresponding Account. Lifecycle Stage from Act-On migrates to a custom field on Person so the customer's admin can use it for segmentation without losing the historical classification.

Act-On Companies map to Nutshell Account records. Company name, industry, and address fields transfer directly. We create Accounts first during migration so that Person-to-Account lookups resolve at the moment of Person insert. Custom company fields in Act-On migrate to Nutshell customFields on Account.

Act-On Lists are audience segments used for campaign targeting. We preserve List membership as Nutshell Person tags or a custom multi-select field depending on whether the List is static or dynamic. Static List membership (fixed contacts) maps to tags; dynamic List logic does not transfer and the customer rebuilds equivalent filters in Nutshell or Mailchimp.

Act-On Programs define multi-step nurture sequences. These workflow definitions are stored server-side and are not accessible via the API. We export the contact roster for each Program (who entered, when, what branch they followed) as a historical record, then deliver a written Program Blueprint that lists the steps, triggers, delays, and conditions for the customer's admin to rebuild in Nutshell or an external nurture tool.

Act-On calculates a behavioural engagement score per Contact using proprietary weighting across email opens, clicks, page visits, and form submissions. These calculation rules do not export. We migrate the current numeric score for each Contact as a custom numeric field on Nutshell Person (e.g., acton_engagement_score__c) as a static property. The customer must configure any new scoring logic in Nutshell manually after migration.

Act-On's Custom Data schemas define user-extended field structures on Contact and Company. We read the schema definition via Act-On's API, pre-create equivalent custom fields in Nutshell (under Person.customFields or Account.customFields), and import existing records with values written to those fields. Field types (text, number, date, currency) map to Nutshell's corresponding custom field types.

Act-On campaign email content and subject lines are accessible via API. We preserve campaign names and send history as Activity records attached to the relevant Person, or as tags indicating the last campaign received. HTML email body does not transfer as a usable asset in Nutshell because Nutshell is not an email marketing platform; we flag this as a reference record rather than a reusable asset.

Act-On web form definitions and submission data are accessible. Form field names and submission timestamps migrate as Activity records or custom fields on the relevant Person. The form embed code itself does not transfer and must be re-implemented in Nutshell or a separate form tool.

Email opens, clicks, form submissions, and other behavioural events logged in Act-On migrate as timestamped Activity records attached to the corresponding Nutshell Person. Volume can be large; we chunk by date range and apply backoff logic. The activity type (email_open, email_click, form_submit) maps to Nutshell Activity type and description fields.

Contact and Company tags from Act-On export cleanly as label arrays. We map them to Nutshell tags on the corresponding Person or Account record. Multi-value tags transfer as individual tag entries.