Migrate from Vryno CRM to Nutshell

Vryno Leads with auto-assignment rules, lead scoring fields, and geography-based routing map to Nutshell Leads. The lead source, status, and score values migrate as standard fields. We deduplicate on email address during import and preserve any custom field extensions on the Vryno Lead record. Vryno's lead routing logic (by geography, product line, or rep availability) is a configuration that does not export; we document the active routing rules for the customer's Nutshell admin to rebuild.

Vryno Contacts (name, email, phone, address, custom fields) map directly to Nutshell People. We deduplicate on email during import using Nutshell's duplicate detection. Contact-level custom fields from Vryno migrate to Nutshell People custom fields, subject to the destination plan's field count limits. The Account-to-Person relationship is preserved by resolving the Account lookup after the Accounts phase completes.

Vryno Accounts (company name, industry, address, revenue, employee count) map to Nutshell Companies. Company-level custom fields migrate to Nutshell Company custom fields. We create Companies first in the migration sequence so that the lookup relationship is satisfied at the moment of Person import. The Account-Contact relationship chain is preserved through Nutshell's Person-Company link.

Vryno Deals map to Nutshell Deals with stage name, probability, deal value, expected close date, and owner preserved. Vryno's pipeline stage columns (Kanban columns or grid views) become Nutshell pipeline stages. We flag any deal that references a stage name not defined in the destination Nutshell plan before writing. Closed-Lost and Closed-Won status migrates as deal status.

Vryno's pipeline definitions (stage names, stage order, probability percentages) map to Nutshell Pipeline configuration. Vryno's plan-gated pipeline limits (1 on Free, 5 on Essentials, 10 on Professional, 20 on Enterprise, 50 on Premium) determine the target Nutshell plan recommendation. If the customer uses fewer pipelines than Nutshell's Starter plan allows (1), we map directly; if more, we recommend Professional or above.

Vryno Activity records (type, date, duration, notes, related Contact or Deal) map to Nutshell Activity records. Call logs, emails, meetings, and tasks each become Nutshell Activity entries linked to the related Person or Deal. Notes migrate as Activity notes. We reconstruct the activity timeline by setting the activity date to the original Vryno timestamp. If the activity references a Contact or Deal not yet migrated, we hold it in a staging queue until the parent record is created.

Vryno Products (name, SKU, unit price) map to Nutshell Products. The Products & Taxation module in Vryno (gated to Essentials and above) requires tax code schema mapping by country set. We migrate product records and pricing; tax rate configurations are documented separately for manual setup in Nutshell.

Vryno Custom Modules (Vendors, Projects, Tax records, and other user-defined objects) are instance-unique with no two Vryno instances sharing 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 fields in Nutshell on the relevant object (Company, Person, or Deal). If a custom module contains lookup relationships to other Vryno objects, we resolve those references during the transform phase and map to Nutshell's native lookups. Plan-based Nutshell custom field limits apply and are checked during scoping.