Migrate from Adobe Campaign to HubSpot

Adobe recipient records migrate 1:1 to HubSpot contacts. The @email field maps to HubSpot's email property. NmsRecipient is the core contact table in Adobe; its custom extension fields (cus:* namespace) map to HubSpot custom properties. HubSpot lifecycle stage is assigned based on Adobe @blacklist status and last delivery event.

Adobe's company extension schema (if present) maps to HubSpot companies. Adobe allows N:N recipient-to-company associations; HubSpot supports one primary company per contact plus additional Company Contact Relationships. We preserve all associations and surface them in HubSpot's association panel. During migration, we evaluate each recipient's company associations to determine which becomes the primary company, while preserving secondary associations through the relationship model to maintain data integrity.

Adobe campaign objects don't have a direct HubSpot equivalent. Each Adobe campaign becomes a HubSpot deal record, with the deal name derived from NmsCampaign @label. Campaign metadata (internal name, channel type) is preserved in deal custom properties. Campaign targeting and audience data is stored as a custom property reference for rebuild in HubSpot lists.

Adobe deliveries are distinct from campaigns. Each delivery's aggregate metrics (send count, open count, click count, bounce count) are stored as HubSpot deal-level custom properties. Delivery-level HTML content migrates as a file attachment on the associated deal record. Individual recipient delivery events live in broadlog (see broadlog mapping).

Broadlog tables store per-recipient delivery events (sent, failed, quarantined, opened, clicked). We aggregate broadlog event data into per-contact custom properties (Last_Send_Date__c, Open_Count__c, Click_Count__c, Bounce_Flag__c) and surface the most recent send engagement as a timeline entry. The granular per-event history is collapsed to avoid creating thousands of activity rows.

Adobe service subscriptions (opt-in lists) are complex objects with subscription date and status. We migrate active subscriptions as a HubSpot contact-level opt-in property and, if multiple services are used, as a HubSpot custom object (Subscription) linked to contacts via a custom association. Unsubscribed status maps to HubSpot's email opt-out field.

Adobe seed addresses are test contacts used for delivery previews. We migrate seed addresses as HubSpot contacts tagged with Seed_Address__c = true. Seed addresses that are also on the suppression list are migrated to HubSpot's suppression list directly. This prevents test contacts from entering the live marketing pipeline.

Adobe Campaign custom schemas extend the recipient table with custom attributes and related tables. Each cus:* extension schema maps to a set of HubSpot custom properties on the Contact object. Related (linked) custom schemas map to HubSpot custom objects with their own schema and a custom association to the Contact. The XML schema definition is reviewed to ensure HubSpot property types match (string, number, date, Boolean, enumeration).

Adobe delivery templates store the HTML structure and personalization tokens used across campaigns. We export template HTML as files and attach them to the relevant deal or company record. Adobe personalization tokens (@context.nms.recipient.fieldName) must be manually reconfigured to HubSpot token syntax (e.g., {{contact.fieldname}}) — we flag each token location in the export.

Adobe Campaign workflows are JavaScript-based orchestration pipelines with targeting, query, enrichment, and delivery activities. These do not migrate to HubSpot. We export each workflow definition as a structured JSON specification documenting the trigger conditions, audience logic, delivery actions, and timing rules. This package is handed to your HubSpot admin as a rebuild reference for HubSpot workflow automation.

Adobe Campaign built-in reports (delivery tracking, campaign performance, tracking indicators) and custom dashboards do not migrate. Underlying data (delivery metrics, broadlog aggregates) migrates to HubSpot deal custom properties and contact custom properties, which can be used to rebuild reports in HubSpot's reporting tools.

Adobe tracking logs aggregate URL-level click data per recipient. We extract the most recent tracked URL and click count per contact and store them as HubSpot custom properties (Last_Tracked_URL__c, Click_Count__c). Full URL-level tracking history is exported as a CSV for reference but not imported as individual records in HubSpot.