Migrate from Cision to Twenty CRM

Cision's journalist database (1.4M+ contacts) maps to Twenty People records. We extract contact details including name, email, phone, outlet affiliation, beat assignments, social profiles, and Cision's contact tier flags. Beat assignments and outlet relationships map to Twenty's workspace and tag fields. Any Cision-specific scoring or engagement data migrates as custom fields. Email addresses are used as the dedupe key during import.

Cision outlet records (publication name, type, geography, beat coverage, contact relationships) map to Twenty Company records. Outlet type (print/digital/broadcast) maps to a custom select field. Geographic coverage maps to Company address fields. The Company record acts as the parent for journalist People records linked via the outlet relationship, enabling outlet-centric views in Twenty.

Cision distribution lists (curated media lists for targeted pitching) map to a Twenty custom object. Each list gets a Distribution List record with name, description, and date created, and list membership links to People records via a many-to-many relationship object. We extract list metadata and all contact associations and reconstruct the list structure in Twenty as a custom object with People relationship records.

Monitored coverage records from CisionOne (article metadata, outlet, tone/sentiment, reach estimates, tags) map to a Twenty custom object called Coverage. Article title, URL, publication date, outlet (linked Company), sentiment, reach, and tag associations migrate. We run deduplication on mention records before import to address Cision's duplicate article issue flagged in G2 reviews. For lower-volume accounts, coverage records may map to Note objects linked to the related Outlet Company.

Cision PR campaigns (grouping press releases, pitches, and coverage mentions) map to Twenty Opportunity records. Campaign name, date range, status, and linked contacts migrate. The Opportunity model works for campaign-centric tracking even though Cision campaigns serve a different workflow than sales opportunities; the customer may rename Opportunity to Campaign in Twenty's workspace label configuration.

Press releases from PR Newswire (content, distribution history, recipient lists, wire tier, open/click metrics) map to a Twenty custom object or Note records. Distribution tier, recipient count, and performance metrics (opens, clicks) migrate as custom fields. The wire distribution itself does not transfer (PR Newswire remains a separate service), but the release metadata and performance data give the comms team a historical record in Twenty.

Brandwatch social monitoring data (social mentions, engagement metrics, trend data) maps to a Twenty custom object or Task records with platform attribution (Twitter/X, LinkedIn, Instagram). Platform, post URL, engagement counts, and timestamp migrate. Brandwatch-specific metadata that does not map to standard Twenty fields becomes custom fields on the Social Engagement custom object.

Cision user accounts (name, email, role, workspace assignments) map to Twenty Members. We extract active users and map role assignments to Twenty workspace permissions. Cision's workspace-based access controls may require restructuring in Twenty's workspace and permission model, which we document during scoping.

Any custom fields on Cision journalist records (beat tags, tier classifications, engagement scores, notes) map to custom fields on the Twenty People object. We pre-create these fields in Twenty's data model (Settings -> Data Model) before importing People records so that the CSV import populates them correctly.

Cision monitoring alert configurations and saved search parameters use Cision's proprietary schema and are not exportable. We document the alert criteria (keywords, filters, date ranges, notification settings) during the discovery call and deliver a written alert inventory for the customer's admin to rebuild manually in Twenty. This is explicitly a documentation-only step, not a data migration.