Migrate from Fat Free CRM to HighLevel

Fat Free CRM Accounts (name, website, phone, billing address) collapse into GoHighLevel Contact records. The Account name maps to contact.company_name, website maps to contact.website, and phone maps to contact.phone. Since GoHighLevel has no separate Account object, the Account-Contact link table in Fat Free CRM is resolved by setting the company_name field on each Contact. The contact_type is set to customer for Accounts with closed-won Opportunities, lead for Accounts with open pipeline only, and prospect otherwise.

Fat Free CRM Contacts map directly to GoHighLevel Contacts with first_name, last_name, email, phone, title, and address fields preserved. The contact_accounts join table is used to set the company_name field on each Contact at migration time. Tags attached to Contacts (via acts_as_taggable) migrate as GoHighLevel Tags applied to the Contact record.

Fat Free CRM Leads map to GoHighLevel Contacts with contact_type set to lead. The Lead status field maps to a custom field ffc_status__c, source maps to ffc_lead_source__c, and rating maps to ffc_rating__c. If the Fat Free CRM Lead has been converted (has a linked Contact or Account), we resolve the relationship and migrate the Contact with the converted company_name rather than creating a duplicate Lead in GoHighLevel.

Fat Free CRM Opportunities map to GoHighLevel Opportunities. The opportunity_accounts join table resolves the Account name for the linked company_name on the Opportunity. Stage, amount, probability, and close date migrate to GoHighLevel's stage, value, and close_date fields. We create a GoHighLevel pipeline matching the Fat Free CRM pipeline structure, with stages mapped to pipeline stages, during the configuration phase before data import begins.

Fat Free CRM Tasks (title, body, due date, category, completion status) map to GoHighLevel Tasks. Open tasks and completed tasks both migrate; completed tasks retain their completion status and the original completion timestamp in a custom field ffc_completed_at__c. Tasks linked to an Opportunity or Contact in Fat Free CRM are linked to the corresponding GoHighLevel Opportunity or Contact via the migration-assigned record IDs.

Fat Free CRM Campaigns (name, status, budget, target) have no direct GoHighLevel equivalent. We migrate campaign records to a GoHighLevel custom object named Campaign with the original campaign name, status, and budget fields preserved. Contact membership in campaigns is reconstructed from the campaign_subscriptions and tag join tables and linked via custom relationship fields on the Campaign custom object.

Fat Free CRM's global tagging system (acts_as_taggable) stores tags as string tokens in a separate table. We preserve the full tag set per record and import them as GoHighLevel Tags applied to the corresponding Contact, Lead, Opportunity, or Account-equivalent record. Tags with identical names are deduplicated at import time.

Fat Free CRM user IDs have no meaning in GoHighLevel. We export the full user roster (name, email, role) as a reference table. The customer provisions GoHighLevel workspace users by email invite before migration. We then remap Fat Free CRM owner_id references to the corresponding GoHighLevel user by email match during the data load phase.

Fat Free CRM Groups (organisational units for access control) map conceptually to GoHighLevel Teams. We extract the group membership table and deliver a team structure mapping as a written configuration guide. GoHighLevel Teams are created by the customer, and record ownership is reassigned based on the group membership list we export.

Fat Free CRM custom fields on Accounts, Contacts, Leads, and Opportunities (stored as serialized fields or extension tables) are extracted with their definitions and values. We create matching GoHighLevel custom fields (text, number, date, dropdown) during the schema configuration phase before data import. Plugin-extended columns discovered during schema discovery are included in this mapping pass.