Migrate from Followup CRM to Pipedrive

FollowUp CRM contacts map to Pipedrive Persons. First name, last name, email, phone, and job title migrate as direct field copies. The follow_up_date property requires conversion — FlitStack creates a linked task with a due date matching the original follow-up date and assigns it to the contact's owner.

FollowUp CRM companies map to Pipedrive Organizations. Name, domain, industry, number of employees, and annual revenue transfer directly as matching fields. Industry picklist values require mapping against Pipedrive's industry enumeration — any mismatched or custom values are flagged during the audit phase before import so your admin can decide whether to map them to existing Pipedrive options or create new picklist entries.

FollowUp CRM deals migrate to Pipedrive Deals. Deal name, value, expected close date, owner, and associated company/person links transfer. Pipeline stage name maps to Pipedrive stage_id within the target pipeline — stage_id is numeric and must resolve from the pipeline object created in Pipedrive before migration.

FollowUp CRM pipelines map to Pipedrive Pipelines. Each pipeline must exist in Pipedrive before deals are imported, because Pipedrive deals reference a pipeline_id (UUID) rather than a name string. FlitStack generates a pipeline creation plan with stage names and probability values based on the source pipeline configuration.

FollowUp CRM activity records (calls, emails, meetings) with timestamps and owner attribution map to Pipedrive Activities. Each activity type maps to Pipedrive's activity_type enum ('call', 'email', 'meeting'). The activity is linked to the migrated Person or Deal using Pipedrive's item_type and item_id reference fields.

FollowUp CRM custom properties on contacts require pre-creation in Pipedrive via POST /personFields. Each custom field gets a system_key (40-character hash) that Pipedrive assigns — FlitStack reads the created field keys and uses them in the bulk import payload. Field types (text, number, date, picklist) are mapped to Pipedrive's supported field_types.

FollowUp CRM deal custom properties migrate to Pipedrive Deal custom fields via POST /dealFields. Note that Pipedrive Leads inherit deal custom fields automatically — the same custom field appears on both Deal and Lead records after creation. This inheritance is useful for teams that use Leads in their sales flow, as qualification criteria stored on deal custom fields carry forward to the converted Lead record without re-entry.

FollowUp CRM notes attached to contacts, companies, or deals migrate to Pipedrive Notes. In Pipedrive, notes belong to an item (person, organization, or deal) identified by item_type and item_id. Rich-text formatting is preserved where possible; inline images are downloaded and re-hosted as file attachments.

FollowUp CRM team goals and quotas have no native Pipedrive equivalent. FlitStack migrates the most recent goal assignments and quota values as custom fields on the User (assignee) record. Historical goal-period data is preserved as JSON in a Goal_History__c text field for admin reference.

FollowUp CRM file attachments on contacts, companies, or deals are downloaded and re-uploaded to Pipedrive Files, linked to the target record by item_type and item_id. Pipedrive's file size limit is 100 MB per file on Professional+ plans. Files without an associated record are attached to the default organization or person owner.