Migrate from Flavor CRM to Zoho CRM

Flavor CRM Leads map directly to Zoho CRM Leads. We export all Lead fields including source, status, and custom properties. The conversion date and any converted_student_id are preserved as custom fields on the Zoho Lead record. Unconverted Leads migrate as active Leads; converted Leads retain the student reference for audit but are flagged as converted in Zoho's status field.

Flavor CRM Students are the primary Contact equivalent and map directly to Zoho Contacts. Enrollment history and parent linkage properties transfer as custom Contact fields. The original Flavor CRM student_id is preserved in a custom field for cross-referencing. We create the Zoho Contact before importing any related Activities so that the parent record exists for lookup resolution.

Flavor CRM Parent records map to Zoho Contacts with a custom field parent_type__c set to Parent and a lookup pointing to the related Student Contact. Some customers prefer to store Parents as separate Contact records with a Many-to-Many relationship via a junction object; we confirm the preferred approach during scoping. The parent contact type ensures segmentation and reporting by guardian relationships in Zoho.

Flavor CRM Contracts are a distinct object with related activities. We create a Zoho Custom Object named Contracts with fields mirroring the Flavor CRM schema: contract_id, student_name (lookup to Contact), start_date, end_date, contract_value, and status. Contract PDFs migrate as attachments linked to the custom Contract record via ContentDocumentLink.

Flavor CRM Opportunities map directly to Zoho Deals. Stage, amount, owner, and create date migrate, and pipeline stages map to Zoho's defined Deal stages. We configure Zoho pipeline stages during destination setup to match the Flavor CRM dealstage values so that historical pipeline reporting is preserved.

Flavor CRM Invoice records require an explicit routing decision during scoping: (a) load as Zoho Invoices module records (Standard tier and above), (b) attach as PDFs to the related Student Contact or Contract, or (c) export to a separate accounting system via CSV mapping. We flag Invoices as a separate migration phase and document the chosen routing before import begins. Line item detail migrates as structured CSV mapped to Zoho's invoice line item fields if option (a) is selected.

Flavor CRM Class records have no native Zoho equivalent. We create a Custom Object named Classes with fields for class_id, class_name, instructor (lookup to User), schedule, enrollment_capacity, and current_enrollment. Class enrollment data maps from Flavor CRM's student_class_associations table. If Zoho does not support enough custom objects on the selected tier, we alternatively map Classes to Zoho Tags on the Student Contact records for a lighter-weight representation.

Flavor CRM Staff records map to Zoho Users. We resolve Staff by email match against Zoho User accounts. Staff without a matching Zoho User go to a reconciliation queue for the customer's admin to provision. Role and permission data from Flavor CRM maps to Zoho Profiles and Roles during User configuration. Inactive Staff migrate as Zoho Users with Active = false.

Flavor CRM Activities (Email, Phone call, Meeting, Task) export individually and map to Zoho Tasks with Task Type differentiated by a custom field activity_type__c. Meetings map to Zoho Events with Start DateTime, End DateTime, and Location preserved. We set the WhoId (Contact lookup) on each Zoho Activity by resolving the related Student or Parent Contact by email.

Flavor CRM does not expose a bulk attachment export endpoint. We flag binary attachments for manual handling: we export the media transaction report as CSV listing file names, record associations, and download URLs. The customer's team downloads files individually or via any available batch download tool, and we provide a Zoho attachment import mapping template. Files are linked to Zoho records via ContentDocumentLink after upload. This phase extends the project timeline and is priced separately if attachment volume exceeds 500 files.

Flavor CRM creates a permanent reference when a Lead converts to a Student. This linkage is not preserved in standard exports. We extract conversion_timestamp and original_lead_id as custom properties on the Zoho Contact record so that the enrollment funnel history can be reconstructed. This custom mapping is critical for institutions tracking lead-to-enrollment conversion rates and must be flagged during scoping.