Migrate from Membrain to HighLevel

Membrain Companies map directly to GoHighLevel Companies. Standard fields (name, address, industry, website) transfer directly. We use domain name as the dedupe key during GoHighLevel import. Company-to-Contact links are preserved as GoHighLevel's Contact-Company relationship, which is optional and non-hierarchical rather than the parent-child structure in Membrain.

Membrain Contacts map to GoHighLevel Contacts. Email address is the dedupe key. Standard fields (name, email, phone, title) transfer directly. Contact custom fields migrate to GoHighLevel Contact custom fields, which must be created before import and cannot be converted to Opportunity fields afterward. We flag every Membrain Contact custom field during scoping and create the GoHighLevel schema before any data moves.

Membrain Prospects belong to the Prospecting module and have their own lifecycle stages, distinct from Contacts. GoHighLevel does not have a separate Prospect object. We map Prospects with an early lifecycle stage (New, Contacted, Qualified) to GoHighLevel Contacts with a custom Prospect Status field and a tag applied. Prospects at an advanced stage (Proposal, Negotiation) migrate as Contacts with an open Opportunity attached.

Membrain Sales Projects map to GoHighLevel Opportunities. Each Sales Project type defines its own pipeline with custom stage names, probabilities, and step counts. We extract the complete stage definition during discovery, map the custom stage names to GoHighLevel pipeline stages by position and win-rate intent, and configure the GoHighLevel pipeline before migration. Closed-Lost and Closed-Won reasons from Membrain migrate as custom fields.

Membrain Account Growth Projects track expansion and account planning work at the Company level with their own workflow and custom fields. For simple account growth records, we map to GoHighLevel Opportunities with a custom Account Growth type tag and relevant custom fields. For complex account growth workflows with multiple stages, we document the structure as a written workflow for the customer's admin to rebuild using GoHighLevel's workflow builder.

Membrain custom field values are stored under CustomField{GUID} keys rather than human-readable names. We query the custom field definitions first, build a GUID-to-label lookup table, then substitute human-readable field names during mapping. This lookup table is validated against the Membrain schema before any GoHighLevel custom field creation begins.

Activities migrate by type: Membrain Calls map to GoHighLevel Tasks with Call subtype; Emails map to Notes with email content; Notes map to Notes; Tasks map to Tasks; Appointments map to Events. Each activity preserves its parent-record link (Contact, Company, Opportunity) and the original timestamp for timeline ordering. Activity custom fields migrate as GoHighLevel custom fields on the corresponding activity type.

Membrain Full users map to GoHighLevel user seats. We resolve by email match. Lite users (who cannot own records in Membrain) are flagged during scoping; their records are reassigned to a designated Full user before import. GoHighLevel Starter plan includes API access restrictions that may affect migration tooling; we confirm the plan tier during discovery.

Membrain Sales Project pipeline stages are fully custom per type. We extract the complete stage definition (name, probability, step count, ordering) during discovery, then configure equivalent GoHighLevel Pipeline stages before migration. Stage probabilities are mapped to GoHighLevel probability percentages per stage. If a Membrain stage does not map cleanly to a GoHighLevel stage, we document it for the customer's admin to decide during pipeline design.

Membrain automations execute sequences across Companies, Contacts, Prospects, Sales Projects, and Account Growth Projects with enrollment triggers, conditions, delays, and actions. GoHighLevel workflows use a different automation model. We do not migrate automations as code. We export the automation logic as a written inventory documenting trigger, conditions, actions, and recommended GoHighLevel Workflow equivalent, which the customer's admin rebuilds post-migration.