Migrate from Membrain to Microsoft Dynamics 365 Sales

Membrain Company records map directly to Microsoft Dynamics 365 Sales Account. Standard fields (name, address, industry, website) migrate as their typed Dataverse equivalents. The company domain becomes the Account Website field and is used as the deduplication key during import. Account is created before any Contact import so that the customerid lookup is satisfied at the moment of Contact insert. Team ownership migrates to the Account ownerid field after user reconciliation.

Membrain Contacts map to Microsoft Dynamics 365 Sales Contact with a 1:1 correspondence. The company-to-contact parent link migrates by resolving the Membrain Company GUID to the destination AccountID. Email address is the deduplication key; records with matching emails are updated rather than inserted. Custom fields on Contact migrate via the GUID lookup table built during discovery. The Membrain contact's primary company assignment becomes the parentcustomerid field on Contact.

Membrain Prospects (from the Prospecting product module) map to Microsoft Dynamics 365 Sales Lead. The Prospect lifecycle stage property maps to Lead Status, and the stage value is preserved in a custom field mb_original_lifestage__c for audit. Prospects with a confirmed company association are flagged to receive an Account during migration; those without are imported as Leads only. The Lead's company name field maps from the Membrain Prospect company field.

Membrain Sales Projects map to Microsoft Dynamics 365 Sales Opportunity. Each Sales Project type becomes a Dynamics 365 Record Type on Opportunity with a corresponding Sales Process. The Sales Project's custom stage names and probabilities are mapped by position and win-rate intent to the destination stage values. Closed-Won and Closed-Lost reasons from Membrain custom properties become Dynamics 365 Opportunity close fields. The expected close date migrates to estimatedclosedate and actual close date to closedate.

Membrain Account Growth Projects have no native Microsoft Dynamics 365 Sales equivalent. We create a custom AccountGrowthProject Dataverse object in the destination environment before migration, with fields for expansion_type, target_expansion_value, target_date, current_stage, and related_accountid (lookup to Account). The custom object's schema is defined during the destination schema design phase and deployed to the Dynamics 365 environment before any data import begins. If the customer does not license Dynamics 365 custom object support, Account Growth Projects are logged as Activity records attached to the parent Account.

Membrain Appointments map to Dynamics 365 Event records. Start time, end time, location, and description migrate directly. Attendees are resolved by email match to Contact or Lead and inserted as EventRelation records. Custom fields on Appointments use the GUID lookup table. Activity timestamps are preserved to maintain chronological ordering in the destination timeline.

Membrain Call records map to Dynamics 365 Task with TaskSubtype set to Call. Call duration, disposition, and any recording URL transfer to custom Task fields (mb_call_duration__c, mb_disposition__c, mb_recording_url__c). The WhatId on Task points to the related Opportunity or Account; the WhoId points to the related Contact or Lead.

Membrain Notes migrate to Dynamics 365 Annotation records (the unified notes and attachments object in Dataverse). Rich text body and file attachments migrate as separate Annotation records linked via objectid to the parent Account, Contact, Lead, or Opportunity. Custom fields on Notes use the GUID lookup table before mapping.

Membrain Email engagements migrate to Dynamics 365 EmailMessage records (the email content stored in Dataverse) and an ActivityPointer Task record (the activity timeline entry). The email body and subject migrate to EmailMessage; the activity timestamp and direction (inbound/outbound) migrate to the ActivityPointer. Recipients are resolved by email match to Contact or Lead.

Membrain Task activities map directly to Dynamics 365 Task. Status, Priority, due date, and description migrate directly. Task assignment migrates by resolving the Membrain hubspot_owner_id to Dynamics 365 OwnerId via the User mapping. The WhatId and WhoId links are resolved at migration time against the imported Account and Contact records.

Membrain Full User accounts map to Microsoft Dynamics 365 Sales User records by email match. Active Full users become active Dynamics 365 users; inactive Full users become inactive Dynamics 365 users. The mapping is validated during owner reconciliation before any record migration begins. A reconciliation queue holds any Membrain user without a matching Dynamics 365 user for the customer's admin to provision.