Migrate from Flavor CRM to Nutshell

Flavor CRM Student records map directly to Nutshell People. The student's email becomes the People email field and the dedupe key. We preserve the Flavor CRM Student ID as a custom field (flavor_student_id__c) and any enrollment status or graduation year as custom fields on the People record. If the Student has an associated Parent in Flavor CRM, the parent link is stored as a custom People field (parent_contact__c) pointing to the parent's People ID, which we resolve after the parent import phase.

Flavor CRM Parent records map to separate Nutshell People records with a custom field (contact_type__c) set to 'Parent' to distinguish them from Student People. Parent-to-Student relationships are resolved after both record types are imported by matching the parent_reference field in Flavor CRM against the newly created Student People records and writing the relationship into parent_contact__c on the Student record.

Flavor CRM Leads map to Nutshell Leads. Lead status, source, and any custom properties migrate to Nutshell's Lead custom fields. The Lead-to-Student conversion link from Flavor CRM is stored as two custom fields on the Lead: converted_to_student_id__c and conversion_date__c. These fields allow the Nutshell admin to manually reconstruct which Student record the Lead converted to, since Nutshell does not have an automated Lead conversion mechanism.

Flavor CRM Opportunities map to Nutshell Deals. The deal stage maps to the nearest Nutshell pipeline stage, and the deal amount maps to the Nutshell monetary value field. We create the Nutshell pipeline stage mapping during scoping based on Flavor CRM's stage labels. If Flavor CRM has multiple pipelines, Nutshell's single pipeline model requires the customer to choose which pipeline maps to the primary Nutshell pipeline or whether to distribute across Tags.

Flavor CRM Contract records are exported with full contract metadata as a structured document. We export contract data as a JSON metadata file and attach it as a file to the related Student or Company People record in Nutshell via ContentDocumentLink. Contract line items and terms are stored as custom fields on the People record if the customer requests a flat structure, or as a separate CSV sheet for manual entry if the contract data is complex.

Flavor CRM Invoice records are exported as PDF files where available, or as structured CSV with line item details. We attach invoice PDFs to the related Student or Company People record in Nutshell as ContentDocument records. Invoice totals, payment status, and due dates are stored as custom fields (invoice_total__c, invoice_status__c, invoice_due_date__c) on the People record for quick reference. Actual invoice line items that require detailed financial tracking should be routed to the customer's QuickBooks or accounting system via the existing Nutshell-QuickBooks integration rather than stored in Nutshell's CRM layer.

Flavor CRM Class records have no native equivalent in Nutshell. We export Class data as a structured CSV (class_name, schedule, instructor, enrollment_count, capacity) and map it to Nutshell as tagged data: a custom field (enrolled_class__c) on the People record holds the primary class name, and a separate Classes CSV is delivered as a reference document for the customer to maintain in a spreadsheet or rebuild using Nutshell's Groups and Tags for segmentation. If Nutshell Groups are available in the customer's plan, we create a Group per Class and add People to the appropriate Group.

Flavor CRM Staff records map to Nutshell People with a custom field (user_type__c) set to 'Staff' to distinguish internal users from external Students and Parents. Staff email addresses map to People email for identification. Nutshell's User accounts for internal CRM access are provisioned separately by the customer; Staff People records are contact records only and do not become Nutshell Users unless the customer explicitly creates User accounts for them.

Flavor CRM engagement records (Email, Phone Call, Meeting, Task) map to Nutshell Activities. Each activity type is exported separately from Flavor CRM and mapped to the corresponding Nutshell Activity type. Activity timestamp, subject, description, and related Person or Opportunity links migrate to Nutshell's activity fields. Nutshell's activity timeline displays all activity types chronologically against the related People and Deals records.

Flavor CRM does not expose a bulk attachment export endpoint. We export binary attachments as individual file downloads where accessible via the web interface and attach them to the corresponding Nutshell People or Deal record via ContentDocumentLink. Media transaction reports from Flavor CRM are exported as CSV and cross-referenced with the file download list to confirm coverage. Any attachments that cannot be individually retrieved are listed in a missing_attachments.csv delivered alongside the migration with instructions for manual upload.