Migrate from Fat Free CRM to Freshsales

Fat Free CRM accounts table stores name, website, phone, billing address, and assigned user ID. We extract these fields and map them directly to Freshsales Account fields. The account's assigned user_id resolves to a Freshsales User by email lookup once the customer has provisioned Freshsales user accounts. Multi-address or multi-contact relationships encoded in join tables are preserved as Freshsales Contact-to-Account links. Standard tier and edition constraints do not apply to Account object ingestion — all Freshsales tiers support Accounts.

Fat Free CRM contacts store name, email, phone, title, and a foreign key to the parent account. The contact_accounts join table preserves the many-to-one relationship. We map contacts to Freshsales Contacts with the AccountId lookup resolved at import time. Duplicate contacts (same email) are flagged in a pre-import report for the customer to resolve before record insertion.

Fat Free CRM leads are a distinct pre-conversion object with status, source, rating, and assigned user fields. We map Leads directly to Freshsales Leads, preserving lead status, source attribution, and rating. Any tag memberships on leads migrate as Freshsales tag assignments. The customer decides whether to keep leads as Leads or convert them to Contacts during the scoping phase.

Fat Free CRM opportunities store deal name, stage, amount, probability, close date, and links to a contact and account. We map these to Freshsales Deals with the pipeline stage mapped to a Freshsales pipeline stage value, and the amount and probability preserved as numeric fields. The opportunity_contact join table is preserved as a Freshsales Deal Contact association. Deal ownership maps via the email-based user lookup.

Fat Free CRM tasks include title, body, due date, category, completion status, assigned user, and optional links to opportunity or contact. We map open and completed tasks to Freshsales Tasks, preserving title, description, due date, status, and category. Task assignment resolves through the email-based owner mapping. Tasks linked to Opportunities or Contacts retain those associations in Freshsales via the WhatId and ContactId fields.

Fat Free CRM campaigns store name, status, budget, and target metrics. Contact-campaign membership is stored in the tag and subscription tables. We import campaign records and rebuild contact-campaign associations by enumerating the tag memberships linked to each campaign. Note that Freshsales Campaign metrics (budget tracking, target versus actual) are basic compared to dedicated marketing platforms; we document the metrics available in Freshsales and flag any campaign data that has no destination field for the customer to acknowledge.

Fat Free CRM uses a global ActsAsTaggable system storing tags as string tokens in a separate table. Tags are attached to Contacts, Accounts, Opportunities, and Leads via join tables. We extract the full tag set per record and map to Freshsales Tags. Freshsales stores tags as a separate Tag object linked to records via tag assignments. Because multiple tags can exist per record, we create tag records first, then insert tag assignments in a second pass.

Fat Free CRM supports custom fields on Accounts, Contacts, Leads, and Opportunities via a serialized field or extension table. We extract custom field definitions and their stored values during schema discovery. Custom fields map to Freshsales custom fields on the corresponding object. Plugin-extended columns (added by third-party Fat Free CRM plugins) may not have documented types; we infer field type from the column schema and flag any ambiguous types for the customer to confirm before destination field creation.

Fat Free CRM stores internal user accounts with role, team, and login credentials. These IDs have no persistence in Freshsales because Freshsales maintains its own user directory. We export the full user roster as a reference table including email, name, and role. Freshsales user accounts must be created by the customer before migration begins. Ownership mapping resolves by matching the Fat Free CRM user email to the Freshsales user email at record import time.

Fat Free CRM groups serve as organisational units for access control and data sharing. The group concept does not map directly to any Freshsales object, but group membership can be preserved as tags on user records or noted in a supplementary access matrix delivered alongside the migration. We extract group membership as a separate table and document it as a reference for the customer to implement via Freshsales role and territory configuration post-migration.