Migrate your Fat Free CRM data

Accounts map 1:1 to Companies/Accounts in most destination CRMs. Fat Free CRM stores name, website, phone, billing address, and an assigned user/owner. We extract from the accounts table and preserve the owner assignment via user ID cross-reference.

Contacts store name, email, phone, title, and a link to an Account. The contact_accounts join table preserves the many-to-one relationship. We map Contacts directly to Contacts in the destination and rebuild the account linkage by name or external ID.

Leads are a distinct pre-conversion object with status, source, and rating fields. We extract the full lead record including assigned user and tag memberships. On import, Leads map to Leads or get merged into Contacts depending on destination schema.

Opportunities link to a Contact and an Account, track stage, amount, probability, and close date. We preserve the opportunity_contact join table to ensure each deal is associated with the correct contact record in the destination.

Tasks belong to a user and optionally to an Opportunity or Contact. Standard fields include title, body, due date, category, and completion status. We import open and completed tasks and recreate the parent linkage using destination foreign keys.

Campaigns track name, status, budget, and target metrics. Tag memberships link contacts to campaigns. We import campaign records and rebuild contact-campaign associations from the tag and subscription tables, which requires value-mapping in the destination.

Fat Free CRM uses a global tagging system (acts_as_taggable) across Contacts, Accounts, Opportunities, and Leads. Tags are stored as string tokens in a separate table. We preserve the full tag set per record but note that destination CRMs may handle tag namespaces differently.

Users represent your internal team members with login credentials, role (admin, user), and team membership. Because the destination CRM will have its own user directory, we extract the user roster and map them to destination users by email, flagging any unmapped owners as needing manual reassignment.

Groups in Fat Free CRM are organisational units used for access control and data sharing. The concept does not exist as a first-class object in most SaaS CRMs. We map group membership to team structures or static groups in the destination where possible.

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 values, then map them to custom properties in the destination, noting that field type (text, number, date, dropdown) must be verified.

File attachments uploaded to Contacts, Accounts, or Opportunities are stored on the local filesystem or cloud storage bucket configured by the host. We cannot reliably extract binary attachments without direct server access. We flag attachment records so the customer can decide whether to copy files manually post-migration.