Migrate from Flavor CRM to Twenty CRM

Flavor CRM Students map directly to Twenty CRM People records. Student name fields (first name, last name) map to the corresponding Twenty People fields. The enrollment date, enrollment status, and any custom student properties migrate as custom fields on the People record. We preserve the parent link (Flavor CRM's related Parent contact) as a custom People field storing the parent's email for cross-reference. Student-specific status values (active, enrolled, graduated, withdrawn) migrate as a multi-select picklist custom field in Twenty.

Flavor CRM Leads map to Twenty CRM People records using the same People object. Unlike Salesforce's separate Lead and Contact model, Twenty uses a unified People record for all individuals. We migrate the Lead source, Lead status, and any lead scoring value as custom fields on the People record. The Lead creation date and last activity date migrate as People creation and update timestamps for pipeline analysis.

Flavor CRM Parent records are separate contact-type objects linked to Student records. We export Parents as individual People records in Twenty and add a custom field student_email__c storing the linked student's email address. If a single Parent record appears in multiple Flavor CRM exports (linked to multiple students), we deduplicate by email and create a single People record with multiple student_email__c entries separated by semicolon, so the relationship remains queryable in Twenty.

Flavor CRM Opportunities map 1:1 to Twenty CRM Opportunity records. Opportunity name, amount, stage, expected close date, and owner email migrate directly. Pipeline stage values from Flavor CRM are mapped to Twenty Opportunity stage values that we configure during workspace setup. Closed-won and closed-lost reasons from Flavor CRM become custom Opportunity fields in Twenty.

Flavor CRM Contracts are distinct records linked to a Student or Company. Twenty has no native Contract object, so we create a Custom Object named Enrollment Contract with fields for contract number, student reference (via People email lookup), company reference (via Company name lookup), contract start and end dates, total value, and status. The custom object is created in Twenty Settings > Data Model before any CSV import begins, per Twenty's documentation requirement that fields exist before import.

Flavor CRM Class records have no native equivalent in Twenty. We create a Custom Object named Class with fields for class name, subject, schedule day and time, instructor (linked to a Staff People record by email), enrollment capacity, and current enrollment count. We also create a Class Enrollment custom relationship field linking the Class to the enrolled People records so that student-class attendance and enrollment history are queryable. This is the most education-specific mapping and requires the most schema design time.

Flavor CRM Invoices are financial documents stored in the billing module, not as CRM notes or attachments. We export Invoice records as line items and create a Custom Object named Invoice in Twenty with fields for invoice number, student reference (People email lookup), invoice date, due date, total amount, amount paid, balance due, and status. Payment history lines migrate as related Invoice Payment records under the same custom object. We flag whether the customer wants to load invoices as custom objects or attach PDF exports to the People record.

Flavor CRM Staff records map to Twenty CRM Workspace Members. We extract staff name, email, role, and permission level and create the corresponding Workspace Members in Twenty before importing any People or Opportunity records, because Twenty requires user accounts to exist before assigning Owner references on imported records. Per Twenty's documentation, workspace members must be invited and accept their invitation before Owner lookups resolve during import.

Flavor CRM Activities (calls, emails, meetings, tasks, notes) are exported per activity type. We map call activities to Twenty Task records with TaskSubtype set to Call and call duration stored in a custom field. Email activities migrate as Note records in Twenty with the email body preserved as rich text. Meeting activities migrate as Note records with date, time, and location stored in custom note fields. Task activities (non-call, non-email) migrate as Twenty Task records with Status, Priority, and due date preserved. Activity timestamps are preserved on all records to maintain the historical timeline.

Flavor CRM does not expose a documented bulk export endpoint for media and binary attachments. Media transaction reports export as CSV or Excel but binary file attachments require individual manual downloads per record. We flag this as a manual step during scoping, generate a per-record attachment inventory list from the Flavor CRM CSV export, and advise the customer on whether to download files manually or route the work to a data entry assistant. Twenty supports file attachments via ContentDocument records linked to People, Opportunity, or Custom Objects, but those files must be available locally before we can attach them.