Migrate from Fat Free CRM to Twenty CRM

Fat Free CRM Account records map directly to Twenty CRM Company records. The Account name becomes Company name, website maps to the website field, and phone maps to the phone field. Billing address columns in the accounts table map to company address fields. The account's assigned user_id maps to the owner field in Twenty CRM by email lookup against the Twenty CRM user roster. Accounts with no assigned user default to the migration user until the customer remaps ownership post-migration.

Fat Free CRM Contact records map to Twenty CRM Person records. The contact's first name, last name, email, phone, and title transfer directly. The contact_accounts join table preserves the many-to-one link to the Account; we resolve the Account ID first (or create the Company in Twenty CRM) so that the contact-company relationship is established at import time. Contacts without an associated account import as Persons with no company link.

Fat Free CRM Leads are distinct from Contacts in the source schema and carry status, source, rating, and assigned user fields that have no direct Twenty CRM equivalent. We import Leads as Persons and append a custom text field or tag capturing the original lead status (new, contacted, qualified, converted) and lead source. The customer's admin reviews and sets the appropriate Person type in Twenty CRM after migration.

Fat Free CRM Opportunity records map to Twenty CRM Opportunity records. Stage, amount, probability, and close date transfer directly. The opportunity_contacts join table is critical — we resolve each linked Contact's new Twenty CRM Person ID and attach it to the Opportunity. Without join table resolution, opportunities in Twenty CRM appear disconnected from the people working them.

Fat Free CRM Task records map to Twenty CRM Task records. Title, body, due date, category, and completion status transfer. Assigned user_id resolves via email to the Twenty CRM user roster. Tasks linked to a Contact or Opportunity carry the resolved Person or Opportunity ID in the Twenty CRM target object field. Open and completed tasks both migrate; the status field preserves completion state.

Fat Free CRM Campaign records (name, status, budget, target metrics) map to Twenty CRM Target List records. Contact-campaign membership is stored in the tag_subscriptions or contacts_tags join table depending on Fat Free CRM version; we reconstruct the membership by resolving each contact's new Twenty CRM Person ID and associating it with the corresponding Target List. Status mapping: active campaigns become active target lists, completed campaigns become archived.

Fat Free CRM's global tagging system (acts_as_taggable) stores tags across Contacts, Accounts, Opportunities, and Leads in a separate tagging table. We extract the full tag set per record and decide with the customer whether to map tags to a single multi-value custom field in Twenty CRM or to a tagging implementation in the target object's notes. This decision depends on how heavily the customer uses tagging for segmentation.

Fat Free CRM Users (name, email, role, team membership) export as a reference roster keyed by email. Twenty CRM manages its own user directory, so we cannot provision users or reassign ownership automatically. The roster is delivered as a CSV mapping source user_id to email, and the customer creates corresponding users in Twenty CRM before the final migration pass. Ownership assignments on migrated records reference the roster for manual remapping.

Fat Free CRM Groups represent organisational units used for access control. Twenty CRM does not have an equivalent Group concept as a first-class CRM object. We export group membership as part of the user roster and document which Fat Free CRM users belonged to which groups. The customer maps these to Twenty CRM team structures or user roles post-migration.

Fat Free CRM custom fields on Accounts, Contacts, Leads, and Opportunities are stored as extended columns in the core tables (plugin-extended schema) or in a separate custom_fields table depending on version. We run schema discovery first, enumerate every custom column, and create matching custom fields in Twenty CRM before data import. All custom field values transfer as text for maximum compatibility; the customer validates type conversion in the Twenty CRM settings UI post-migration.

Fat Free CRM stores uploaded files on the host server's filesystem or a configured S3 bucket, not in the database. We enumerate every attachment record (filename, path, associated record type and ID) and deliver a file inventory CSV. The customer copies files to Twenty CRM's storage layer manually. Binary attachment content cannot be extracted through our standard database connection and is explicitly excluded from migration scope.