Migrate from Membrain to HubSpot

Membrain Prospects map to HubSpot Contacts directly. Pre-deal contacts that have not entered a Sales Project land in HubSpot as Contacts with lifecycle_stage set to 'lead'. Any email, phone, or company association present on the Prospect carries over as standard Contact properties.

Membrain Company records map 1:1 to HubSpot Companies without any transformation required. All standard fields — company name, domain, industry, employee count, and annual revenue — map to their HubSpot equivalents. Parent-company hierarchies defined in Membrain map to HubSpot's parent company association field, preserving organizational structures across the migration.

Membrain Contact records map directly to HubSpot Contacts. All standard properties — first name, last name, email, phone, job title, address — map to their HubSpot counterparts. Custom fields on Membrain Contacts migrate as HubSpot custom properties in snake_case naming.

Membrain Sales Projects are the primary deal-tracking object and map to HubSpot Deals. The Sales Project name becomes the Deal name, amount maps to deal amount, and close date maps to close date. The Membrain process step the project is in maps to the HubSpot dealstage pick-list value in the target pipeline.

Each Membrain Sales Project process step maps to a HubSpot deal stage. Stage names and order are mapped value-by-value. If Membrain has custom-named process steps (e.g., 'Discovery Complete', 'Proposal Sent'), those values are created as HubSpot deal stage labels in the target pipeline.

Membrain Appointments migrate as HubSpot Meeting engagements. Original start and end timestamps, owner, and the parent record (Contact, Prospect, or Sales Project) are preserved. If Membrain has custom Activity Types beyond Appointment, those are mapped to the closest HubSpot engagement type.

Membrain Tasks map to HubSpot Tasks with all key data preserved during migration. Subject, body, due date, owner, and completion status transfer directly. Completed tasks receive a completion date in HubSpot; open tasks retain their original due date as a reference point for follow-up.

Membrain Phone Calls migrate as HubSpot Call engagements with original call duration, outcome (if recorded as a custom field), owner, and the associated Contact or Sales Project preserved. Call disposition data stored in Membrain custom fields becomes a HubSpot custom property.

Membrain logged Emails map to HubSpot Email engagements with all metadata preserved. Sender, recipient, subject, body, and timestamp transfer and link to the parent Contact or Company record. Any file attachments included in emails are re-hosted in HubSpot's file storage during migration.

Membrain Notes map to HubSpot engagement notes, preserving rich-text formatting where HubSpot supports it. Notes originally attached to a Sales Project link to the corresponding Deal in HubSpot via the deal association, maintaining context continuity across the migration.

Membrain Account Growth Projects have no direct HubSpot equivalent. We create a HubSpot Custom Object named Account_Growth_Project__c, map the project name, target account (linked to Company), owner, status, and growth metrics as custom properties. This is a structural gap that requires HubSpot Enterprise-level access.

Membrain Tickets map to HubSpot Tickets. Subject, description, status, priority, owner, and pipeline assignment carry over. Membrain ticket custom fields migrate as HubSpot ticket properties. Note: Membrain's Flows module (process flows) does not have a HubSpot equivalent — those are not migrated.

Membrain custom fields use the CustomField{GUID} naming pattern — e.g., CustomField447dbe60-4925-4a75-b07b-13ad07d095d7. We extract the human-readable label from Membrain, create a corresponding HubSpot custom property using a snake_case version of that label, and map values field-by-field during migration.

Membrain owner assignments on Sales Projects, Prospects, Activities, and Tickets resolve by matching the owner's email address to an existing HubSpot user. Any unmatched owners are flagged before the migration runs — your team either creates the HubSpot user first or assigns those records to a designated fallback owner to prevent orphaned records in HubSpot after migration.