Migrate from Voopty Inc. to Freshsales

Voopty Clients (parents or adult learners who book services directly) map to Freshsales Contact. We map client name, email, phone, and address fields to the corresponding Freshsales Contact fields. Voopty's active-client threshold (one lesson per month) does not translate to a Freshsales field; we preserve it as a custom text field for reference. Client records with associated Student records link via the Contact-Account relationship if the customer uses a parent-organization Account structure.

Voopty Student records map to Freshsales Contact with a custom field student_id__c carrying the original Voopty student identifier for audit and reconciliation. Student contact details, assigned courses, and attendance history migrate to Contact fields and related custom fields. Students linked to a Client (parent or guardian) receive the same Contact with a relationship indicator in a custom field.

Voopty Staff accounts with teacher and administrator roles map to Freshsales User records. We match by email address. Role assignments (teacher vs. administrator) migrate to Freshsales custom fields since Freshsales User roles differ from Voopty's role-based permissions model. Admin provisioning in Freshsales is validated before migration to ensure the migration user has the required permissions.

Voopty Courses (group classes and individual lesson configurations) have no direct Freshsales equivalent. We map course name, description, and duration to custom fields on Contact (for individual tutoring) or create a Course custom object on Freshsales Growth and above with a lookup to Contact. The customer chooses the strategy during scoping. Group courses that span multiple students map to a custom object if the customer requires enrollment tracking.

Voopty Subscription plans tied to students or clients map to Freshsales Deals. The subscription plan name becomes the Deal Name, the billing amount becomes Deal Amount, and the subscription period maps to Expected Close Date or a custom field. We flag Deal records originating from subscriptions for the customer's admin to assign appropriate pipeline and stage values in Freshsales.

Voopty payment records from WayForPay, LiqPay, and Stripe integrations export with transaction IDs, amounts, and timestamps. Freshsales has no native payment object, so we map payment records to custom fields on the related Deal (amount paid, last payment date, payment processor reference) or to a Payments custom object if the customer licenses Growth or above. Transaction IDs from regional payment providers migrate as text fields with no transformation.

Voopty static and dynamic scheduling has no Freshsales equivalent. We extract recurring session definitions and convert them to Freshsales Tasks (one Task per session with a due date) or to custom date fields on the Contact record. The customer selects the scheduling strategy during scoping. Native calendar sync in Freshsales (Growth and above) can be used as a workaround if the customer maintains sessions externally.

Voopty attendance tracking per session per student has no Freshsales native object. We map attendance status values (present, absent, late) to custom picklist fields on Tasks (if using Task-based session tracking) or to a custom Attendance custom object. Status values require mapping during scoping since Voopty and Freshsales use different enum values. The customer decides whether to preserve full attendance history or retain only summary statistics.