Migrate from Membrain to Twenty CRM

Membrain Companies map directly to Twenty Companies. Standard fields (name, address, industry, website) migrate to Twenty Company fields by name match. The company domain becomes the Website field and serves as a dedupe key during import. CustomField{GUID} values on Companies resolve via the GUID-to-label lookup built from Membrain's custom field definitions during discovery. Company must import before People so the Company lookup relationship resolves on Contact insert.

Membrain Contacts map to Twenty People. Email address is the dedupe key; contacts with duplicate emails are merged or flagged for review based on activity recency. Standard fields (firstName, lastName, email, phone, jobTitle) map to Twenty People fields by name. The company-to-contact link migrates as the People.CompanyId lookup resolved against the imported Company records. Custom field GUIDs resolve via the lookup table; date and phone formats standardize to ISO 8601 and E.164 respectively.

Membrain Prospects live in the Prospecting product module with their own lifecycle stages distinct from Contacts. Where the customer uses Prospects as unqualified pipeline entries, we map them to Twenty People records with a custom pipeline_stage field carrying the original Prospect stage. If the customer maintains strict Contact-Prospect separation in Twenty, Prospects map to a custom Status field on People. Prospect-specific custom fields migrate to matching People custom fields in Twenty's Data Model.

Membrain Sales Projects map to Twenty Opportunities. The Sales Project's Company and primary Contact links migrate as Opportunity.CompanyId and a custom peopleId field resolved against the imported Company and People records. Stage name, probability, expected close date, and value migrate to Twenty Opportunity fields. Pipeline stage definitions require explicit mapping: Membrain's custom stage names (arbitrary per Sales Project type) map to Twenty's Opportunity stage values by position and win-rate intent.

Membrain Account Growth Projects track expansion and account planning at the Company level with their own workflow and custom fields. Twenty does not have a native account growth or account planning object, so we create a custom AccountGrowthProject object in Twenty's Data Model before import. Custom fields from Membrain map to the new object; the project-to-Company link migrates as a CompanyId lookup. Stage and value fields map to custom fields on the new object.

Membrain Activities migrate to Twenty Task or Note records depending on type. Appointments map to Event records with startDate, endDate, and location. Calls map to Task with a custom taskSubtype field set to 'Call' and callDuration custom fields. Notes map to Note records linked via ContentDocumentLink to the parent People or Company record. Emails and Tasks migrate as Task records. Activity-to-record links (PeopleId, CompanyId, OpportunityId) resolve against imported records by email or name match before insert.

Tickets are a Membrain add-on module with their own workflow stages, custom fields, and assignment rules. Twenty does not have a native ticket object in the base install. We map Tickets to a custom Ticket object created in Twenty's Data Model with custom fields for status, priority, assignee (resolved via User email match), and the parent Company or People link. If the customer does not have the Tickets module licensed, this object is absent from the export and skipped.

Membrain Full User accounts map to Twenty User (Member) records. We extract owner assignments from every record type (Companies, People, Sales Projects, Activities) and match by email against the Twenty Members list. Owners without a matching Twenty User are placed in a reconciliation queue; the customer's admin provisions missing users before record import resumes. Lite accounts are flagged separately and ownership is reassigned to a designated Full user before migration.

Membrain Teams group users and can be assigned as record owners. Team structure is exportable, but team-to-user membership requires explicit mapping because team naming conventions differ between platforms. We export the team hierarchy as a custom CSV and map team assignments to Twenty's workspace permissions or a custom Group object depending on the customer's intended usage.

Every Membrain custom field uses the CustomField{GUID} naming convention on each object context (Companies, Contacts, Prospects, Sales Projects, Account Growth Projects, Activities, Tickets). We query the custom field definitions first to build a GUID-to-label lookup table, then substitute human-readable field names during mapping. Before importing, all custom fields must exist in Twenty Settings Data Model; we create them via Twenty's UI or API before data import begins.

Membrain allows each Sales Project type to define its own stages with arbitrary names, probabilities, and step counts. We extract the complete stage definition from Membrain and map each stage to Twenty's Opportunity stage values by position and win-rate intent. Stage history that exceeds Twenty's default stage field capacity is logged as a custom activity record to preserve the audit trail.