Migrate from Voopty Inc. to Salesforce Sales Cloud

Voopty Student records map to Salesforce Contact with the Student record type. Voopty's contact fields (name, email, phone, address) map to standard Contact fields. We add custom fields student_id__c (Voopty's internal ID), enrollment_date__c, grade_level__c (picklist), and program_type__c (group class, individual, subscription). Parent or guardian contacts from Voopty's client records attach via the Parent__c lookup relationship we pre-create.

Voopty Client records (parents or adult learners who book services) map to Salesforce Contact with a Client record type, distinct from the Student record type. Active status from Voopty is computed behaviorally (one lesson per month); we preserve this in a custom field voopty_active_threshold__c and recommend the customer's admin set an explicit IsActive__c flag in Salesforce based on their business rules.

Voopty Teacher and Staff records map to Salesforce Contact with the Teacher record type and a custom field teacher_role__c carrying the Voopty role (instructor, administrator, receptionist). If the teacher accesses Salesforce, we provision a matching User record and link via User_Contact__c lookup. Role-based permissions from Voopty map to Salesforce Permission Sets (e.g., Teacher_Access, Admin_Access) that the customer's admin assigns post-migration.

Voopty Course records map to a Salesforce custom object Course__c. Fields include course_name__c, course_type__c (group, individual, hybrid), description__c, duration_minutes__c, and status__c (active, inactive). Course__c Lookup relationships to Account (the school or organization) and Contact (the assigned teacher) are resolved at migration time.

Voopty static recurring schedules (fixed weekly classes) map to Salesforce Event records for calendar visibility and a custom Session__c object for data integrity. The Event carries StartDateTime, EndDateTime, Subject (course name), and Location. Session__c stores the Voopty session_id__c, recurrence_pattern__c, session_type__c, and capacity__c. Dynamic per-session bookings map to Session__c with Event records created for confirmed bookings only.

Voopty dynamic scheduling (per-session, non-recurring) maps to Salesforce custom object Session__c without Event records unless explicitly booked. We preserve session_date__c, start_time__c, end_time__c, status__c (scheduled, completed, cancelled), and linked Course__c and teacher Contact lookups. Cancellation reason migrates to cancellation_reason__c.

Voopty attendance tracking per session per student maps to a custom object Attendance__c with Lookup fields to Session__c and Contact (student). The attendance_status__c picklist maps from Voopty values (present, absent, late, excused) to Salesforce equivalents. Timestamp fields (arrival_time__c, departure_time__c) migrate as datetime fields. Historical attendance records are bulk-loaded via Salesforce Bulk API 2.0 in batches of 10,000.

Voopty subscription plans tied to students or clients require a scoping decision: if the school operates on a recurring revenue model (monthly tuition, course bundles), Subscription__c custom object is recommended with fields plan_name__c, billing_cycle__c, start_date__c, end_date__c, and status__c. If subscriptions represent one-time course enrollments with payment plans, Opportunity with custom fields is appropriate. The customer chooses during discovery; we document both options with pros and cons.

Voopty payment records from WayForPay, LiqPay, and Stripe integrations map to a custom object Payment__c with fields amount__c, currency__c, payment_date__c, payment_provider__c, transaction_id__c (external reference), status__c, and Lookup to Contact (student or client payer) and Subscription__c or Opportunity. Payment provider metadata (processor, gateway response) is stored in payment_metadata__c as a long-text field for audit.

Voopty's organization-level entity maps to Salesforce Account. For single-location schools, Voopty's primary business account becomes a single Account record. For multi-location organizations, we create a parent Account (the school brand) and child Accounts (each location) with Account Hierarchy preserved via ParentId. Account custom fields include organization_type__c (language school, tutoring center, fitness studio, etc.) and timezone__c.

Voopty payment processor configurations (WayForPay and LiqPay credentials, webhook settings, payout currency) have no Salesforce native equivalent. We create a custom object Payment_Config__c to store processor_name__c, merchant_id__c, currency__c, and active__c so the customer's admin can configure Salesforce Payments or a third-party payment app post-migration. This is informational, not functional, within the migration scope.

Voopty's Telegram and email campaign integration for parent and student communication has no Salesforce standard object equivalent. Salesforce uses Marketing Cloud for email campaigns and Service Cloud for messaging integrations. We flag the Voopty campaign configuration in the migration handoff document with the recommended replacement approach (Marketing Cloud Email Studio for newsletters, Service Cloud Flow for parent notifications, or an AppExchange messaging app). This is a separate implementation scope.

Voopty staff accounts with role-based permissions for teachers and administrators map to Salesforce Permission Sets. We extract each distinct Voopty role and create a corresponding Permission Set in Salesforce (Teacher_Access, Admin_Access, Billing_View, etc.). Access levels (read, write, admin) translate to Salesforce field-level security settings on the custom education objects. User-to-Permission-Set assignments are documented for the customer's admin to assign post-migration.

Voopty's online booking feature (for class-based businesses accepting student reservations) maps to a custom object Booking__c with fields booking_date__c, status__c, booked_by__c (Contact lookup), session__c (Session__c lookup), and notes__c. Confirmed bookings create Event records for calendar visibility; pending bookings remain as Booking__c only until confirmed.