Migrate from Vryno CRM to Salesforce Sales Cloud

Vryno Leads with auto-assignment by geography, product line, or rep availability map directly to Salesforce Lead. Lead scoring fields migrate to custom integer fields on Lead (vryno_lead_score__c). We preserve the original owner assignment in a custom field vryno_owner_id__c for reconciliation. Vryno lead status values map to Salesforce Lead Status picklist, with any custom status values created in Salesforce before migration.

Vryno Contacts map 1:1 to Salesforce Contact. Standard fields (FirstName, LastName, Email, Phone, MailingAddress) map directly. We deduplicate on email during import using Salesforce matching rules. Contact-level custom fields migrate to Salesforce custom fields on Contact with __c suffixes. The Account-Contact relationship resolves by matching Vryno Account.name to Salesforce Account.Name at migration time.

Vryno Accounts (companies and organizations) map directly to Salesforce Account. Company-level industry, address, and revenue fields migrate to the equivalent Account fields. Account is created before Contact import so that AccountId Lookup is satisfied at Contact insert time. Any Vryno Account without a matching Contact still migrates as a standalone Account.

Vryno Deals map to Salesforce Opportunity. Deal stage maps to Salesforce StageName; deal value maps to Amount; expected close date maps to CloseDate; owner maps to OwnerId via email match to Salesforce User. Pipeline stage names and probability percentages migrate as the Salesforce Sales Process and stage probability values.

Each Vryno pipeline (capped at 1-50 depending on Vryno tier) maps to a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the stage values. Stage probability percentages migrate from Vryno to Salesforce StageProbability. If the customer uses multiple Vryno pipelines for different lines of business, each becomes a separate Record Type with its own Page Layout.

Vryno Activities (calls, emails, meetings, tasks) split by type into Salesforce Task (calls and tasks) and Event (meetings). Email-type activities migrate as Salesforce Task with a note that Salesforce's native EmailMessage object can be used for full email content. We preserve activity type, date, duration, and notes, and resolve WhoId (Contact or Lead) and WhatId (Opportunity or Account) via lookup resolution against migrated records.

Vryno Products (name, SKU, unit price, tax codes) map to Salesforce Product2. The Products & Taxation module in Vryno is gated to Essentials and above, so we check the source tier before migration. Price Book entries (Standard) are created during import. Tax code schemas vary by country setting and are preserved as custom fields if the destination org uses Salesforce tax configuration.

Vryno Custom Modules (Vendors, Projects, Taxation, and any user-defined objects) require per-instance field-level discovery before migration because no two Vryno instances share the same custom schema. We run the discovery step against the live Vryno instance, generate a field map for each Custom Module, create the equivalent custom object in Salesforce (with matching __c field names), configure lookup relationships to Account or Contact, and then import the Custom Module records in dependency order after the parent standard objects are in place.

Vryno Custom Dashboards (widget definitions and metric names) migrate as Salesforce Dashboard metadata, but the live data queries re-evaluate against migrated data at runtime. We preserve the metric names, widget types, and filter configurations in a written dashboard reconstruction guide. Sales Head win-rate dashboards and CFO revenue forecast dashboards are documented separately so the customer's admin can rebuild them in Salesforce CRM Analytics or standard Reports and Dashboards.

Vryno Owner assignments on Deals, Contacts, Accounts, and Activities resolve by email match against the destination Salesforce User table. Any Vryno Owner without a matching Salesforce User goes to a reconciliation queue before record import begins. The customer's Salesforce admin provisions missing Users (active or inactive per the original user's status). OwnerId must be resolved before any standard object insert because it is a required reference on Opportunity.

Vryno pipeline stage names and probability percentages migrate to Salesforce Sales Process stage definitions. The stage ordering is preserved. We flag any Vryno pipeline that exceeds the Salesforce Professional tier's stage count recommendations (typically 8-10 stages per process) and recommend consolidation during the scoping call.

Vryno's built-in lead scoring fields (auto-assignment and scoring by geography, product line, and rep availability) migrate as custom fields on Salesforce Lead. The scoring algorithm itself is a Vryno workflow configuration and does not migrate; we document the scoring logic during discovery for the customer to implement in Salesforce Flow using criteria-based entry or Einstein Lead Scoring as an upgrade.