Migrate from Tribune to Recruit CRM & ATS

Tribune Subscriber records (name, email, phone, address) map to Recruit CRM Candidate records. We use first_name and last_name from the subscriber name field, email_address to the email field, and map the delivery address into the Candidate address fields. The subscriber_id is preserved as a custom field src_subscriber_id__c for audit and cross-reference. Any subscriber with no name is flagged for manual review before import.

Tribune's 77 daily and 150 weekly publication titles have no direct Recruit CRM equivalent. We map publication entitlements as a multi-select picklist or tag field on the Candidate record. Each subscriber's publication list (many-to-many in Tribune) becomes a pipe-delimited or comma-separated value in the custom field, or multiple tag records if the destination supports tagging. The customer decides during scoping whether to flatten publications into one field or suppress them entirely if irrelevant to the recruitment use case.

Tribune subscription tiers (print-only, digital-only, bundled) map to a custom picklist field subscription_tier__c on the Candidate record. Tier names are preserved verbatim. Since Recruit CRM has no native subscription concept, the tier value is informational in the candidate profile. We flag any non-standard tier name for renaming during scoping.

Tribune billing records (payment method, billing frequency, transaction history) cannot map into Recruit CRM's Candidate or Contact objects natively. We map payment method type (card, ACH, invoice) and billing frequency as custom fields billing_method__c and billing_frequency__c. Transaction history and billing amounts migrate as a Note attached to the Candidate with a formatted billing history table, or as a JSON blob in a long-text custom field for programmatic access. Full billing reconciliation requires the customer's billing team review post-migration.

Tribune auto-renewal flags map to a boolean custom field auto_renewal_active__c on the Candidate. We flag records where auto_renewal_active equals true AND the effective_date is a promotional rate, since those will convert to standard rates at renewal. The customer receives an auto-renewal audit report as part of migration deliverables so the billing team can assess exposure before or after cutover.

Tribune digital access credentials (online portal login, access tier) map to a text custom field portal_access_tier__c. Full credential migration is not possible since Tribune's portal credentials cannot be exported in plaintext. We preserve the access tier label as a reference field and note that the subscriber will need to reset credentials in the destination system.

Tribune delivery addresses (street, city, state, zip, country) map 1:1 to the Candidate address fields in Recruit CRM. We flag records with active temporary forwarding instructions or seasonal addresses for manual review. Print delivery-specific address notes (e.g., doormail, locker) are preserved in a custom address_note__c field since Recruit CRM's standard address fields do not support delivery instructions.

Tribune delivery frequency preferences (daily, weekends, selected days), format preferences (print vs. digital), and notification opt-ins map to custom fields delivery_frequency__c, format_preference__c, and notification_opt_in__c. Where Recruit CRM has equivalent standard fields we use those; otherwise we create custom fields during import scope.

Recruit CRM requires Company records for client organizations in the recruitment CRM model. If the Tribune migration includes corporate or group subscription accounts (enterprise clients, universities, libraries cited in Tribune's product description), we extract those as Company records in Recruit CRM with the group subscriber name as company_name. Individual subscribers without a company linkage become Candidates without a Company association.

Recruit CRM's Job object has no Tribune equivalent since Tribune is a subscriber system, not a job posting system. We do not create placeholder Job records. If the customer has internal job openings data in a separate system, we document that as out-of-scope and note it as a separate migration engagement. The customer creates Job records manually post-migration or imports from their ATS if one existed.

Recruit CRM's bulk import supports field mapping but does not run automatic deduplication at import time. We pre-process Tribune subscriber records to detect duplicates by email address and by name+address combination before generating the import CSV. Duplicate records are flagged in a reconciliation report and the customer decides which subscriber_id to retain. This step is required given Tribune's high-volume subscriber base.

Tribune subscription start_date, renewal_date, and cancellation_date migrate as custom date fields on the Candidate record (subscription_start__c, renewal_date__c, cancellation_date__c). These preserve the subscriber's tenure history but do not affect Recruit CRM's native sorting or pipeline logic, which is driven by candidate stage and activity date rather than subscription tenure.