Migrate from Flavor CRM to Salesforce Sales Cloud

Flavor CRM Leads map directly to Salesforce Lead. The lead source, status, and any custom properties migrate to standard and custom Lead fields respectively. We preserve the original Flavor CRM lead_id as a custom field for audit traceability. Flavor CRM's Lead-to-Student conversion link (when a Lead enrolls as a Student) is captured at migration time: we store the original lead_id and conversion timestamp as custom properties on the corresponding Salesforce Contact so the enrollment funnel remains historically reconstructable.

Students are the primary Contact equivalent in Flavor CRM. We map Student records directly to Salesforce Contact, preserving enrollment history, grade level, enrollment status, and any associated parent links as custom Contact properties. The original Flavor CRM student_id is stored in a custom field for lookup resolution if the institution later needs to cross-reference historical data. Parent relationship data from Flavor CRM is exported separately and linked via a custom Contact relationship field or a dedicated Parent Contact record with a relationship type.

Parent records in Flavor CRM are stored as related contact types with a designated relationship to the Student. We export Parent records separately and map them to Salesforce Contact records with a custom relationship type field (e.g., Mother_Of__c, Father_Of__c, Guardian_Of__c) linking to the corresponding Student Contact. Email, phone, and address data migrate to standard Contact fields. If the destination Salesforce org uses the standard Family relationship model, we flag the mapping strategy during scoping.

Class records in Flavor CRM have no standard Salesforce equivalent. We pre-create a Class__c Custom Object with fields for class_name, subject, instructor (lookup to User), schedule, enrollment_capacity, and enrollment_count. Each Class__c record is linked to its enrolled Student Contacts via a junction object (Class_Enrollment__c) or a lookup field on the Contact. This schema must be designed and deployed to the destination Sandbox before migration begins; the customer confirms the Custom Object structure during scoping.

Flavor CRM Invoice records contain line items, payment history, and status that do not map to any standard Salesforce object. We flag Invoice exports separately and discuss three options with the customer: load as Invoice__c Custom Objects with line item detail preserved, attach PDF exports to the Student Contact record, or route to a separate accounting system (QuickBooks, XERO) via an existing integration. The choice depends on whether the institution needs Salesforce to serve as the billing system of record post-migration. This decision point must be resolved during scoping because it affects the data extraction format from Flavor CRM.

Flavor CRM Contracts map to Salesforce Opportunity when the contract represents an enrollment or service agreement with a monetary value. Contract start date, end date, and value migrate to Opportunity fields. If the contract represents a fixed-term enrollment (e.g., an annual tuition contract), we also create a custom Contract_Date__c range field on the Opportunity. The related Student Contact becomes the Opportunity's primary Contact, and the Account (if using Account for the institution) is assigned accordingly.

Staff records in Flavor CRM store employee data separate from Student records. We export Staff as Salesforce User records, matching by email address. Permissions and access levels from Flavor CRM are flagged as custom User fields (e.g., Flavor_CRM_Role__c) for the customer's admin to map to Salesforce Profiles and Permission Sets post-migration. Staff without an email address are held in a reconciliation queue for the admin to provision before record import resumes.

Activities in Flavor CRM (calls, emails, meetings, tasks) are exported by activity type and mapped to Salesforce Task and Event objects. Calls map to Task with TaskSubtype = Call and CallDurationInSeconds preserved. Meetings map to Event with StartDateTime, EndDateTime, and Location preserved. Emails map to Salesforce EmailMessage records linked to Task for the activity timeline. The parent record (Student Contact or Lead) is resolved at migration time via the Flavor CRM contact_id mapping.

Flavor CRM Opportunities map directly to Salesforce Opportunity. Stage, amount, owner, and create date migrate to standard Opportunity fields. Pipeline stages from Flavor CRM are mapped to Salesforce Stage values, and we recommend the customer configure a corresponding Sales Process in Salesforce before migration. Closed-Won and Closed-Lost reasons from Flavor CRM become custom Opportunity fields for reporting consistency.

Flavor CRM does not expose a documented bulk export endpoint for media and attachments. Binary file attachments cannot be extracted programmatically and require manual download by the customer's team. We flag this as an out-of-scope item during scoping and recommend the customer download critical attachments (enrollment documents, student records, contracts) before the migration date. We provide a written checklist of attachment record IDs for manual retrieval.

Flavor CRM integrates with QuickBooks, XERO, Carbonate, and PayNow for financial sync. These integrations store transaction IDs and sync tokens that do not migrate to Salesforce. We export the last 90 days of transaction history from the accounting system as a CSV and discuss whether to load it as a Custom Object in Salesforce or maintain it in the accounting system with a reference field on the Student Contact. This decision depends on whether Salesforce is intended to be the financial system of record post-migration.

Any custom properties defined by the institution in Flavor CRM (beyond the standard object schema) migrate to Salesforce custom fields on the corresponding object. Custom field API names follow Salesforce's __c suffix convention. We validate data types at migration time: multi-select values from Flavor CRM map to Salesforce multi-select picklists, date fields map to Date, and text fields map to Text or Long Text Area depending on content length.