Migrate from Fat Free CRM to Nutshell

Fat Free CRM Accounts map directly to Nutshell Companies. We extract name, website, phone, and billing address from the accounts table and use the Company name as the dedupe key during import. The owner_id from Fat Free CRM resolves to a Nutshell owner via email lookup on the People table post-provisioning. Address fields migrate to Nutshell's address compound field. Account categories and tags (acts_as_taggable) attach as Nutshell tags on the resulting Company record.

Fat Free CRM Contacts map to Nutshell People with a 1:1 field-level correspondence: first_name, last_name, email, phone, title, and department all have direct equivalents. The contact_accounts join table resolves the account_id to a Nutshell Company lookup that we set as the contact's company reference during import. Tags from the contacts table migrate as Nutshell tags on each Person record.

Fat Free CRM Leads are a distinct pre-conversion object with status, source, rating, and assigned user. We import Leads as Nutshell People with a custom field ffcrm_lead_source__c carrying the original lead source, and a status field indicating whether the record was converted or unconverted at migration time. The assigned user resolves via email lookup. Lead ratings (cold, warm, hot) map to a custom rating field rather than a native Nutshell field.

Fat Free CRM Opportunities map to Nutshell Deals with stage, amount, probability, and close date preserved. The opportunity.account_id resolves to the Nutshell Company lookup at migration time. Nutshell Deals support multiple contacts per deal, which handles the opportunity_contact many-to-many join from Fat Free CRM; we import the opportunity_contacts link table as a secondary lookup pass after Deals and People exist in Nutshell.

Open tasks in Fat Free CRM migrate to Nutshell Tasks with title, body, due_date, category, and completion status. Completed tasks are optional and migrate only if the customer requests them; by default we import open tasks to avoid flooding the destination with resolved work. Nutshell does not have a separate activity object for historical task data, so due_date and completion tracking use Nutshell's native task fields.

Fat Free CRM Campaign records track name, status, budget, and target metrics, with contact membership stored in tag tables. Nutshell has no native campaign object. We import Campaign records as Nutshell tags on Person records (e.g., tag: Campaign_Name) and add a custom field campaign_attribution__c on People to preserve campaign-level metrics where the customer requires them. Tag count per Person in Nutshell is limited to 100; records exceeding this threshold use an additional custom field for overflow.

Fat Free CRM's global tagging system (acts_as_taggable) stores tags as string tokens across Contacts, Accounts, Opportunities, and Leads. Tags map directly to Nutshell's native tag feature. We preserve the full tag set per record by enumerating the taggings table and attaching each unique tag token to the corresponding Nutshell People, Company, or Deal record at import time.

Fat Free CRM Users and Groups have no direct Nutshell equivalent because Nutshell's API does not expose user management endpoints. We export the full user and group roster as a reference table keyed by email, role, and group membership. The customer provisions Nutshell users manually post-migration, and we use the email-based lookup to reassign owner references on all migrated records during the import phase.

Fat Free CRM supports custom fields on Accounts, Contacts, Leads, and Opportunities via serialized columns or extension tables. We extract the custom field definitions from the database schema and migrate values to equivalent Nutshell custom fields, which are available on People, Companies, and Deals at all Nutshell tiers. Text fields exceeding 255 characters in Nutshell require a custom field type or are flagged for truncation during the scoping phase.