Migrate from Fat Free CRM to HubSpot

Fat Free CRM contacts map directly to HubSpot contacts. First name, last name, email, phone, and job title pass through as HubSpot properties with the same values. HubSpot's lifecycle_stage is applied as a default based on the Fat Free CRM contact's status field — active contacts default to 'customer' or 'lead' per your specification.

Fat Free CRM contacts with status 'converted' land in HubSpot as lifecycle_stage 'customer'. This preserves the conversion event without a separate lead record. If your Fat Free CRM uses a custom status field for lifecycle, we map each value to the nearest HubSpot lifecycle stage during migration.

Fat Free CRM accounts map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue map to HubSpot's corresponding company properties. Parent-account hierarchies in Fat Free CRM translate to HubSpot's parent company association field. We also preserve the account type field as a custom property since HubSpot lacks a native equivalent for categorizing accounts by type.

Fat Free CRM opportunities map to HubSpot deals with stage, amount, close date, and probability preserved. The opportunity name becomes the deal name. HubSpot's deal pipeline stages are configured to match the stage names from your Fat Free CRM setup, with probability values carried over as deal probability custom fields.

Fat Free CRM tasks map to HubSpot engagements based on their type field. Tasks flagged as calls become HubSpot call engagements with duration and outcome preserved. Email tasks become email engagements with subject and body. General to-do tasks become HubSpot tasks. Owner is resolved by email match to HubSpot users.

Fat Free CRM notes map to HubSpot notes on the associated contact or company record. Original timestamps and note body text are preserved. Rich-text formatting is converted to HubSpot's note content format. Notes with attachments trigger a separate file-migration step to HubSpot Files.

Fat Free CRM tags do not have a native HubSpot equivalent with the same semantics. We create a custom contact and company property (e.g., 'FFCRM_Tags') and join tag values with commas, or create a multi-select pick-list property if the unique tag count is under 200 values. Tag frequency is preserved as a count property for reporting continuity.

Fat Free CRM groups control data visibility and user permissions. HubSpot's teams are assignment buckets only — they do not enforce record-level sharing rules equivalent to Fat Free CRM's group model. We map each Fat Free CRM group to a HubSpot team and surface the original group membership as a custom contact/company property for admin reference.

Fat Free CRM file attachments are downloaded from the Rails storage path and re-uploaded to HubSpot Files. Each file is associated back to the originating contact, company, or deal record. Files over 300MB are flagged for manual handling since HubSpot's file hosting has a per-file size cap.

Custom fields added via Fat Free CRM plugins or Rails migrations become HubSpot custom properties. We infer the HubSpot property type from the database column type — varchar becomes string, integer becomes number, boolean becomes enumeration, date becomes date. Some Fat Free CRM field names may collide with HubSpot-reserved names and require a rename during mapping.

Fat Free CRM campaign tracking (if enabled via plugin) has no direct HubSpot equivalent without Marketing Hub. We preserve campaign membership as a contact property and recommend rebuilding campaign logic in HubSpot's lists once you have a Marketing Hub seat.

Fat Free CRM users are matched to HubSpot users by email address. Unmatched owners are flagged before migration so your team can invite them to HubSpot first or assign their records to a fallback owner. User role permissions in Fat Free CRM do not transfer — those must be reconfigured in HubSpot's native roles and teams.