Migrate from Voopty Inc. to Zoho CRM

Voopty student records map to Zoho CRM Contacts with a custom field voopty_student_id__c preserving the original Voopty identifier for reconciliation. Student contact fields (name, email, phone, address) map directly. We create a custom module called Student_Profile__c linked to Contact via lookup if the institution needs to store grade level, enrollment date, or emergency contact separately from the Contact record. Voopty's student-course enrollment relationship migrates as a custom multi-select picklist or a Course_Enrollment__c custom module linking Student Contact to Course custom module.

Voopty Clients represent parents, adult learners, or organizational buyers. Individual adult learners map to Zoho CRM Contacts with a custom field voopty_client_type__c = 'Individual'. Organizational clients (language school franchises, corporate training buyers) map to Zoho CRM Accounts with the parent Contact stored as Primary Contact or in a custom Account_Contact_Relation__c module. We apply Voopty's active-client definition (one lesson per month minimum) as a custom picklist field voopty_active_status__c with values Active/Inactive rather than letting Zoho's default blank status absorb the distinction.

Voopty staff accounts with role-based permissions map to Zoho CRM Users if the institution wants the teacher to log in to Zoho, view their student roster, and track sessions. Role assignment (teacher, administrator, coordinator) migrates as a Zoho custom field staff_role__c. If Voopty staff do not need Zoho login access, we map them as Contacts with a custom field is_voopty_staff__c = true and preserve their role assignment for reporting. We resolve each Voopty staff email against the destination Zoho User table during scoping.

Voopty course definitions (group classes, individual lesson configurations, program names, and duration) map to a Zoho custom module Course__c. We pre-create the module in Zoho before migration, including custom fields for course_type__c (group/individual), max_capacity__c, duration_minutes__c, and a lookup to the primary teacher Contact. Course pricing migrates to a custom field course_fee__c if the institution needs to track per-course revenue separately from subscription billing.

Voopty static fixed schedules and dynamic recurring sessions map to Zoho CRM Events for calendar display, and to a custom module Scheduled_Session__c to preserve the full session definition including recurrence rule, room or location, and linked Course lookup. Voopty session identifiers are preserved in voopty_session_id__c on the Scheduled_Session__c record for reconciliation. We extract recurrence patterns from Voopty exports and convert them to Zoho Event recurrence format or store them as custom text fields if the recurrence logic exceeds Zoho's native recurrence model.

Voopty attendance tracking per session per student maps to a custom module Attendance__c linked to both the Student Contact and the Scheduled_Session__c custom module. Attendance status values (present, absent, late, excused) migrate as a custom picklist field attendance_status__c. We perform value-mapping during transform to ensure that Voopty's status encoding maps correctly to the Zoho picklist values. Session identifiers from Voopty are preserved to enable the Attendance-to-Session lookup resolution during import.

Voopty subscription plans tied to students or clients require custom mapping because Zoho's standard Deal object models sales opportunities rather than recurring enrollment billing. We create a custom module Subscription__c with fields for plan_name__c, billing_cycle__c, start_date__c, end_date__c, monthly_fee__c, and a lookup to the Student Contact. Alternatively, for institutions that prefer Zoho's native pipeline view, we map active subscriptions to Zoho Deals with Record Type = Enrollment, Stage = Active Subscription, and subscription metadata stored in custom fields. The customer chooses during scoping.

Voopty payment records tied to WayForPay, LiqPay, or other Eastern European processors migrate as custom module Payment__c entries linked to the Subscription__c record or the Student Contact. We preserve payment_amount__c, payment_date__c, payment_provider__c, and transaction_id__c. We do not migrate payment processor configuration or webhook settings; these are documented as requiring reconfiguration in the destination payment gateway. Stripe payment references migrate as-is for audit trail but require reconnection in the destination billing environment.

The Voopty enrollment relationship between a student and a course maps to a custom module Course_Enrollment__c linking the Student Contact to the Course__c custom module. Enrollment date, enrollment status, and completion date store as custom fields. This module is required because Zoho's standard module relationships do not natively model the many-to-many relationship between students and courses in an education context.

Voopty parent and guardian records attached to student accounts map to Zoho Contacts with a custom field relationship_to_student__c (parent, guardian, authorized_pickup). We create a custom module Parent_Student_Relation__c or use Zoho's native Contact-to-Contact related list to link the parent Contact to the student Contact. This is scoped as configuration-intensive for families with multiple enrolled students.