Migrate from Thryv to Salesforce Sales Cloud

Thryv Clients are the primary contact object with no separate Lead concept. We split at migration time based on opportunity association: Clients with no linked Opportunities map to Salesforce Lead; Clients with one or more Opportunities map to Salesforce Contact with AccountId resolved from the Company. We preserve the original Thryv Client ID in a custom field thryv_client_id__c for audit. Email, phone, address, and standard fields migrate directly; custom fields map 1:1 with type matching (text, number, date, checkbox, dropdown).

Thryv's flat Company structure maps to Salesforce Account. Company name, address, phone, website, and custom fields migrate directly. If the source account has a Company hierarchy or parent-subsidiary relationship (defined via a custom field or tag), we attempt to reconstruct this as Salesforce Account hierarchy by matching parent Company name to Account name. Single-level flat accounts import as standalone Account records without a parent.

Thryv Opportunities map to Salesforce Opportunity. The Opportunity name, monetary value, close date, and stage map to Opportunity.Name, Amount, CloseDate, and StageName. Thryv stage values are mapped to Salesforce StageName values via a lookup table configured during scoping. Stage probability percentages migrate to Salesforce StageProbability. The Opportunity.LeadSource maps from Thryv's lead_source property if present.

Thryv pipeline stages (defined per deal pipeline) map to Salesforce Sales Processes. Each Thryv pipeline becomes a Salesforce Record Type on Opportunity, with a corresponding Sales Process that whitelists the relevant stage values. We configure the Sales Process in a Sandbox before production migration.

Thryv Appointments map to Salesforce Event records. Appointment date, time, duration, service type, assignee, and client association migrate directly. The assignee maps to a Salesforce User via email lookup. The client association resolves to the migrated Contact or Lead WhoId. Recurring appointment series are flattened into individual Event records with the recurrence pattern preserved as a custom field.

Thryv Invoices contain line items, totals, payment status, and client associations. We create a custom Invoice__c object in Salesforce with fields for InvoiceNumber, InvoiceDate, DueDate, TotalAmount, BalanceDue, and Status. Line items migrate as InvoiceLineItem__c records linked to Invoice__c. Payment status (paid, unpaid, partial) preserves as a custom field; full transaction history exports without the ThryvPay merchant account relationship.

Thryv freeform tags on Client records are collected, deduplicated, and normalized during scoping. We create a custom Multi-Select Picklist field on the migrated Lead or Contact (or a Custom Text field if tag count exceeds Salesforce's 500-value picklist limit). Tag normalization handles case differences, singular/plural variants, and typographical variations before import.

Thryv custom fields on Client, Company, and Opportunity migrate to Salesforce custom fields of equivalent type. Radio buttons and drop-downs map to Salesforce Picklist; checkboxes map to Checkbox; dates map to Date; numbers map to Number. Text fields map to Text or Long Text Area depending on length. We verify the destination Salesforce edition's custom field limits during scoping; Salesforce editions have higher limits than Thryv so this is rarely a blocker.

Thryv user records (name, email, role) map to Salesforce User records. We resolve by email match against the destination org's User table. Staff/Owner role maps to a custom Salesforce Role field or to the standard UserRole if hierarchy mapping is required. Any Thryv user without a matching Salesforce User goes to a reconciliation queue for admin provisioning before record import proceeds.

Thryv communication history (emails, SMS threads, call logs) is accessible via API for Keap-tier accounts. Email logs migrate as Salesforce Task records with body content; SMS threads migrate as Task records with a custom sms_thread__c field. Call logs migrate as Task records with TaskSubtype=Call and CallDisposition preserved. Communication history is linked to the migrated Contact or Lead WhoId.

Thryv website form submissions are stored as structured records with date, client name, contact info, and custom form fields. These migrate as Salesforce Lead records with the form submission date, all custom field responses mapped to custom Lead fields, and a custom field thryv_form_source__c indicating the original form name. Unqualified leads remain as Leads for sales team qualification.

Thryv Automation Builder sequences (triggers, conditions, actions) are not accessible via API and cannot be migrated programmatically. We conduct a pre-migration documentation sprint where we extract and record every active automation with its logic, triggers, conditions, and actions. The output is a written inventory document delivered to the customer's admin for rebuild in Salesforce Flow post-migration. This is not included in data migration scope.