Migrate from Membrain to monday CRM

Membrain Companies map to Monday.com CRM Organizations. Company name, address, industry, and owner assignment transfer directly. We use the organization's name as the dedupe key during import. Organizations must be created before any Contact import so that the People-Organization link is satisfied at the moment of Person insert.

Membrain Contacts map to Monday.com CRM People. Standard fields (name, email, phone, title) transfer directly. We deduplicate by email address on import. The company-to-contact link migrates by resolving the Membrain Company GUID to the Monday.com Organization ID. Custom fields on Contact migrate as Monday.com CRM column fields, resolved through the GUID-to-label lookup table built during extraction.

Membrain Prospects are a distinct object with their own lifecycle stages and belong to the Prospecting product module. Monday.com CRM does not have a separate Prospect object — Prospects are tracked as People records inside a CRM board. We migrate Prospects as People records with the original Membrain lifecycle stage stored in a custom column for segmentation. The customer's admin configures the board structure (e.g., a 'Prospecting' board with status columns representing lifecycle stages) post-migration.

Membrain Sales Projects map to Monday.com CRM Deals. Deal value, expected close date, owner, and associated Company and Contact links transfer directly. The Membrain Sales Project's stage maps to a Monday.com board Status column value, resolved by comparing stage position and win-rate probability to the closest Monday.com status option. Closed-Lost and Closed-Won states map to Done and Lost status columns in Monday.com Deals.

Membrain Account Growth Projects track expansion and account planning at the Company level. Monday.com CRM has no native Account Growth equivalent. We map these to Deals attached to the Organization with a custom 'Growth' or 'Expansion' label, or to items in a dedicated Account Growth board if the customer chooses that structure during scoping. Custom fields on Account Growth Projects migrate as Monday.com columns, resolved via the GUID lookup table.

Membrain Activities are first-class objects with their own custom field sets. Monday.com CRM does not have native Activity objects — activities are logged through automations or item update history. We create a Monday.com Activity board where each activity type becomes a group, with items representing individual engagement records. Activity date, duration (for Calls), subject, and notes transfer as columns. Large activity migrations (over 50,000 records) are chunked and sequenced chronologically.

Membrain pipeline stages are fully customizable per Sales Project type with arbitrary names, step counts, and probability percentages. Monday.com Deal pipeline stages are board Status columns with no native probability field. We extract the complete stage definition from Membrain (names, ordering, probabilities) and map them to Monday.com status options by position and intent. We flag stage probability differences in the mapping documentation so the customer's admin can add a probability column if needed.

Membrain custom fields use GUID-prefixed property names (CustomField{GUID}) rather than human-readable field names. We query the Membrain custom field definitions first, build a GUID-to-label lookup table, then substitute human-readable column names during Monday.com import. All custom fields belong to a specific object context (Company, Contact, Prospect, Sales Project), and we create Monday.com CRM columns scoped to the matching entity type.

Membrain Full users (can own records, trigger automations, import/export) map to Monday.com workspace Members. We resolve users by email match against the Monday.com workspace. The Monday.com CRM seat count (Basic, Standard, or Pro) must accommodate all migrated Full users before import begins.

Membrain Tickets are an add-on module with their own workflow stages, custom fields, and assignment rules. Monday.com CRM does not have a native ticket object but supports ticket-style tracking through a Service board with status columns. We map Ticket records to items in a dedicated Service board, preserving the ticket status, priority, and assignee. Custom fields on Tickets migrate as board columns via the GUID lookup.