Migrate from Nielsen Marketing Cloud to Twenty CRM

Nielsen Consumer Profiles represent the unified view of an individual across devices and data sources. We migrate profile records as Twenty People objects. Each profile's identifier, name, email, phone, and demographic attributes map to the corresponding standard fields in Twenty's Person object. Attributes that do not have a direct standard field in Twenty (such as lifestyle indicators or behavioral scores from Nielsen enrichment) are stored as custom fields on the Person object, which we pre-create in Twenty's Data Model before import. Profiles that relied on device graph linkage for cross-device identity consolidation are flagged — the device linkage itself cannot migrate, but the individual profile attributes transfer as isolated records.

Nielsen Audiences are segment definitions built from first-party and third-party data sources. We assess the Audience schema — membership criteria, data source references, and segment size — and map it to Twenty's custom object model or to the tag system depending on complexity. Simple behavioral segments (e.g., 'purchased in last 30 days') map to Tags on the Person object. Complex multi-criteria segments with nested conditions are modeled as a Custom Object named AudienceSegment with fields for segment name, criteria (stored as JSON or text), source data, and creation date. The customer chooses the strategy during scoping.

Nielsen Campaigns represent activated audience segments sent across marketing channels. We migrate campaign metadata — name, status, targeting criteria, channel assignments, and scheduling — as Twenty Opportunity records (for revenue-tracked campaigns) or as Note records attached to the relevant Person records (for awareness campaigns). The mapping decision depends on whether the campaign has a budget and revenue target. Nielsen campaign targeting criteria (audience segment references, channel configurations) are preserved as custom fields on the Opportunity or as linked Note content.

Nielsen Data Sources represent ingest connections for first-party, second-party, and third-party data. We preserve source configuration metadata — source type, connection parameters, last sync timestamp, and record count — as a custom object named DataSource in Twenty. The raw data from these sources migrates as People records or as Audience segments depending on data type. Third-party enrichment layers attached to Data Sources are flagged as non-portable and noted for the customer's admin to reconstruct through alternative data partnerships or clean-room solutions.

Nielsen Content Assets include creative files, email templates, and messaging content. We export available content assets in bulk via structured file export and assess file type and size for migration. Email template content migrates as Twenty Note records with the body preserved as rich text. Binary assets (images, PDFs) are catalogued in a custom DataSource object pointing to the asset URL or file location, and the customer's team reassembles the asset library in their chosen creative management tool post-migration. Asset metadata (persona mappings, usage history) migrates as tag associations on the relevant Person records.

Nielsen Reports and Analytics exports include pre-built dashboard definitions and historical campaign performance metrics. We export the report structure and available data fields. However, Nielsen's pre-built analytics dashboards cannot be replicated in Twenty because Twenty's reporting is workspace-level views rather than campaign-attribution analytics. We deliver a written report inventory documenting each Nielsen report's metrics, filters, and data sources so the customer's admin can rebuild the most critical reports as custom views or connect to a BI tool for advanced analytics. Historical metric values (impressions, CTR, conversion) are stored as custom fields on the related Campaign Opportunity or as a standalone AnalyticsReport custom object.

Nielsen Media Plans define channel strategy, budget allocation, and scheduling for audience activation. We migrate Media Plan records by extracting budget amounts, channel assignments, and audience segment associations and merging them into the corresponding Campaign Opportunity record as custom fields (channel, budget_amount, scheduled_start, scheduled_end). Cross-platform budget allocation percentages are stored as a JSON custom field or as child records in a MediaBudgetLineItem custom object. If the customer has no direct Campaign Opportunity record for a given Media Plan, we create a standalone Opportunity record with a MediaPlan tag.

Nielsen user accounts with assigned roles, permissions, and data access scopes export as a user directory. We map Nielsen permission profiles to Twenty's role model (Admin, Editor, Viewer) and create workspace members accordingly. Note that Twenty's permission model is workspace-level rather than object-level; granular data access scopes that exist in Nielsen (field-level visibility, data source restrictions) are noted for manual configuration post-migration. Users without an email match in Twenty are held in a reconciliation queue for the customer's admin to provision.

Nielsen maintains one of the largest global device graphs covering over 6 billion devices for cross-device identity resolution. This graph is entirely proprietary to Nielsen and cannot be exported or replicated. Consumer Profiles that relied on device graph linkage are migrated as individual records without cross-device associations. We flag every Consumer Profile that had device graph linkage in the pre-migration audit and document the linkage loss in the handoff report. The customer may establish alternative ID resolution (probabilistic ID, clean-room partnership) as a separate initiative post-migration.

Nielsen's third-party behavioral and demographic enrichment layers — including offline, mobile, and streaming behavioral signals — are contractually restricted from export. Any Consumer Profile attribute that originated from third-party enrichment (demographic推断, lifestyle scores, purchase propensity models) cannot migrate. We document which profile fields are Nielsen-enriched in the pre-migration audit and advise the customer to populate those fields through alternative enrichment providers (e.g., Clearbit, FullContact) post-migration via Twenty's GraphQL API.