Migrate from Thryv to Twenty CRM

Thryv Clients map directly to Twenty People records. Standard fields (firstName, lastName, email, phone, address) migrate cleanly via CSV or REST. Custom client fields map to Twenty custom fields on the Person object. The migration user must pre-create any custom fields in Twenty Settings > Data Model before import; fields do not auto-create from CSV. Tags assigned to clients convert to multi-select picklist values on a tags field we add to Person.

Thryv Companies map to Twenty Companies. Company names, addresses, and industry fields migrate via 1:1 mapping. Thryv's flat company structure has no parent-company hierarchy; Twenty's Company object also uses a flat model by default, so no hierarchy flattening is required. Custom company fields map to Twenty custom fields on Company.

Thryv Opportunities map to Twenty Opportunities with stage, value, and pipeline preserved. Stage names from Thryv become Opportunity stage values in Twenty; the customer defines stage labels during workspace configuration. Monetary values transfer as integers or decimals depending on Thryv field type. Pipeline assignments map to Twenty's opportunityStatus field or a custom pipeline field.

Thryv Appointments carry date, time, duration, service type, assignee, and client association. We map these to Twenty Task records with the appointment details in the task body or to custom calendar Event records depending on the customer's preference. Recurring appointment series are flattened into individual records during extraction. Assignee maps by email to a Twenty workspace Member.

Twenty has no native invoice object, so Invoices migrate to a custom Invoice object we create in the Twenty workspace during schema setup. Invoice records include line items, totals, payment status, and client association (linked via Person lookup). Paid/unpaid status from Thryv preserves as a select field. We do not migrate the ThryvPay merchant account configuration.

Thryv's freeform tagging system on Client records converts to a Twenty multi-select picklist on the Person object. During extraction, we deduplicate and normalize tags, converting spaces and special characters to valid picklist option names. The customer chooses whether to create a single personTags field or split tags into multiple typed picklists (e.g., industryTag, sourceTag) during scoping.

Thryv custom fields (up to 150 on Max tier) map to Twenty custom fields on the corresponding object (Person, Company, Opportunity, or a custom object). Field types are matched: Thryv radio buttons map to Twenty select; Thryv checkboxes map to Twenty boolean; Thryv text fields map to Twenty text. The customer must create all destination custom fields in Twenty Settings > Data Model before migration begins.

Thryv Users map to Twenty Members by email address match. Name, email, and role title migrate. Permission levels and access control configurations from Thryv do not transfer and must be reconfigured in Twenty Settings > Members. Members must be invited and active before importing any records with owner or assignee references.

Thryv communication history (Keap tier) migrates to Twenty Task records representing email and SMS activity. Email content and SMS body migrate as task body text; timestamps preserve as ActivityDate for timeline ordering. Logs link to the Person record via the PersonId lookup. This requires the Person records to exist before the activity import.

Thryv form submissions are structured records with contact info and custom form fields. These migrate as Person records with form-specific fields added as custom Person fields. The form submission date and source field map to date and source fields on Person. Duplicate detection uses email as the dedupe key.

Thryv Automation Builder sequences are not accessible via API and cannot be migrated programmatically. We deliver a written inventory of every active automation with its trigger, conditions, and actions documented for the customer's admin to rebuild in Twenty's Workflow builder. Workflow rebuild is outside migration scope.

Thryv Marketing Center social posts migrate as Note records attached to the associated Person or Company record, or as standalone Note records if no linked contact exists. Post content, scheduling metadata, and performance metrics transfer as note body text and custom fields. Platform-native posts are not recreated; content is exported for manual review.