Migrate from Tribune to Crelate

Tribune Subscriber records (name, email, phone, delivery address) map to Crelate Contact. The subscriber's Tribune subscription tier and publication preferences migrate as Crelate custom fields (text picklists and multi-select fields) since Crelate Contact has no native subscription property. Auto-renewal flags and promotional rate effective dates also become custom fields requiring manual audit by the customer's billing team post-migration. Subscriber deduplication runs before import to merge records sharing the same email address.

Tribune's 77 daily and 150 weekly publication titles have no direct Crelate equivalent. We map the publication-to-subscriber many-to-many relationship as a Crelate multi-select custom field on Contact (e.g., publication_subscriptions__c) with one picklist value per active publication title. Customer admins configure the picklist in Crelate Settings before import. Historical publication counts per subscriber become numeric custom fields.

Tribune subscription tiers (print-only, digital-only, bundled) have no Crelate native equivalent. We map tier names and current rate to Crelate custom text and currency fields on Contact (subscription_tier__c, subscription_rate__c). Promo-to-standard renewal transitions are preserved as date fields (promo_expiration_date__c) so billing teams can identify which migrated subscribers will trigger automatic rate changes in the source system post-cutover.

Tribune billing records (payment method type, billing frequency, transaction history) have no Crelate native billing object. We attach billing summary records as Crelate Note records linked to the parent Contact, flagging the Arnold class action billing inconsistencies (overcharge line items) for manual customer review. Payment card data is tokenized or masked in Tribune and cannot be migrated; we note the last payment method type only. Full billing history requires manual export from Tribune's billing system separate from the Crelate migration scope.

Digital subscriber access credentials (portal username, access tier) link to the subscriber record in Tribune but have no Crelate credential or identity object. We attach a credential summary as a Crelate Note linked to the Contact with the access tier preserved as a custom picklist field (digital_access_tier__c). Full credential migration is not attempted because Tribune digital access infrastructure is proprietary and not transferable to Crelate's platform.

Print delivery addresses migrate directly to Crelate Contact address fields (mailing street, city, state, postal code, country). Temporary or seasonal forwarding instructions preserved as Crelate custom date fields (temp_forwarding_start__c, temp_forwarding_end__c) and a text field (forwarding_address__c). Addresses flagged with active temporary forwarding are noted in the migration reconciliation report for the customer's operations team to action before print cutover.

Delivery frequency (daily, weekends, selected days), format preferences, and notification opt-ins map to Crelate custom fields (delivery_frequency__c, format_preference__c, notification_opt_in__c). These are configured as picklist fields in Crelate Settings before import. Any opt-out preferences migrate to Crelate's native email opt-out fields (has_opted_out_of_email) for compliance.

Tribune group enterprise subscriptions (corporate, university, library accounts) require a split mapping. The enterprise entity maps to a Crelate Company record; individual subscriber contacts under that enterprise map to Crelate Contacts with the Company Lookup set. We extract the group hierarchy from Tribune's subscriber export and reconstruct it as Company-Contact relationships in Crelate. Group pricing tiers and contract terms become Company custom fields.

Auto-renewal flags from Tribune are preserved as Crelate Contact custom fields (auto_renewal_enabled__c, promo_rate_effective_date__c). These are migration-scope flags only; Crelate has no billing automation to act on them. The customer's billing team receives a report of all auto-renewal-enabled records with their renewal dates so that they can manage source-system cancellations or rate transitions before cutover.

Tribune Publishing is classified as an HRMS in this migration setup but holds no employee records, org chart, or HRMS objects. Tribune is a media publisher. No HR data exists in this source system. We confirm zero employee records at project kickoff and document the absence in the migration scope sign-off.

Tribune's subscriber management does not include workflow automation, sequence cadences, or recruitment pipeline triggers. No automation rebuild is required. Crelate automation and sequencing features (Business Plus and Enterprise) are available for the customer's admin to configure independently post-migration.

Tribune subscriber reports and publication analytics have no Crelate equivalent in the recruiting data model. We deliver a written inventory of all identified Tribune reports with their column sets and filter logic so the customer's admin can rebuild equivalent Crelate reports or export to a BI tool. Crelate Advanced Reports and Analytics are available at Business tier and above.