Migrate from Thryv to Nutshell

Thryv's Client records map to Nutshell Person records. We extract standard fields (first name, last name, email, phone, address) and preserve all contact-level custom field values. Thryv's client tags are extracted separately and converted to Nutshell dropdown or multi-select custom fields on Person. Any Thryv custom fields that exceed Nutshell's character limits (Text fields cap at 225 characters) are flagged during scoping, and long-text fields are mapped to Nutshell Long Text fields.

Thryv's flat Company structure maps to Nutshell's Company object. Company name, address, phone, website, and company-level custom fields transfer directly. We flag any Thryv Company records that have no associated Contacts — these are imported as standalone Nutshell Companies with no Person link, which is valid in Nutshell's data model.

Thryv Opportunities map to Nutshell Deals. We preserve deal name, monetary value, stage name, expected close date, and owner assignment. Custom stage names from Thryv are preserved as-is in Nutshell's Deal stage columns. If the Thryv account uses multiple deal pipelines, we map each pipeline to a separate Nutshell pipeline column.

Thryv Appointments (date, time, duration, service type, assignee) map to Nutshell Tasks with activity date set to the appointment start time and a note attached containing service type and duration. Recurring appointment series are flattened into individual Task records per occurrence, since Nutshell does not support recurring task series natively. Assignee maps to the matching Nutshell User by email.

Nutshell does not have a native invoice or billing object. We export full invoice records (line items, totals, payment status, client association) as a structured CSV with column headers matching Nutshell's CSV import template for Leads and People. The customer runs the import via Nutshell's built-in importer. Paid or unpaid status is added as a custom field in Nutshell after import if the customer needs to track it.

Thryv's freeform tagging system on Client records converts to Nutshell custom fields. During scoping, we identify the distinct tag vocabulary, deduplicate it, and map tag groups to either Dropdown (single-tag) or Multi-Select (multi-tag) custom fields on Person. Tags used as content classification rather than contact classification are exported as a separate tagging reference sheet for manual categorization.

Thryv custom fields map to Nutshell custom fields on the matching record type (Person or Company). Field type matching is required: Thryv radio buttons map to Nutshell Dropdown, Thryv checkboxes map to Nutshell Checkbox, Thryv text maps to Nutshell Text (or Long Text if over 225 characters). Thryv Pro's 100-field limit and Max's 150-field limit do not apply in Nutshell, but Nutshell's supported field types are fewer — any unsupported Thryv field types are flagged for customer decision on how to store that data.

Thryv user records (name, email, role) map to Nutshell Users resolved by email match. Thryv role-based permission levels (admin, manager, staff) are preserved as a custom field in Nutshell because Nutshell's role model is structured differently. Any Thryv user without a matching Nutshell account goes to a reconciliation queue for the customer to provision before record import resumes.