Migrate your Membrain data

Companies are first-class CRM records in Membrain. Standard fields include name, address, industry, and owner assignment. We map Companies directly to Account/Company objects in destination CRMs using the canonical name field as the primary key anchor.

Contacts live under Companies and carry standard fields (name, email, phone, title) plus a rich set of custom fields. We deduplicate by email address on import and preserve the company-to-contact linkage.

Prospects are distinct from Contacts and belong to the Prospecting product module. They have their own lifecycle stages and can be enrolled in automations. Where the destination CRM lacks a separate Prospect object, we merge them into Leads and preserve the source Prospect stage as a custom property.

Sales Projects are Membrain's deal/opportunity equivalent, tied to a Company and Contact with stage, value, expected close date, and owner. Pipeline stage names and values must be mapped explicitly because Membrain allows fully custom stage sets per team. We preserve the stage history as a custom activity log when the destination does not support native stage audit trails.

Account Growth Projects track expansion and account planning work at the Company level. They have their own workflow and custom fields. We map these to the destination's account plan or opportunity object, flagging them as expansions against the primary account record.

Activities cover Appointments, Calls, Notes, Emails, and Tasks. Each activity type can carry its own custom fields. We migrate Activities in chronological order and preserve the activity-to-record linkage. Activity types are configurable in Membrain so we map them to the destination's corresponding activity type labels.

Automations execute sequences of steps across Companies, Contacts, Prospects, Sales Projects, and Account Growth Projects. Enrollment can be manual, batch, or event-triggered. We export automation logic as a structured workflow definition so it can be rebuilt in the destination system — migration of automation triggers requires reconfiguration by the customer's admin.

Custom fields in Membrain use a GUID-prefixed property naming convention (CustomField{GUID}). Each custom field belongs to a specific object context. We parse the GUID from field names, map them to destination custom fields by label, and handle type conversions (picklist options, date formats, numeric precision) during import.

Membrain distinguishes Full User accounts (can own records, trigger automations, import/export) from Lite accounts (read-only access to CRM data). We map Full users to active user seats in the destination and Lite users to read-only contacts or team members, flagging which records they should not be assigned as owners of.

Teams group users and can be assigned as record owners. Team structure is exportable but the team-to-user membership must be mapped explicitly since team naming conventions vary between CRMs.

Tickets are an add-on module. They have their own workflow stages, custom fields, and assignment rules. We map Ticket records to the destination's ticket or case object and preserve the assignment and status fields.

Content Hub stores sales content, templates, and collateral. We do not migrate binary content assets. We export the content library metadata (names, categories, associated record links) as a reference file so the customer can re-upload files to the destination's content library manually.

Pipeline stages are fully customizable per Sales Project type. We extract the complete stage definition including names, probabilities, and ordering, then map each stage to the destination pipeline's corresponding stage by position and intent.

Attachments linked to records are migrated as file references where API access permits. Large binary attachments may require the customer to re-upload manually post-migration.