Migrate from Nielsen Marketing Cloud to HubSpot

Nielsen subscriber Data Extensions storing first name, last name, email, phone, and demographic fields map directly to HubSpot Contact properties. HubSpot requires an email address as the primary identifier — subscribers without email are flagged for manual review or suppression before migration.

Nielsen Data Extensions containing company name, domain, industry, and employee count map to HubSpot Companies. Parent-child company hierarchies in Nielsen map to HubSpot's parent company association via the parent_company_id field in the source Data Extension. If the source Data Extension includes additional properties such as address or revenue, we map those to corresponding HubSpot Company properties, preserving as much detail as possible.

Nielsen campaign Data Extensions containing spend, impressions, conversions, and attribution metrics require transformation. Campaign name becomes Deal name; spend maps to Deal amount or a custom field; campaign stage maps to a Deal pipeline stage via value mapping. We also handle multi-currency conversion if Nielsen stores spend in multiple currencies, applying exchange rates at migration time and storing the original currency in a separate field for reporting accuracy.

Nielsen audience segment membership stored per subscriber in a Data Extension is not a native HubSpot object. We generate HubSpot static lists from segment membership flags — each Nielsen segment becomes one HubSpot list populated with the matching contact email addresses. Dynamic lists with Nielsen behavioral rules require workflow recreation.

Nielsen behavioral event Data Extensions (page views, email opens, conversion events) have no direct HubSpot CRM equivalent. Events migrate as HubSpot custom contact properties (last_event_type, last_event_date) or as a custom object tracking event history. Full event timelines require HubSpot's Events API at additional configuration cost.

Nielsen's proprietary enrichment data — demographic appends, intent scores, and predictive indices — are bound to Nielsen's data infrastructure and cannot be exported as discrete records. We preserve enrichment field names as custom contact properties with null values as a rebuild reference for your HubSpot admin.

Nielsen's cross-device identity graph covering 6B+ devices is a Nielsen-only asset with no HubSpot equivalent. Device-to-email linkages used for audience targeting cannot be transferred. HubSpot's cookie-based tracking and email identity model replaces this capability on a per-session basis. Because the device graph is proprietary, we cannot export device-to-email mappings; however, we record the original device IDs in a custom property as a reference for future cross-device reconciliation using HubSpot's native cookie and email tracking.

Nielsen media planning Data Extensions containing media channel, placement, flight dates, and budget allocations require a HubSpot custom object (Media_Plan__c) with fields for channel, start_date, end_date, and budget. Campaign-linked plans associate via a lookup field to the destination Deal representing the campaign.

If Nielsen stores product reference data in a Data Extension, those records map to HubSpot Products. Product associations to campaign performance Data Extensions map to Line Items on the corresponding Deal, preserving the spend‑per‑product attribution model. We also map product categories and SKUs to HubSpot product properties, and if the source includes pricing, we create associated price books to maintain accurate revenue calculations in HubSpot's analytics.

Nielsen user records identifying campaign managers and data analysts map to HubSpot Users by email match. Unmatched Nielsen users are flagged and assigned to a fallback HubSpot owner, or your admin creates HubSpot user accounts before migration finalizes. We also capture each user's role and department from Nielsen, storing them as custom properties on the HubSpot User record for future reporting and task assignment clarity.