Migrate from Adobe Campaign to Nutshell

Adobe Campaign's nms:recipient schema maps to Nutshell People. Standard fields (email, first name, last name, format preference, address) migrate directly. Extended custom fields from the nms:recipient extension schema migrate to Nutshell custom columns on People. We flag every Recipient with a suppression or inactive status for Nutshell's contact-level opt-out mapping to prevent post-migration email delivery issues.

Adobe Campaign broadlog records track every message sent. Nutshell has no native delivery log equivalent, so we surface a summary as custom fields on the linked People record: last_email_sent_date, last_delivery_status, and total_sends_count. We compute these from broadlog aggregation during the transform phase so the activity timeline carries campaign attribution context without requiring a separate object.

NmsTrackingLog records with click URLs and timestamped open/bounce events migrate as Nutshell activities attached to the corresponding People record. Each tracked click event becomes a Note or custom activity entry with the URL and timestamp. Aggregate open and click rates are noted as custom fields; Nutshell's native email tracking handles future opens and clicks post-migration.

Campaign labels, dates, type, and status migrate as a custom text field (campaign_name) and date field (last_campaign_date) on the linked People record. Nutshell's native Activities capture meetings and tasks; campaign metadata attaches as reference context. We do not recreate the hierarchical program-campaign-delivery structure because Nutshell's CRM model does not support multi-level campaign containers.

Adobe Campaign account or custom account schema records map to Nutshell Companies. The account name maps to company name, domain maps to website, industry maps to a custom picklist or free-text industry field. We dedupe by domain during import to merge accounts that appear across multiple campaign targeting lists.

Adobe Campaign service subscriptions (opt-in lists) map to Nutshell People as boolean or multi-select fields: email_opt_in, sms_opt_in, push_opt_in. Subscription date and confirmation status preserve as date fields. Double-opt-in confirmation flags may need value mapping depending on the customer's consent capture process.

Seed addresses are internal Adobe Campaign testing records instance-specific to the delivery routing configuration. They are not portable across platforms. We do not migrate seed addresses and recommend recreating test lists as Nutshell test People records or suppression lists post-migration.

Custom tables created via nms:ext: namespace or FDA-linked external schemas require schema XML inspection to derive the underlying SQL table structure. We inspect the schema XML, map each extended field to an equivalent Nutshell custom column (with type matching), and pre-create the custom fields before data import. FDA-linked schemas require a separate extraction step against the external database before mapping.

Adobe Campaign targeting workflows, campaign workflows, and technical workflows export as XML packages. Dynamic content blocks and queryDef expressions frequently break across ACS-to-ACC migrations and cannot be reliably mapped to Nutshell's workflow rules. We do not migrate workflows as code. We deliver a written inventory of every active workflow with its trigger, conditions, and actions, plus a recommendation for rebuilding equivalent automation in Nutshell or a connected integration.

Adobe Campaign control groups (exclude populations) are stored as query definitions linked to deliveries. We extract the exclusion criteria and reapply them as a tag (control_group) or boolean field (is_control) on the People record so the customer's admin can reference the original targeting logic when rebuilding campaigns in Nutshell.