Migrate from Fat Free CRM to Pipedrive

Fat Free CRM accounts (name, website, phone, billing address, assigned user) map directly to Pipedrive Organizations. The account name becomes the Organization name and serves as the dedupe key during import. We resolve the assigned user against the Pipedrive user roster by email. Organizations are inserted before People to satisfy the Organization-People lookup that Pipedrive enforces when linking People to Organizations.

Fat Free CRM contacts (name, email, phone, title, link to Account) map to Pipedrive People. The contact_accounts join table resolves which Organization each Person belongs to; we set the org_id field on the Person record during insert. The contact's assigned user maps by email to a Pipedrive User. If a Contact has no associated Account in the source, we import it as an unlinked Person — orphaned from an Organization perspective but not dropped.

Fat Free CRM Leads (with status, source, rating, assigned user) map to Pipedrive Leads. Pipedrive's Lead object is distinct from its Person object and supports a separate Lead status field. We preserve the Fat Free CRM lead status as the Pipedrive Lead status value, the source as a custom field, and the rating as a custom field or label. Leads do not automatically convert to People during migration; the customer's sales team reviews and converts them manually post-migration.

Fat Free CRM Opportunities (stage, amount, probability, close date, link to Contact) map to Pipedrive Deals. The opportunity stage maps to a Pipedrive pipeline stage that we configure before migration. Pipedrive requires a Deal to link to a Person, an Organization, or both; we use the opportunity's linked Contact to resolve the Person reference, then derive the Organization ID from the Contact-Account relationship. If no Contact is linked to the Opportunity, the Deal is inserted as an unlinked Deal pending manual association.

Fat Free CRM's single pipeline stages map to a Pipedrive pipeline we create during migration. Each stage name and probability percentage from the source become a Pipedrive stage entry. If the customer uses multiple deal pipelines via a custom plugin, we create multiple Pipedrive pipelines with corresponding stage sets. Stage order and probability values are preserved as configured.

Fat Free CRM Tasks (title, body, due date, category, completion status, assigned user) map to Pipedrive Activities with type = task. Due dates and assignees migrate; open tasks insert with status open and completed tasks with status completed. The activity date is set to the original task due date or completion date. Tasks linked to Opportunities or Contacts in Fat Free CRM carry their parent reference in the Pipedrive Activity's related_object and related_object_id fields.

Fat Free CRM notes attached to Contacts, Accounts, or Opportunities map to Pipedrive Activities with type = note. The note body migrates as the activity subject or body field. Parent record associations (contact_id, account_id, opportunity_id) map to Pipedrive's related_object and related_object_id structure. Notes without a parent record are inserted as standalone notes.

Fat Free CRM Campaigns (name, status, budget, target metrics) have no direct Pipedrive equivalent. We import Campaign records as a custom field set on the Contact or as a Label in Pipedrive, depending on whether the customer needs to query by campaign membership. Campaign-contact associations (from the subscriptions or tag tables) migrate as Labels on the linked Person. The campaign metrics (budget, target) are stored in a migration reference table for the admin to review.

Fat Free CRM internal user IDs have no meaning in Pipedrive. We export the full user roster (id, email, first_name, last_name, role) as a reference table. Pipedrive user accounts are created by the customer in advance of migration. We resolve each Fat Free CRM owner_id by matching the user email to the provisioned Pipedrive user and store the Pipedrive user_id for use as the owner reference on all migrated records.

Fat Free CRM Groups function as organisational access-control units. Pipedrive's visibility groups (Restricted, Shared, Entire company) serve a similar purpose at a simpler level. We map group membership to Pipedrive Teams, which control record visibility per user. If a group structure is complex (nested groups, partial overlaps), we document the mapping and the customer configures Pipedrive visibility groups post-migration.

Fat Free CRM custom fields on Accounts, Contacts, Leads, and Opportunities may exist as serialized columns or plugin-added schema columns. We extract all custom field definitions and values during schema discovery. In Pipedrive, custom fields are key-value pairs created via the API (field type, label, key). We create matching Pipedrive custom fields before migration, then map values by matching the field key. Custom field keys in Pipedrive are alphanumeric hashes assigned at creation time; we preserve the original Fat Free CRM field name in the Pipedrive field label for discoverability.

Fat Free CRM uses a global tagging system (acts_as_taggable) applied across Contacts, Accounts, Opportunities, and Leads. Pipedrive Labels serve a similar tagging function. We extract the full tag set per record from the taggings and tags tables, then apply labels to the corresponding Pipedrive Person, Organization, or Deal. Label names are preserved exactly. If a tag is used across multiple object types in the source, we apply the same label in Pipedrive to each record regardless of type.