Migrate from ActiveCampaign to Nutshell

Deal notes are not exportable from ActiveCampaign

ActiveCampaign's deal export API and CSV export do not include deal notes. This is a documented platform limitation. During scoping, we identify all Deals that contain notes and present the customer with two options: extract notes via a workaround if ActiveCampaign's internal export method is accessible, or acknowledge that deal notes will not transfer. If the customer has deal notes that contain critical context (negotiation history, objections, terms discussed), we recommend exporting a screenshot-based archive before migration cutover. Nutshell supports deal notes natively, but we cannot import them programmatically from ActiveCampaign.

Automations cannot be migrated to Nutshell

ActiveCampaign does not expose automation workflow definitions via its public API for export. The only migration path for automations is to manually rebuild them in Nutshell by referencing screenshots or documentation of the original automation logic. We do not import automation JSON because it is not accessible. We deliver a written inventory of every active ActiveCampaign automation with its trigger conditions, action steps, and recommended Nutshell equivalent (manual workflow, rule, or integration-based automation), and the customer's admin rebuilds them post-migration.

ActiveCampaign custom objects have no native Nutshell equivalent

ActiveCampaign custom objects (available on Enterprise tier or with the Pipelines/Sales Engagement add-on) define custom field schemas associated with standard objects. Nutshell does not have a native Custom Objects feature at the same level of abstraction. During scoping, we identify every ActiveCampaign custom object and its relationship to standard objects. Options include: mapping custom object records to Nutshell custom fields on the parent record, using Nutshell's custom fields with a JSON-encoded data field, or accepting that the custom object schema is not migratable and documenting the gap for admin review.

Contact-based pricing affects scoping and planning

ActiveCampaign's November 2025 pricing change now counts all contacts including unsubscribes, bounces, and unconfirmed records toward the contact limit. This means the billable contact count in ActiveCampaign may be significantly higher than the number of active, emailable records. When scoping the migration, we count the full contact footprint including suppressed records so the customer understands both the migration scope and the potential cost reduction opportunity: archiving or cleaning suppressed contacts before migration reduces the Nutshell plan requirement since Nutshell charges per user, not per contact.

Email templates and campaign history do not migrate

ActiveCampaign email templates and campaign send history (opens, clicks, bounces, unsubscribes per campaign) are not migratable as a data set. Template HTML can be exported but requires manual reformatting in Nutshell's template editor. Campaign history is a reporting artifact that lives inside ActiveCampaign; Nutshell's reporting focuses on Deal pipeline metrics and sales activity rather than marketing campaign attribution. We do not migrate email templates or campaign history. We recommend the customer export historical campaign performance reports from ActiveCampaign as CSV for archival purposes.