Migrate from Thryv to Microsoft Dynamics 365 Sales

Thryv Clients map to Microsoft Dynamics 365 Sales Contacts. Standard fields (firstname, lastname, email, phone, address) migrate directly. We preserve all Thryv custom field values as typed custom fields on the Contact record, checking the Dynamics 365 edition's custom field limits during schema design. Client tags migrate to a multi-select picklist or custom text field, with deduplication applied during the transform step to collapse near-duplicate tags (case differences, spacing) before insertion.

Thryv Companies map to Microsoft Dynamics 365 Sales Accounts. Thryv's flat Company structure becomes the parent Account in Dynamics 365's hierarchical model. We create the Account first in the migration sequence so that AccountId is available as a lookup on every Contact at insert time. Thryv Company custom fields map to Account custom fields. If a Thryv Contact has no associated Company, we create a placeholder Account named after the Contact's company name or use the Contact's name as a single-person Account.

Thryv Opportunities map to Dynamics 365 Opportunities. The Thryv dealstage property maps to a Microsoft Dynamics 365 Sales Process with stage values that we configure during schema design. Pipeline names from Thryv map to Opportunity Record Types. Deal monetary values, close dates, and owner assignments migrate directly. Any Thryv custom fields on Opportunities become Opportunity custom fields in Dynamics 365.

Thryv Appointments map to Dynamics 365 Activities. Short-duration appointments (under two hours) map to Task records; full-day or multi-hour scheduled sessions map to Event records. Appointment date, time, duration, service type, and assignee migrate directly. We resolve the assignee to the matching Dynamics 365 User by email. Recurring appointment series in Thryv are flattened into individual Activity records with shared metadata flags. Scheduling status (confirmed, cancelled, no-show) migrates as custom Activity fields.

Thryv Invoices carry line items, totals, payment status, and client associations. Microsoft Dynamics 365 Sales does not include a full billing or accounts-receivable module by default; Invoice records are available only with the additional Finance and Operations license. For standard Sales tier migrations, we convert invoice data to Opportunity Product line items (for historical deal records) or store invoice metadata as custom fields on the related Account and Contact records. We export full invoice records including line-item prices and totals as a structured CSV deliverable for the customer's finance team to reconcile or import into a separate accounting system.

Thryv freeform tags on Contact and Company records have no direct Dynamics 365 equivalent. We deduplicate the tag vocabulary during the transform step, then either create a multi-select picklist (preferred, up to 150 values per picklist) or store tags as a comma-delimited custom text field. The customer chooses the strategy during scoping. Tags used for segmentation are better suited to multi-select picklists; tags used for loose categorization can remain as text.

Thryv custom fields of all types (text, number, date, radio button, checkbox, dropdown) map to equivalent Dynamics 365 custom fields on the relevant entity (Contact, Account, Opportunity). We perform type-matching during schema design: Thryv radio buttons become Dynamics 365 option sets, checkboxes become two-option fields, and drop-downs become option sets. Edition limits are not a concern on the Dynamics 365 destination since Professional tier has no meaningful custom field ceiling. We flag any Thryv custom fields that would require a new custom entity (for lookup relationships) and scope those separately.

Email and SMS communication history from Thryv's Keap tier migrates to Dynamics 365 Activity records. Email content migrates as EmailMessage records linked to the parent Contact. SMS thread metadata migrates as Task records with a custom communication-type field. Communication timestamps are preserved for activity timeline ordering. Note that Thryv's REST API coverage for communication logs varies by account tier and API version, so we scope this object as conditional and flag any missing API endpoints during extraction.

Thryv user records (name, email, role) map to Dynamics 365 Users by email match. We extract all owners referenced on Contacts, Companies, Deals, and Appointments and resolve them to Dynamics 365 Users during the migration. Users without a matching Dynamics 365 User are placed in a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission settings do not transfer and must be reconfigured in Dynamics 365 Security Roles and Field Level Security post-migration.

Thryv website form submissions migrate as Lead or Contact records in Microsoft Dynamics 365 Sales depending on the customer's lead strategy. Form field data maps to standard Contact fields where possible (name, email, phone) and to custom fields for non-standard form inputs. Submission timestamps and referrer metadata are preserved in custom fields for attribution. If the customer plans to use Microsoft Dynamics 365 Sales Lead model for pre-conversion prospects, we map form responses to Lead; otherwise, they land as Contacts directly.