Migrate from Netmera to Zoho CRM

Netmera Users map to Zoho CRM Contacts as the primary migration record. Standard Contact fields (First Name, Last Name, Email, Phone) populate from Netmera user profile properties. Custom Netmera profile attributes (beyond defaults) map to Zoho CRM custom fields on the Contact layout, with field type alignment (string to text, number to integer or decimal, date to date picker, boolean to checkbox). Device information (OS, app version, push token) is stored as structured notes with a Note type classification or as custom fields on Contact. We deduplicate by email match at import time. Any untagged users that arrived via Netmera's tagless capture feature are flagged as a data gap for customer review.

Netmera Segments are audience rules rather than standalone records and do not map directly to a Zoho CRM object. We translate segment membership into Zoho CRM Tags attached to the corresponding Contact records, preserving which segments each Contact belonged to at migration time. For segments used as campaign audience scopes, we document the segment rule in a custom field on the related Campaign record. Zoho does not support dynamic segmentation natively, so the rebuild strategy for ongoing segment updates must be defined in Zoho using Tags, Advanced Filters, or Zoho CRM's Lookups. The customer selects the tagging approach during scoping.

Netmera Company properties attached to User records map to Zoho CRM Account records. If the source Netmera implementation stores company name and domain as User properties rather than a separate Company object, we synthesize Account records from that User-level data during migration, using the domain as the Account Website and the company name as the Account Name. The Account is created before the Contact import so that the Account-Contact Lookup relationship is satisfied at the moment of Contact insert. If no company data exists in Netmera, we document this gap and advise the customer on whether to create Accounts post-migration or leave Contacts unbound.

Netmera Campaign records migrate to Zoho CRM Campaign with campaign name, type (Push, Email, SMS, In-App), scheduled start and end dates, and audience scope (linked segment names) preserved in custom fields. Campaign creative content (text, images, video) migrates as file attachments to the Campaign record, subject to Netmera's 1MB image and 12MB video limits and Zoho's attachment handling. Widget assets embedded in in-app campaigns are exported as separate files with a reference in the Campaign record notes; the in-app message rendering engine is platform-specific and cannot be recreated in Zoho. Delivery logs and performance metrics (open rate, click rate, delivery rate) migrate to Campaign custom fields for historical reference.

Netmera Journey Orchestration flows define multi-step user-entry rules and channel steps but are bound to Netmera's event model and user-entry trigger logic, making them non-portable to Zoho Workflows. We export a Journey configuration inventory documenting each active Journey's entry conditions, step sequence, channel assignments, and conversion event definitions. This inventory is delivered as a structured document for the customer's Zoho admin to rebuild in Zoho Workflows or Blueprint. Note that Netmera's Journey conversion counting is user-based (one conversion per user per journey) whereas Zoho and most CRM platforms count per conversion event, so KPI definitions must be aligned during the rebuild scoping.

Netmera SDK-tracked events (page views, custom actions, trigger events) map to Zoho CRM Notes or Tasks depending on event type and volume. High-value conversion events (purchase, signup, upgrade) map to Tasks for CRM activity timeline visibility. Informational events (page view, feature use) map to Notes with the event name in the Note title and event properties in the Note body. Netmera event schemas vary by customer implementation, so each event property requires field-level mapping during the discovery phase. Event timestamps migrate as Note created dates or Task Activity dates to preserve historical ordering. Due to the schema variation risk, behavioral event migration is scoped and priced as a separate line item.

Netmera Device records (OS, OS version, app version, device model, push token, FCM/APNs token) migrate to Zoho CRM Contact custom fields for structured data (OS, app version) and to Notes for free-form or multi-value device data. Push notification delivery tokens (APNs, FCM) are explicitly non-transferable because they are bound to the Netmera-configured push credentials. We flag this in the migration scope and recommend planning a re-opt-in campaign or silent token refresh for active app users post-migration. Without this step, migrated users will not receive push notifications in Zoho CRM or any downstream push provider connected to Zoho.

Netmera custom profile attributes beyond the default set migrate to Zoho CRM custom fields on the Contact layout. We match Netmera attribute types to Zoho field types during schema design: string attributes map to Zoho text fields, numeric attributes to integer or decimal depending on precision, boolean attributes to checkbox, date attributes to date picker, and multi-value attributes to multi-select picklist or to separate related records if the cardinality exceeds picklist practicality. Default Netmera profile attributes (name, email, phone) map to standard Zoho Contact fields. Attribute naming conventions differ between platforms, so we use the Netmera attribute API name as a reference and assign Zoho field labels that align with the customer's business terminology.

Netmera Widgets (tooltips, pop-ups, in-app messages) are visual engagement assets rendered by Netmera's widget engine and are not transferable to Zoho CRM. We export widget content (text, images, video under the 1MB/12MB Netmera limits) as file assets and deliver them alongside a widget inventory document that lists each widget's name, type, content, trigger conditions, and targeting rules. The customer's design team uses the inventory to rebuild widgets as Zoho Canvas-generated in-app content or as external assets hosted in Zoho-integrated content management. Widgets with oversized assets (images over 1MB, video over 12MB) are flagged for re-encoding before the rebuild.

Netmera Tags used for labeling users and organizing data migrate to Zoho CRM Tags attached to Contact records. We preserve the tag name and the association to each user. Tagless data captured by Netmera's tagless capture feature is flagged as a data gap during migration scoping; the customer reviews and assigns appropriate tags or discards untagged records based on business rules. Zoho CRM Tags support a maximum tag length and character set that may require normalization of Netmera tag names containing special characters.