Migrate from Flavor CRM to Freshsales

Flavor CRM Leads map directly to Freshsales Lead records. We extract all Lead properties including source, status, and any custom enrollment-interest fields. The Lead-Student conversion link from Flavor CRM is preserved as a custom text field original_student_id__c on the Freshsales Lead so that if the lead later converts, the original Student reference remains available for reporting.

Flavor CRM Students are the primary contact-equivalent object and map directly to Freshsales Contact records. Enrollment history, any grade-level or program fields, and the link back to the originating Lead (via original_lead_id__c) migrate as custom Contact fields. Parent relationships stored in Flavor CRM attach to the Contact record via a custom relationship field or the Freshsales contact's phone and address block for family-facing institutions.

Flavor CRM Parent records are stored as related contact types. We export Parent records separately and map them to Freshsales Contact records with a parent_type__c custom field set to 'Parent' to distinguish them from Student contacts. Where multiple students share the same parent, we create one Contact record per parent and link each student Contact via a custom field parent_contact_id__c.

Flavor CRM Contracts map to Freshsales Deal records. The contract value and effective dates migrate to Freshsales Deal amount and close date fields. The contract record ID is stored in a custom field original_contract_id__c so that the customer can cross-reference back to the source system during the reconciliation window. Associated contract activities migrate as Tasks linked to the Deal.

Flavor CRM Opportunities map 1:1 to Freshsales Deals. Stage, amount, owner, and create date transfer directly. Pipeline stages from Flavor CRM are mapped to Freshsales Deal stages during configuration, and any custom stage properties migrate as custom fields on the Deal.

Flavor CRM Invoice records require explicit handling because Freshsales has no native invoice object. We create a Custom Object called Invoice__c in Freshsales and map invoice number, date, line items, amounts, payment status, and student reference as fields on the custom object. If the customer prefers, we can instead attach invoice PDFs as notes to the related Contact record and route full financial history to an external accounting system via the Freshsales integration API. This decision is made during scoping.

Flavor CRM Class records have no standard Freshsales equivalent. We create a Class__c Custom Object with fields for class name, schedule, instructor, enrollment capacity, and linked Student references, or map class enrollment to Freshsales Groups with a tag-based grouping strategy if Custom Objects are not available on the destination plan tier. The customer confirms the preferred approach during scoping.

Flavor CRM Activities — including calls, meetings, and tasks — export as individual records per activity type. We map call activities to Freshsales Task with TaskSubtype = Call, meeting activities to Event, and general tasks to Task. Each task inherits the owner and timestamp from the source record. The activity is linked to the appropriate Contact, Lead, or Deal via Freshsales's WhoId and WhatId fields.

Flavor CRM Staff records map to Freshsales User accounts by email match. Permissions and role data from Flavor CRM are not transferred as Freshsales role definitions — those must be rebuilt by the customer's Freshsales admin post-migration. We flag the role mapping as a deliverable in the written handoff document so the admin knows which staff member needs which access level.