Migrate from Flavor CRM to Pipedrive

Flavor CRM Students map to Pipedrive People. Student name, email, phone, address, and enrollment status transfer as typed fields. We preserve the Flavor CRM Student ID as a custom field (flavor_student_id__c) on the Person for cross-reference. Parent link data is extracted separately and stored as custom fields on the Person (parent_name__c, parent_email__c, parent_phone__c) because Pipedrive People does not support a native parent-child contact relationship. Enrollment history dates and enrollment status migrate as custom date and picklist fields on the Person.

Flavor CRM Parent records attach to Student records as related contacts. We extract the Parent's name, email, and phone and merge them into the mapped Student Person record as custom fields rather than creating separate Person records, since Pipedrive does not natively represent the Parent-Student relationship as a typed object. If the institution requires separate Parent Person records for reporting or communication workflows, we create them as linked Persons and document the linking strategy during scoping.

Flavor CRM Leads map to Pipedrive Leads. The Lead's source, status, and assigned counselor migrate as standard Pipedrive Lead fields with any education-specific custom properties (enquiry_grade__c, enquiry_program__c, enquiry_intake__c) carried over as custom fields. The Lead-to-Student conversion chain is reconstructed post-migration by linking the converted Person record to its originating Lead via a custom field (original_lead_id__c) that references the Flavor CRM Lead ID preserved during export.

Flavor CRM creates a permanent reference link when a Lead converts to a Student. This link does not survive CSV export. We extract the conversion timestamp and Flavor CRM student_id as a pair of custom fields on the migrated Pipedrive Person (converted_at__c, flavor_student_id__c). This allows the institution to reconstruct the enrollment funnel historically. The customer's Pipedrive admin documents the original pipeline stages during scoping so that deal stage reports can be rebuilt using the migrated enrollment data.

Flavor CRM Opportunities representing active enrollments map to Pipedrive Deals. The deal stage maps to Pipedrive stage (Appointment Scheduled → Enrollment Application → Interview Complete → Enrollment Confirmed → Closed Won). We attach the associated Student (Person) as the Deal's Person link and add the parent contact details as custom fields on the Deal for administrative access. Closed-Lost and withdrawal reasons from Flavor CRM become custom picklist fields on the Pipedrive Deal.

Flavor CRM Invoice records have no direct Pipedrive equivalent. During scoping, we determine whether the institution wants invoice data loaded as Pipedrive Custom Objects (requiring Professional tier or above), attached as PDF files to the related Student Person record, or routed to an external accounting tool via integration. We export invoice line items, payment status, outstanding balance, and due date as structured fields. The decision between Custom Object and PDF attachment affects schema design before migration begins.

Flavor CRM Class records with schedule, enrollment capacity, instructor, and term data have no native Pipedrive equivalent. We export Class data as structured CSV and recommend loading it as a Pipedrive Custom Object (Class) with custom fields for schedule, instructor, capacity, and enrollment count. Alternatively, Pipedrive Groups can represent class cohorts if the institution prefers a lighter-weight mapping. The customer selects the approach during schema design. Ongoing class scheduling beyond initial data migration requires a dedicated scheduling tool integrated with Pipedrive.

Flavor CRM Activities (calls, emails, meetings, tasks, notes) against Students and Opportunities map to Pipedrive Activities. Each activity type exports separately and maps to the corresponding Pipedrive Activity type. We resolve the activity's subject Person or Deal reference during migration so that the Activity timeline in Pipedrive shows the correct linked record. Activity dates and timestamps preserve for historical reporting. Note content migrates as Activity notes with the original timestamp maintained.

Flavor CRM Staff records map to Pipedrive Users by email match. Staff roles and permissions from Flavor CRM (admission_counselor, teacher, finance_admin) migrate as custom fields on the Pipedrive User (flavor_role__c). Any Staff record without a matching Pipedrive User email goes to a reconciliation queue for the customer's admin to provision before record import. Inactive Staff records in Flavor CRM become inactive Pipedrive Users assigned to no Deals.

Flavor CRM does not expose a documented bulk export endpoint for binary attachments. Media files, enrollment documents, and student records with attached files cannot be migrated programmatically. We export a manifest CSV listing every attachment with its associated Student or Contact ID and recommended filename. The customer's team downloads files individually or uses the Flavor Studio API individually if available. We do not migrate attachment binaries as a standard migration deliverable.