Migrate from Tribune to Zoho Recruit

Tribune subscriber records map to Zoho Recruit Candidate objects as the primary identity translation. We map subscriber name to Candidate First Name and Last Name, email to Email, phone to Phone, and delivery address to Candidate address fields. Tribune's subscriber_id becomes a custom field tsa_subscriber_id__c preserved for audit traceability. Records without a last name require a 'not provided' value per Zoho Recruit's mandatory Last Name requirement during import.

Tribune Publishing's 77 daily and 150 weekly publications create a many-to-many relationship with subscribers (a subscriber may hold entitlements to multiple titles). We map these as Zoho Recruit Tags attached to each Candidate record, with one tag per publication title. Alternatively, for cleaner filtering, we create a multi-select picklist field publication_entitlements__c if the Standard or higher tier is in use. The customer selects tag versus picklist strategy during scoping.

Tribune subscription tiers (print-only, digital-only, bundled) map to a custom picklist field subscription_tier__c on the Candidate object. We create the picklist values during schema setup before import. Tier pricing and rate information does not have a native Zoho Recruit equivalent; we note this as a manual rebuild item for billing teams and preserve rate information in a text field subscription_rate__c for reference.

Tribune billing records (payment method type, billing frequency, transaction history) have no native Zoho Recruit equivalent because Zoho Recruit is an ATS, not a billing or subscription management platform. We migrate the last four transaction dates and payment method type as custom text fields (billing_frequency__c, last_payment_date__c) on the Candidate record. Full billing history and auto-renewal status require a separate billing system or spreadsheet; Zoho Recruit does not support financial transaction records.

Tribune print delivery addresses map to Zoho Recruit Candidate address fields (street, city, state, zip, country). We preserve the full address history and flag records with active temporary forwarding instructions as a custom checkbox has_forwarding__c. Seasonal address changes are retained as additional address records in a custom related list structure if the Enterprise tier is in use; otherwise, the most recent active delivery address is migrated as the primary.

Tribune auto-renewal flags map to a custom checkbox field auto_renewal_active__c on the Candidate. Records with auto-renewal enabled and a promotional effective date are flagged during import scoping so the customer can audit which migrated subscribers will trigger automatic renewal events. Zoho Recruit does not process billing or auto-renewal; this flag serves as a reference for the customer's billing team.

Tribune delivery frequency preferences (daily, weekends, selected days), format preferences, and notification opt-ins map to custom fields on the Candidate object. We create delivery_frequency__c (picklist), format_preference__c (picklist: print, digital, both), and notification_opt_in__c (checkbox) during schema setup. Where equivalent Zoho Recruit fields do not exist, we configure custom fields before migration.

Tribune digital subscriber access credentials (online portal login entitlements) map to a custom text field digital_access_tier__c on the Candidate record indicating the access level held. Full credential migration (username, password) is not performed because Zoho Recruit does not manage subscriber authentication. The access tier indicator preserves the entitlement classification for the customer's admin to reconcile against their portal system post-migration.

Each Tribune subscriber can hold entitlements to multiple publication titles across the 77 daily and 150 weekly portfolio. We decompose this relationship during migration by creating one Candidate record per subscriber and attaching one tag per publication title the subscriber holds entitlements for. This preserves the full portfolio relationship in Zoho Recruit's tagging system for filtering and reporting purposes.

Tribune internal staff records managing subscriber accounts (if present in the source data) map to Zoho Recruit User records by email match. Any Tribune owner without a matching Zoho Recruit User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Zoho Recruit Standard and above support Department Hierarchy for org structure mapping.

Zoho Recruit's Job Openings module has no Tribune source equivalent since Tribune is a media publisher. We configure the Job Openings module during migration setup as a new structure for the customer's recruiting workflow. Job Openings limits scale from 1 active job on Forever Free to 750 active jobs on Enterprise, matching the customer's planned hiring volume.

For staffing agencies migrating from Tribune to Zoho Recruit, the Clients module provides organizational tracking for hiring companies. We configure Client and Client Contact records as new structures post-migration. Client portals ($6/license/month add-on) are available for agencies wanting a client-facing interface; this is an optional configuration outside standard migration scope.