Migrate from Vryno CRM to Pipedrive

Vryno Leads map directly to Pipedrive Person records using the Lead object type. Standard fields (name, email, phone, address, lead source) migrate 1:1. Lead scoring fields migrate as numeric custom fields in Pipedrive. We deduplicate on email address during import and flag any Person that already exists in the destination with a conflict resolution rule (skip, update, or duplicate) agreed during scoping.

Vryno Contacts map to Pipedrive Persons (Contact subtype). Standard fields (name, email, phone, job title, address) map 1:1. Contact-level custom fields migrate as Pipedrive custom fields on the Person object. We preserve the Contact-to-Account relationship by resolving the Account reference at migration time and linking to the target Organization record.

Vryno Accounts map to Pipedrive Organizations. Company name becomes Organization name; industry, website, address, and phone migrate as standard Organization fields. The Account-to-Contact relationship is preserved by linking each migrated Contact Person to its parent Organization via the organization_id field. Organization is created before any Person import so that the lookup relationship is satisfied at the moment of Person insert.

Vryno Deals map to Pipedrive Deals. Deal name, value, expected close date, stage name, probability percentage, and owner migrate 1:1. Vryno pipeline stage names map to Pipedrive stage labels; we pre-create the stage structure in Pipedrive before migration to avoid orphaned stage assignments. Owner resolution uses email matching against Pipedrive Users.

Each Vryno pipeline becomes a Pipedrive Pipeline with stages defined to match the source stage names and probabilities. Vryno Professional allows up to 10 pipelines; Enterprise allows 20; Premium allows 50. We validate pipeline count against the destination Pipedrive plan (Growth and above support multiple pipelines). Pipeline count exceeds the destination tier limit are flagged and resolved during scoping.

Vryno Activities (calls, emails, meetings, tasks) map to Pipedrive Activities linked to their parent Person or Deal via the deal_id and person_id foreign keys. Activity type, date, duration, notes, and outcome migrate. We set the Activity's due_date and due_time to the original Vryno timestamp so that the activity timeline order is preserved in Pipedrive. Email body content migrates as an Activity note attachment.

Vryno Products (name, SKU, unit price, tax codes) map to Pipedrive Products. The Products & Taxation module is gated to Vryno Essentials and above; we validate the source tier before attempting product migration. Tax code schemas vary by country setting and may require field-level adjustment during mapping.

Vryno Custom Modules are user-defined objects with unique field schemas per instance. Pipedrive does not support standalone custom objects—custom data lives as custom fields attached to standard objects. We perform a schema discovery pass on the source Vryno instance first, generate a per-customer field map, create the corresponding custom fields in Pipedrive, and map each Custom Module record to a standard object (typically Deal or Person) using a designated reference field. If a Custom Module has lookups to other Custom Modules, we flatten these into Pipedrive custom fields with concatenated display values. This is the most variable part of any Vryno-to-Pipedrive migration and requires per-instance scoping.

Vryno Custom Dashboards are configurable reporting widgets per role—Sales Head sees win rates, CFO sees revenue forecasts. Pipedrive's reporting is sales-activity-focused rather than CFO-oriented. We do not migrate dashboard data queries. We deliver a written specification of every active dashboard definition (widget types, metrics, filters, and layout) so the customer's Pipedrive admin can rebuild using Pipedrive's report builder or an embedded BI tool.

Vryno workflow rules—including conditional follow-up emails, lead routing by geography or product line, and stage-change triggers—are configuration data that cannot be exported. We document every active workflow during the discovery call, capture its trigger condition, action sequence, and delay logic, and deliver an inventory document mapped to Pipedrive Automation actions. Pipedrive Automation (included from the Essentials plan upward) supports trigger-based and scheduled automations that can replicate most Vryno workflow patterns.