Migrate from Membrain to Freshsales

Membrain Company records map directly to Freshsales Account using company name as the primary dedupe key. The company address, industry, and owner assignment migrate to standard Freshsales Account fields. We create Accounts before any Contact import so that the lookup relationship is satisfied at the moment of Contact insert. If Membrain company records contain GUID-prefixed custom fields (CustomField{GUID}), we resolve them using the GUID-to-label lookup table built during discovery before writing to Freshsales.

Membrain Contact records map to Freshsales Contact with email-based deduplication to prevent duplicate creation. The company-to-contact link migrates via the AccountId resolved from the parent Company record. Title, phone, and standard custom fields migrate directly. Any Contact owned by a Lite user in Membrain is remapped to a designated Full user before import to avoid ownership errors in Freshsales.

Membrain Prospects belong to the Prospecting product module and have their own lifecycle stages distinct from Contacts. We map Prospects to Freshsales Leads by default, preserving the Membrain prospect stage as a custom field for admin reference. If the customer prefers Prospects to become Contacts directly (for early-stage teams that do not maintain a separate lead queue), we apply a custom mapping rule during scoping. The Prospect's associated Activities migrate as Tasks attached to the Lead.

Membrain Sales Projects are the deal equivalent, tied to a Company and Contact with stage, value, expected close date, and owner. Freshsales Deals use a standard stage model, so we map Membrain's custom stage names to Freshsales stage values by position and win-rate intent. Stage history that exceeds Freshsales's stage-count field capacity is logged as a custom activity record to preserve audit trail. Deal value, expected close date, and owner migrate directly with the OwnerId resolved via email match to a Freshsales User.

Account Growth Projects track expansion and account planning work at the Company level in Membrain. We map these to Freshsales Deals attached to the parent Account by default, using a Deal record type configured specifically for account expansion tracking. If the customer requires a separate expansion planning record, we pre-create a Freshsales custom object with lookup fields to Account and Deal, and migrate Account Growth Projects as custom object records instead.

Membrain Activities cover Appointments, Calls, Notes, Emails, and Tasks, each with their own custom field sets and the activity-to-record link. We migrate Activities in chronological order, preserving the link to the parent Contact, Company, Sales Project, or Account Growth Project using Freshsales's native activity object references. Call disposition and duration migrate to custom Task fields. Note content migrates as Freshsales Note records linked via ContentDocumentLink to the parent record.

Membrain Full User accounts map to Freshsales User records by email match. We resolve the owner reference on every record (Company, Contact, Sales Project, Activity) against the Freshsales User table during migration. Any Membrain Owner without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Membrain custom field values are stored under properties named CustomField{GUID} rather than human-readable field names. We resolve this by querying the Membrain custom field definitions during discovery to build a GUID-to-label lookup table, then substitute human-readable field names during mapping. Freshsales custom fields are created in the target account before migration using the resolved labels. This step is required for all Membrain object types that use custom fields (Company, Contact, Sales Project, Activity, Account Growth Project, Prospect, Ticket).