Migrate from Simplicity Enterprise CRM to Pipedrive

Simplicity Contact records map directly to Pipedrive Person. Standard fields (first_name, last_name, email, phone, address) map cleanly. We handle the name-split during transform: if Simplicity stores a single full_name field, we parse and separate into first_name and last_name. Any custom fields on the Contact record map to Pipedrive custom fields on Person, created during schema phase. Simplicity contact owner maps to Pipedrive user_id via email lookup.

Simplicity Company records map to Pipedrive Organization. Company name, address, phone, website, and industry fields map 1:1. Organization is created before Person import so that the organization_id reference on Person is satisfied at insert time. Custom fields on Company map to Organization custom fields created during schema phase.

Simplicity stores Contact-to-Company as a relational link. In Pipedrive, the link between Person and Organization is established by setting org_id on the Person record. We resolve the org_id by matching Company name or domain during the Person import phase.

Simplicity Deal records map to Pipedrive Deal. Deal name, value, expected_close_date, and stage map to title, value, close_date, and stage_id respectively. Stage mapping requires explicit value translation because Simplicity stage names are client-defined and Pipedrive stages are pipeline-specific integer IDs. We configure the Pipedrive pipeline and stages before Deal import.

Simplicity deal pipeline stages are configurable per client. Each Simplicity stage name maps to a corresponding Pipedrive stage within the target pipeline. Stage probability percentages from Simplicity are stored as stage_order values or custom fields in Pipedrive, since Pipedrive does not expose stage probability at the API level for all tiers.

If Simplicity has multiple deal pipelines (possible in multi-module configurations), we create corresponding Pipedrive pipelines during schema setup. Each pipeline gets its own set of stages and a display order. Pipedrive supports multiple pipelines from Lite tier.

Simplicity Activities are linked to Contact and Company parents. We export the full activity table explicitly (not just Contact rows) and map by type: email to Pipedrive Activity type=email, call to type=phonecall, meeting to type=meeting, note to type=note. The person_id and org_id references on each Pipedrive Activity are resolved from the Contact and Company mapping done in earlier phases. Activity timestamps preserve the original Simplicity dates.

Simplicity Campaign records track multi-channel campaign execution. Pipedrive does not have a native campaign object at the Lite and Growth tiers. We map campaigns to Pipedrive Activities with type=note and a subject prefix (e.g., Campaign: Spring 2025 Email) so that campaign context is searchable in Pipedrive. If Pipedrive's Campaign add-on is active on the destination account, we map directly to the Campaign object.

Simplicity campaign response tracking stores which contacts responded to which campaign through which channel. Pipedrive has no campaign-response object. We map responses to tagged Activities: an Activity record with type=note, subject=Campaign Response, and a custom field campaign_name__c and response_channel__c preserved. This preserves the behavioural signal without disrupting Pipedrive's activity model.

Simplicity segments define which contacts belong to which behavioural or demographic groups. Segment membership does not map directly to Pipedrive lists or static groups. We map segment membership to a multi-select custom field on Person (segment__c) containing all applicable segment labels, or to Pipedrive Labels if the customer prefers label-based segmentation. The customer chooses the strategy during scoping.

Simplicity Loyalty module stores reward tiers, point balances, and program membership as relational records. Pipedrive has no loyalty module. We handle loyalty data as custom fields on the Person record (loyalty_tier__c, loyalty_points__c, program_name__c) or as a structured JSON attachment, depending on the volume and the customer's preference. We document the chosen archival strategy in the migration scope.

Simplicity's configurable data structure means custom fields exist on Contacts, Companies, Deals, and potentially other objects per client instance. During schema discovery we enumerate every active custom field and its data type. We pre-create each field in Pipedrive before migration, respecting Pipedrive's custom field type constraints (text, numeric, date, single-select, multi-select, boolean, user). Pipeline-specific custom fields require the Premium tier or above.