Migrate from Membrain to Zoho CRM

Membrain Company records map directly to Zoho CRM Accounts. The Company name maps to Account Name, address fields map to standard Zoho address fields, and owner assignment maps via email match to a Zoho User. We deduplicate by domain where multiple Companies share the same root domain. Companies without an assigned owner map to a designated migration admin User in Zoho.

Membrain Contacts map to Zoho CRM Contacts with email as the dedupe key. The Company-to-Contact link maps to the Contacts module's lookup to Accounts (Accounts module in Zoho). Standard fields (name, email, phone, title) map directly; custom fields migrate via the GUID-to-label lookup table built during discovery. Contacts without an email are flagged for manual review before import.

Membrain Prospects (from the Prospecting product module) map to Zoho CRM Leads. Prospects have their own lifecycle stages distinct from Sales Project stages, and we preserve these in a custom text field original_lifecycle_stage__c on the Lead for audit. Any Prospect enrolled in a Membrain automation is flagged in the automation inventory document; the enrollment history does not migrate.

Membrain Sales Projects map to Zoho CRM Potentials. The Company link maps to the Account lookup, the primary Contact maps to the Contact Name lookup, and value, expected close date, and owner migrate directly. Sales Project custom fields migrate via GUID resolution. The critical mapping step is stage translation — Membrain allows arbitrary stage names per Sales Project type, so we extract every stage definition (name, probability, ordering) from the source and map them to Zoho Potential Stage values by position and win-rate intent before import begins.

Membrain Account Growth Projects track expansion and account planning at the Company level with their own workflow and custom fields. Zoho CRM has no native account growth module. We create a custom Accounts Growth module in Zoho during schema setup with fields mapped from Membrain's Account Growth Project schema, or we map these records to Potentials of a designated record type (e.g., Account Growth) if the customer prefers a simpler model. The mapping strategy is confirmed during scoping.

Membrain Appointments map to Zoho Events with Start DateTime, End DateTime, and Location preserved. We link Events to the corresponding Account or Contact via the WhatId and WhoId equivalents in Zoho's EventRelation model. Custom fields on Appointments migrate via GUID resolution. Attendees from the Membrain appointment map to EventRelation records pointing at the related Contacts and Users.

Membrain Calls map to Zoho Tasks with the Call subtype. Call disposition, duration, and outcome stored in Membrain custom fields migrate via GUID resolution and map to Zoho custom Task fields. Activity timestamp preserves the original Membrain date for timeline ordering.

Membrain Notes migrate to Zoho Notes linked via module-specific lookup to the parent record (Account, Contact, or Potential). Rich text formatting is preserved where Membrain exports it as HTML. Note ownership maps by owner email match to Zoho Users.

Membrain email engagements migrate to Zoho Tasks with the Email subtype. Email body migrates to the Task description field, subject to the Task subject field, and timestamp is preserved for timeline ordering. Email attachments migrate as file references where the Membrain API exposes attachment URLs; large attachments may require re-upload post-migration.

Membrain Tasks map directly to Zoho Tasks. Status, Priority, due date, and Activity timestamp migrate directly. Owner assignment maps by email match. Tasks linked to specific Companies, Contacts, or Sales Projects resolve the parent record reference in Zoho before import.

Membrain Full users map to active Zoho CRM User seats by email match. We flag Lite accounts during scoping — Lite users cannot own records, trigger automations, or perform batch operations in Membrain, so their records must be reassigned to a Full user before migration. Zoho's role and profile structure is configured separately post-migration by the customer's admin.

Membrain custom fields use GUID-prefixed property names (CustomField{GUID}) rather than human-readable names. Before processing any data payload, we query the Membrain custom field definitions to build a GUID-to-label lookup table, then substitute human-readable field names during mapping. Zoho custom fields are created via the Fields editor in each module before data import begins. We confirm field types (text, number, date, picklist, lookup) for each Membrain custom field and map to the equivalent Zoho field type.