Migrate from Voopty Inc. to Nutshell

Voopty Student records map to Nutshell Contact. The student's primary email becomes the Contact email field; name fields split into First Name and Last Name or merge into a single Full Name field depending on Voopty data quality. The student's assigned courses migrate as Tag values or a multi-select custom field on the Contact. We flag any Student record missing an email address as requiring manual resolution before import because Nutshell Contact requires a unique email for deduplication.

Voopty Clients represent parents or adult learners booking services. If the Client is a parent linked to Student records, we create a Contact for the parent and link it to the Account representing the family or household. If the Client is an adult learner, the Client maps directly to a Contact with no Account relationship. We preserve the Voopty client type (parent, adult learner) in a custom field.

Voopty Staff accounts with teacher and administrator roles map to Nutshell User records. Role assignments (teacher vs administrator) migrate as a custom field on the Nutshell User. Active status from Voopty maps to Nutshell active/inactive. Staff without a usable email address in Voopty require manual provisioning before migration.

Voopty Course definitions (group classes, individual lessons, language programs) have no direct Nutshell equivalent object. We map courses to Nutshell Tags on the Contact record, with one tag per enrolled course. Course enrollment dates and completion status migrate as custom fields on the Contact. If the customer has more than 20 distinct courses, we use a separate custom field to avoid tag proliferation.

Voopty Subscriptions tied to students or clients map to Nutshell Deals. The subscription plan name becomes the Deal name, the monthly or per-session price becomes the Deal amount, and the subscription status (active, paused, cancelled) maps to Deal stage (Negotiation, Closed Won, Closed Lost). We preserve the Voopty active-client threshold flag as a custom field on the Deal because Nutshell has no native concept of subscription-based client activation.

Voopty Payment records (WayForPay, LiqPay, Stripe) migrate to Nutshell Activity Task records linked to the corresponding Contact and Deal. The payment amount, payment date, and payment provider reference migrate as custom fields on the Task. Transaction IDs from Voopty payment records preserve as external reference fields for audit. Payments without a linked Contact are reconciled during scoping and held in a queue for resolution.

Attendance tracking per session per student migrates as a custom field on the Contact or as structured Activity notes. Voopty attendance statuses (present, absent, late, excused) require value mapping because Nutshell has no native attendance concept. We propose a mapping during scoping and apply it consistently across all attendance records.

Voopty static schedules for fixed recurring classes have no direct Nutshell equivalent. We extract the recurring session definitions (day, time, course, teacher) and deliver a written session inventory document that the customer's admin uses to rebuild sessions in Nutshell's calendar or in a connected scheduling tool like Calendly or Google Calendar. Dynamic scheduling configurations are not migrated but are documented for admin reference.