Migrate from Thryv to Pipedrive

Thryv's Client object maps directly to Pipedrive's Person. Standard fields — FirstName, LastName, Email, Phone, Address, Website — migrate cleanly. Custom fields on the Client record map to Pipedrive custom Person fields with type-matching (radio buttons and checkboxes from Thryv map to Pipedrive dropdown or multi-checkbox). We deduplicate by email during the load phase. The client's Thryv owner_id resolves to the Pipedrive user by email match.

Thryv's flat Company records map to Pipedrive Organizations. Thryv Companies can exist without a Contact, and Pipedrive Organizations can exist without a Person — the schema is compatible. We map company name, address, phone, website, and industry. Thryv custom fields on Company map to Organization custom fields in Pipedrive. The critical mapping step is linking any Thryv Client records to their associated Thryv Company so that the Organization is created before the Person insert, satisfying Pipedrive's org_id foreign key on Person.

Thryv Opportunities map to Pipedrive Deals. The Thryv pipeline stage name maps to the Pipedrive pipeline stage, and the pipeline assignment maps to a Pipedrive Pipeline. We flag any custom stage probabilities or closed-won/closed-lost reasons that require Pipedrive stage configuration before import. Deal value (monetary amount), expected close date, and stage status migrate directly. Pipedrive's rot feature (deal aging flag) is set to default on import — the customer's admin configures the rot threshold post-migration.

Each Thryv Opportunity pipeline maps to a Pipedrive Pipeline. Thryv stage names become Pipedrive stage names with probabilities mapped to Pipedrive's stage probability field. Pipedrive's pipeline model supports multiple pipelines from the Advanced plan upward, so we configure one pipeline for every Thryv pipeline found during scoping. Stage order is preserved from Thryv's configuration.

Thryv appointments carry date, time, duration, assignee, service type, and client association. We map these to Pipedrive Activity records with type=meeting for scheduled appointments and type=task for follow-up items. Appointment notes migrate as Activity subject and details. The assignee resolves to the Pipedrive user by email; the client resolves to the Person record by email match or name lookup. Recurring appointment series are flattened into individual Activity records per occurrence.

Pipedrive does not have a native Invoice object in its standard CRM tiers. We extract Thryv invoice records — line items, totals, payment status, and client association — as structured Note records in Pipedrive, linked to the corresponding Person and Deal. Invoice totals and paid/unpaid status are also recorded as custom fields on the Person or Deal for quick reference. The customer's admin should evaluate Pipedrive's invoicing add-on or a third-party app (like季Invoice) if invoice management is required as a native feature post-migration.

Thryv's freeform tagging on Client records migrates to Pipedrive Labels. Freeform tags are deduplicated and normalized during extraction — tags with identical names in different cases or formats are merged. Tags that represent lead status or segment are recommended for conversion to a single-select custom field rather than labels; the customer's admin decides the strategy during scoping. Labels migrate as a flat list assigned to the corresponding Person record.

Custom field limits vary by Thryv edition (100 for Pro, 150 for Max). We check the source account's edition and field count during scoping. All Thryv custom field types are supported in migration but require type-matching at the destination. Radio buttons, checkboxes, and drop-downs map to Pipedrive's equivalent field types. If the number of custom fields exceeds Pipedrive's practical UI threshold, we surface a priority list to the customer for manual selection.

Thryv communication history (sent emails, SMS threads, call logs) is accessible via API on Keap-tier accounts. We extract content and metadata and represent them as Activity records on the Person's timeline in Pipedrive. Email content migrates as Activity notes; SMS content migrates similarly. The customer's admin configures Pipedrive's email sync and SMS integration (via a Marketplace app like Telzio or Aircall) after cutover to resume live communication logging.

Thryv user records (name, email, role) map to Pipedrive users. We match by email during the import phase. Any Thryv owner referenced on a Client, Company, or Opportunity record without a matching Pipedrive user goes into a reconciliation queue for the admin to provision before migration proceeds. Pipedrive permission levels and team structures must be reconfigured manually post-migration.

Thryv's Automation Builder sequences (triggers, conditions, actions) are not accessible via API and cannot be migrated programmatically. We do not migrate workflows as code. During scoping, we run a pre-migration documentation sprint where we help the customer identify and record their most critical automations. We deliver a written automation inventory with trigger descriptions, conditions, and actions, plus a recommended Pipedrive workflow equivalent for each entry. The customer's Pipedrive admin rebuilds the automations post-migration using Pipedrive's Automation feature (available on Advanced and above).