Migrate from Vryno CRM to Freshsales

Vryno Leads map directly to Freshsales Leads. Standard fields including name, email, phone, company, and lead status transfer cleanly. Vryno lead scoring fields migrate to Freshsales custom numeric fields on Lead. We set Freshsales Lead Status to the equivalent Vryno stage name. Note that Freshsales lead conversion (turning a Lead into a Contact, Account, and Deal) requires preconfigured field mapping rules in Admin Settings; we document these mappings before migration and set them up during Freshsales configuration so that Vryno custom field values do not drop on conversion.

Vryno Contacts map 1:1 to Freshsales Contacts. Name, email, phone, address, and custom contact-level fields transfer directly. We deduplicate on email during import and flag duplicate Contact records for the customer's admin to resolve. Any Vryno contact ownership assignments map to Freshsales Owner lookup by email match against Freshsales User records.

Vryno Accounts map directly to Freshsales Accounts. Company name, industry, website, address, and custom Account fields migrate 1:1. Account is created before any Contact import so that the Account-Contact lookup relationship is satisfied at the moment of Contact insert. We preserve the Account-to-Contact relationship by resolving AccountId during Contact import.

Vryno Deals map to Freshsales Deals with deal name, value, stage, expected close date, owner, and associated account migrating directly. Vryno pipeline stage names map to Freshsales Deal stages, and we configure the stage sequence in Freshsales before migration begins. Deal ownership assignments map by email match to Freshsales User records. Any Vryno deal probability percentages migrate as custom fields or notes since Freshsales Deal does not have a native probability field on all tiers.

Vryno Activities covering emails, calls, meetings, and tasks map to Freshsales Activity records. Vryno activity type, date, duration, notes, and associated Contact or Deal references transfer. Call activities map to Freshsales Tasks with call disposition and duration preserved; meeting activities map to Event records with start and end time. Activity records are imported after Contacts, Accounts, and Deals to ensure the parent-record lookup is satisfied.

Vryno Products migrate to Freshsales Products with name, SKU, and unit price preserved. Vryno's Products and Taxation module on Essentials and above carries tax codes that migrate as custom product fields in Freshsales. We flag any currency or tax code format differences during schema discovery so that product pricing imports without rounding errors.

Vryno Custom Modules are user-defined objects unique to each instance, meaning no two Vryno accounts share the same schema. We perform field-level schema discovery on the source instance before migration, generate a per-customer field map, and create equivalent custom objects or custom fields in Freshsales Admin Settings. Vryno custom module records import after the parent standard objects (Account, Contact, Deal) are present in Freshsales to satisfy any lookup relationships. If a Vryno custom module references another custom module, we sequence the imports in dependency order.

Vryno pipeline definitions (stage names, stage order, and stage probabilities) migrate to Freshsales Pipeline configurations. Each Vryno pipeline becomes a Freshsales Pipeline. We configure the stage sequence and stage-to-status mapping in Freshsales Admin before Deals import. Note that Vryno Kanban visual layout (available on Professional and above) does not transfer; Freshsales Kanban view is applied as the default pipeline view on Growth and above. Any Vryno pipeline exceeding 20 stages may require consolidation if the Freshsales plan limits stage counts.