Migrate from Membrain to Pipedrive

Membrain Companies map directly to Pipedrive Organizations. Standard fields (name, address, industry, website) map to Pipedrive's equivalent Organization fields. The organization's domain name from Membrain becomes the Organization's website field. We deduplicate by exact name match on import and link any child People records via the org_id relationship that Pipedrive maintains.

Membrain Contacts map to Pipedrive People. Standard fields (name, email, phone, title) map directly. Custom fields migrate to Pipedrive Person custom fields, which we create in the destination account before import using the GUID-to-label lookup table derived from Membrain's custom field definitions. Email address is the dedupe key for Person records.

Membrain Prospects (from the Prospecting module) map to Pipedrive Leads if the destination Pipedrive account has the Leads feature enabled. Prospect lifecycle stages map to Pipedrive Lead Status values. If the customer has not licensed the Pipedrive Leads module, Prospects map to People with a custom field prospect_stage__c preserving the original Membrain lifecycle status. Enrollment in Membrain automations is documented but not migrated as code.

Membrain Sales Projects map to Pipedrive Deals. The key migration work is stage mapping: Membrain allows each Sales Project type to define its own stages with arbitrary names, probabilities, and step counts. We extract the full stage definition from Membrain, create matching Pipedrive pipeline stages ordered by probability, and map each Membrain stage name to the corresponding Pipedrive stage by position. Expected close date, deal value, currency, and owner map directly. Closed-won and closed-lost reasons map to Pipedrive custom fields.

Each Membrain Sales Project type defines its own stage set. We read the stage definitions during discovery, create Pipedrive pipelines to mirror the Membrain product structure, and create stages within each pipeline ordered by win-rate probability. If Membrain stage history exceeds Pipedrive's standard stage field capacity, we log the full stage progression as a DealActivity custom field or as linked Notes on the Deal record.

Membrain Account Growth Projects track expansion and account planning work at the Company level and have their own workflow and custom fields. Pipedrive has no native Account Growth Project equivalent. We map Account Growth Projects to Deals with a custom field ag_project_type__c set to Account Growth, linked to the same Organization as the original Sales Project. The account growth-specific custom fields migrate to Deal custom fields. If the customer uses Account Growth Project workflows, we document them for Pipedrive Workflow Automation rebuild.

Membrain Activities (Appointments, Calls, Notes, Emails, Tasks) each carry their own custom field sets and link to specific record types. We migrate all activity types to Pipedrive Activities preserving the activity-to-record linkage (org_id for Organization-linked, person_id for People-linked, deal_id for Deal-linked). Activity timestamps preserve chronological ordering. Call disposition and duration migrate to Pipedrive custom Activity fields. Email content migrates as a Note attached to the related Person or Deal.

Membrain custom fields use the CustomField{GUID} property naming convention. We resolve this by querying Membrain's custom field definitions first, building a GUID-to-label lookup table, then substituting human-readable field names when mapping to Pipedrive. Pipedrive custom fields are created in the destination account using the Pipedrive API before any data is imported. Field types are mapped: text to string, number to numeric, date to date, dropdown to picklist, checkbox to boolean.

Membrain Full User accounts (can own records, trigger automations, import/export) map to active Pipedrive user seats. We resolve owners by email match against the Pipedrive destination account's user list. Lite accounts are flagged during scoping: Lite users cannot own records in Membrain and should not be mapped as deal or contact owners in Pipedrive. We remap ownership of any records owned by Lite accounts to a designated Full user before import.

Membrain Teams group users and can be assigned as record owners. Team structure is exportable, but team-to-user membership requires explicit mapping because Pipedrive team naming conventions differ. We export Membrain team membership, create Pipedrive Teams with matching names, and assign Pipedrive users to teams during import. If team names conflict with existing Pipedrive teams, we apply a prefix during migration and document the mapping for the customer's admin.

Membrain Tickets are an add-on module with their own workflow stages, custom fields, and assignment rules. Pipedrive does not have a native ticket or case object in its standard CRM tiers. If the customer uses Membrain Tickets, we map them to Pipedrive Leads with a custom ticket_status__c field and ticket-specific custom fields, or we recommend the Pipedrive Helpdesk add-on if the customer's Pipedrive plan supports it.