Migrate from Flavor CRM to HubSpot

Flavor CRM contacts map directly to HubSpot contacts. Name, email, phone, job title, address, and company association transfer 1:1. Parent and guardian contacts store relationship type in a custom property since HubSpot's contact model has no native parental-relationship field. During migration we verify email format, flag duplicate contacts, and map any custom Flavor fields to HubSpot custom properties to preserve additional context.

Flavor CRM companies map to HubSpot companies. Name, domain, industry pick-list, employee count, and annual revenue transfer directly. Industry pick-list values map value-by-value where Flavor's values match HubSpot's defaults; non-matching values become custom pick-list options created during schema setup. We also validate domain uniqueness and resolve any duplicate company names before import to avoid creating redundant records in HubSpot.

Flavor opportunities map to HubSpot deals with the deal name, amount, stage, and close date preserved. Stage values map to HubSpot pipeline stages by name. Owner is resolved by email match against HubSpot users. Pipeline assignments transfer as deal properties; HubSpot's pipeline feature manages stage ordering.

Flavor's student entity has no HubSpot native equivalent — it is recreated as a HubSpot custom object (Professional+ plans) with properties for enrollment status, grade level, date of birth, and class assignments. The student record is associated to the parent contact record via HubSpot's association API.

Flavor stores parents as contact-type records. These become HubSpot contacts. The parent-to-student relationship is preserved using HubSpot's contact-to-contact associations with a custom relationship-type label (e.g., 'Parent of Student: [Student Name]) rather than a separate junction object. We also set a custom property on the parent contact to record the student's ID, enabling quick look‑ups and reporting across the family.

Flavor's class and section entities map to a HubSpot custom object named 'Class' with properties for class name, semester, schedule, and teacher. Each class is associated to enrolled student records via HubSpot's custom-object associations. We also capture enrollment capacity and room assignment as additional custom properties, allowing reports on class size and resource allocation.

Flavor invoice records (billing amount, status, payment date, due date) have no native HubSpot equivalent and migrate to a custom Invoice object. Invoice-to-contact and invoice-to-student links are preserved as HubSpot associations. Note that HubSpot does not process payments — the invoice record is a reference record only.

Flavor contracts with start date, end date, and contract value map to HubSpot deals with a custom 'Contract ID' property and 'Contract Value' field. Contracts that are not enrollment-related become deals in the default pipeline. Enrollment contracts are tied to the relevant student record via deal association.

Flavor activities are type-discriminated in a single object. Each type maps to HubSpot's corresponding engagement type — calls become calls, emails become emails, meetings become meetings, and tasks become tasks. Original timestamp, owner, and parent record link are all preserved through HubSpot's engagement association model.

Flavor leads that are prospective students or guardians without an enrollment record map to HubSpot contacts with a 'Lead Status' custom property. If Flavor tracks lead score or source, those properties migrate as HubSpot custom number and pick-list fields respectively.

Flavor CRM users and owners are matched to HubSpot owners by email address. Records belonging to Flavor users with no corresponding HubSpot account are flagged for assignment to a fallback HubSpot owner before the migration commits. We also record the original Flavor user ID on each record so post‑migration audits can trace ownership changes and maintain compliance.

Flavor file attachments on contacts, companies, deals, or student records are downloaded and re-uploaded to HubSpot's file storage. Files are associated to the corresponding HubSpot record by ID. HubSpot's file size limit (25MB per file) applies; oversized files are flagged for manual handling.