Migrate from Cision to Freshsales

Cision journalist contact records map to Freshsales Contact objects. We extract beat assignments, outlet affiliations, email addresses, phone numbers, Twitter handles, and LinkedIn profile URLs from the Cision media database. The contact's primary outlet maps to an Account record created first, with the contact linked via the Account Lookup. Social profile fields migrate to Freshsales custom contact properties. Active status and last-contacted date migrate as custom date fields. We preserve the Cision contact score as a custom numeric field for teams that used Cision's media targeting scoring.

Cision outlet records (publication name, type such as print/digital/broadcast, geography, beat coverage) map to Freshsales Account records with Account Type set to 'Media Outlet' to distinguish from commercial Accounts. Outlet contact relationships within Cision migrate as Contact records linked to the Account. Beat coverage tags from Cision migrate as custom multi-select picklist values on the Account record.

Cision media lists curated for targeted pitching migrate as Freshsales Lists. We export list membership (contact associations and custom list metadata such as list description, segment tags, and custom fields), then reconstruct the list structure in Freshsales. List membership resolves to Freshsales Contact records via email deduplication before list assignment.

Press release distribution records including wire tier (Basic/Standard/Advanced/Premium), distribution scope, recipient list size, open/click metrics, and release date have no native Freshsales equivalent. We create a custom object named 'Press Release' with fields for wire tier, distribution_date, recipient_count, open_rate, click_rate, and associated Contact records. Press release content body migrates as a long-text custom field. The wire distribution itself does not transfer; the custom object holds performance metadata only.

Cision PR campaigns (grouping releases, pitches, and coverage mentions) map to Freshsales Deal records with a custom field campaign_type__c set to 'PR Campaign'. Campaign attributes including name, date range, status, and linked contacts migrate. Multiple Cision campaign records that share the same PR initiative merge into a single Freshsales Deal for pipeline tracking. The Deal's associated Contacts are resolved via email lookup from the campaign's contact list.

Monitored coverage records (article title, outlet, publication date, tone/sentiment, reach estimate, associated tags) migrate to a custom object named 'Coverage Mention'. We run deduplication logic on export to collapse duplicate articles under slightly varying titles, flagging records with incomplete outlet metadata for customer review before load. Tag associations migrate as multi-select values on the custom object. The full article body migrates as a long-text field if the customer's license tier supports it; otherwise, the article URL is preserved as the primary reference.

Social monitoring data from the Brandwatch integration (social mentions, engagement metrics, platform attribution) migrates to a custom object named 'Social Mention' with fields for platform, post_url, engagement_count, sentiment, and mention_date. Brandwatch-specific metadata (trend score, audience demographics, share of voice indices) that has no Freshsales equivalent is documented in the handoff notes for the customer's admin to decide whether to create additional custom fields. This object is only in scope if the customer actively uses Brandwatch within CisionOne.

Cision user accounts (name, email, role, workspace assignments) map to Freshsales User records. We resolve by email match. Workspace-based access controls that differ from Freshsales's role-based security model are documented in the handoff notes for the customer's admin to reconfigure in Freshsales Admin Settings. Suspended or inactive Cision users migrate as inactive Freshsales Users for historical record ownership consistency.