Migrate from Membrain to Salesforce Sales Cloud

Membrain Company records map directly to Salesforce Account. Standard address, industry, and owner fields migrate as their typed Salesforce equivalents. The Company record name becomes Account Name. We use the Membrain Company ID stored as a custom External ID field (membrain_id__c) to maintain referential integrity with related Contacts, Sales Projects, and Account Growth Projects during import. Account is the parent object — it must be created before any Contact or Opportunity import so that the AccountId lookup is satisfied at insert time.

Membrain Contacts map to Salesforce Contacts attached to the resolved Account. Email is the primary deduplication key; we flag duplicate email addresses during scoping and present a resolution option (merge or keep both with a duplicate indicator). Custom fields on Contact migrate via GUID-to-label lookup resolution before mapping. The Company-to-Contact link from Membrain resolves to AccountId on Salesforce Contact at migration time.

Membrain Prospects are distinct from Contacts and belong to the Prospecting product module with their own lifecycle stages. Prospects with a Membrain status of unqualified or early-stage map to Salesforce Lead; Prospects that represent a known contact with an active business relationship map to Salesforce Contact under the resolved Account. We define the split rule during scoping based on the customer's Membrain Prospect lifecycle stage values. The original Membrain Prospect stage is preserved in a custom field membrain_prospect_stage__c on the destination record.

Membrain Sales Projects are the deal equivalent in Membrain, tied to a Company and Contact with stage, value, expected close date, and owner. Custom stage names from Membrain map explicitly to Salesforce StageName values by examining stage position in the Membrain pipeline and the win-rate probability stored in Membrain. We configure a Salesforce Record Type per Membrain Sales Project type before migration so that stage values are scoped to the correct Sales Process. Stage history that exceeds Salesforce's standard stage field capacity is logged as a custom activity record.

Membrain Account Growth Projects track expansion and account planning work at the Company level with their own workflow and custom fields. Salesforce has no native Account Growth equivalent. We map Account Growth Projects to Salesforce Opportunity records using a custom Stage value (e.g., 'Account Growth') or to a custom Account_Plan__c object depending on whether the customer needs the records visible in pipeline reports. The mapping decision is confirmed during scoping based on the customer's reporting requirements.

Membrain Appointment records map to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Attendee links from Membrain map to EventRelation records pointing at the resolved Contact or Lead. Custom fields on Membrain Appointments migrate via GUID-to-label resolution to custom Event fields.

Membrain Call records map to Salesforce Task with TaskSubtype = Call. Call disposition, duration, and any custom fields migrate to custom Task fields. ActivityDate is set to the original Membrain call timestamp to preserve timeline ordering. The WhoId on the Task points to the resolved Contact or Lead; WhatId points to the related Opportunity or Account.

Membrain email activity records migrate to Salesforce EmailMessage (the email content) linked to a Task record (the activity timeline entry). Email body and subject transfer to EmailMessage. The WhoId on Task points to the resolved Contact or Lead; WhatId points to the related Opportunity or Account. We use Bulk API 2.0 for large email histories to avoid timeouts.

Membrain Note records map to Salesforce Note objects linked via ContentDocumentLink to the parent record (Account, Contact, or Opportunity). Rich text formatting in Membrain notes is preserved as HTML in the Note Body field. Custom fields on Membrain Notes migrate via GUID-to-label resolution.

Membrain standalone Tasks map to Salesforce Task with Status, Priority, Subject, ActivityDate, and OwnerId preserved. Owner resolution uses email matching against the Salesforce User table. Task assignment migrates by resolving Membrain owner references to Salesforce OwnerId via the User mapping.

Membrain stores custom field values under properties named CustomField{GUID} rather than human-readable field names. We query the Membrain custom field definitions during discovery to build a GUID-to-label lookup table, then substitute human-readable field names during mapping. Field types are mapped to typed Salesforce custom fields: text fields to Text, picklists to Picklist, dates to Date, numbers to Number, and booleans to Checkbox. Custom fields are pre-created in Salesforce before data import to avoid missing field errors.

Membrain Full users map to active Salesforce User seats by email match. Lite users in Membrain cannot own records, trigger automations, or perform batch operations — we flag every record owned by a Lite account during scoping and remap ownership to a designated Full user before import to avoid silent per-seat billing errors in Salesforce. Users without a matching Salesforce User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Membrain Teams group users and can be assigned as record owners. Team structure is exportable but the team-to-user membership must be mapped explicitly. We create Salesforce Groups with matching names and populate membership by resolving each Membrain team member's email to their Salesforce User ID. If the customer uses territory-based assignment in Membrain, we map those to Salesforce Territory2 records.

Tickets are a Membrain add-on module with their own workflow stages, custom fields, and assignment rules. If the destination Salesforce org includes Service Cloud, we map Ticket records to Salesforce Case. Ticket pipeline becomes Case Record Type; ticket stages become Case Status values; conversations migrate as EmailMessage records linked to the Case. If Service Cloud is not included, we map Tickets to a custom Case__c object.

Attachments linked to Membrain records are migrated as Salesforce ContentDocument records via ContentVersion. Large binary attachments may exceed API payload limits and require the customer to re-upload manually post-migration or use Salesforce Files Connect for cloud storage re-linkage. We flag files exceeding 25 MB during scoping and present the re-upload or Files Connect options.

Membrain allows each Sales Project type to define its own pipeline stages with arbitrary names, probabilities, and step counts. We extract the complete stage definition (names, probabilities, ordering) from Membrain during discovery and map each stage to a Salesforce Opportunity Stage value by position and win-rate intent. Note: Membrain's native Salesforce sync integration caps at 5 stages; migrations from Membrain instances with more than 5 pipeline stages must handle stage consolidation explicitly rather than relying on the sync integration.