Migrate from eTrigue to Zoho CRM

eTrigue Prospects map to Zoho CRM Leads for unqualified records and Contacts attached to Accounts for qualified records. We apply a qualification split rule during scoping based on the customer's campaign response history — Prospects with at least one campaign response or a Lead Score above a defined threshold become Contacts linked to a matching or newly created Zoho Account; all others become Zoho Leads. This split is necessary because eTrigue has no Account concept, so every Prospect's company field must be resolved to either a Zoho Account (for qualified contacts) or a free-text Company field on the Lead record.

eTrigue Campaigns map directly to Zoho CRM Campaigns with the Campaign Name, Campaign Type (Email, Webinar, Trade Show, etc.), and Status preserved. Campaign response data — including prospect responses, email sends, opens, and clicks — migrates as Campaign Member records in Zoho tied to the corresponding Leads or Contacts. We note that eTrigue's campaign response timeline is reconstructed by linking each Activity History entry back to the campaign it originated from using the exported campaign attribution data.

Each eTrigue Prospect Activity History entry — page views, email opens, form submissions, campaign responses — migrates to Zoho CRM as a Task record attached to the corresponding Lead or Contact. The Task Subject captures the activity type, the Description field holds the detail (page URL, form name, email subject), and the Activity Date carries the original timestamp. This preserves the chronological engagement timeline in Zoho's Activity section. eTrigue exports activity history as a structured CSV; we parse each row and map it to the Zoho Task object by resolving the parent Prospect's migrated record ID.

eTrigue Custom Fields — Boolean, Text, Date, Number, and Picklist types defined in Settings > Prospect Settings > Prospect Fields — map to Zoho CRM custom fields of equivalent type. Boolean fields export as true/false and map to Zoho's Checkbox field type. Text fields map directly. Number fields map to Zoho's Number field. Date fields map to Zoho's Date field. We create these as custom fields on the Lead and Contact modules during schema design before any records load, and the field labels are preserved from the source eTrigue field names.

eTrigue's composite Lead Score is stored as five separate numeric fields: Campaign Score, Activity Score, Source Score, Relationship Score, and Buy Time Score. Zoho CRM has no native equivalent for sub-component scoring. We create five custom Number fields on the Lead and Contact modules in Zoho — one for each eTrigue sub-score — and map them 1:1. A sixth composite field is optionally created as a sum of the five components if the customer wants the total available as a single field. We flag which scoring model the customer uses (standard five-component or 3D enriched composite) so the target scoring logic can be documented for rebuild in Zoho's Blueprint or workflow rules.

The 3D Lead Scoring model enriches the standard five-component score with content-type engagement weighting. eTrigue exports the 3D score as a single composite numeric value. We map this to a Zoho CRM custom Number field (etrigue_3d_score__c) on the Lead and Contact. Zoho does not have a native equivalent for 3D-style engagement-weighted scoring; we preserve the raw value so the customer's admin can decide whether to use it as-is, feed it into Zia predictive scoring (Enterprise tier), or rebuild it via Zoho workflow formulas.

Customers using eTrigue Lead Accelerator store partner organization names and partner-specific campaign attribution in custom Prospect fields rather than a dedicated Partner object. We extract these custom fields, identify the unique partner organization values, and create Zoho CRM Accounts for each partner organization. The original Prospect record links to its parent partner Account via a lookup relationship. Any partner-specific scoring rules and attribution data are flagged in the migration deliverable as items requiring manual configuration in Zoho Blueprint or custom fields post-migration.

eTrigue Content Types classify prospect engagement with content categories and are stored as tags on the Prospect record. We export these as comma-separated values and map them to a Zoho CRM Multi-Select Picklist field on Lead and Contact. This preserves the classification system and allows Zoho users to filter by content interest without rebuilding the taxonomy from scratch. We note the full set of unique tags during data profiling and validate that all exported values fit within Zoho's multi-select picklist limits.

eTrigue Prospects carry a Company Name field, but this is a free-text property on the Prospect record, not a linked object. During migration to Zoho CRM, we extract every unique Company Name value, create corresponding Zoho Accounts, and resolve the Account lookup on each Contact record. This step is necessary before Contact import so that the AccountId reference is satisfied at insert time. Accounts are created with the Company Name as the Account Name and the Prospect's website field (if present) mapped to the Account's Website field.

eTrigue Landing Pages and Progressive Forms host the lead capture experience. These do not migrate to Zoho CRM because they are page-rendering objects with styling, layout, and form field definitions that do not map to Zoho's data model. We export the form field definitions (field labels, field types, required status) as a written reference document so the customer's admin can replicate them in Zoho's Web Forms or an embedded Experience Cloud form. Landing page URL mappings are documented so that campaign email links can be updated post-migration.

eTrigue Scheduled Exports define saved search criteria for recurring prospect segment exports. We review each active Scheduled Export, document its filter criteria (field conditions, date ranges, campaign filters), and use the criteria as a guide for validating the completeness of the full CSV export. The scheduled export configurations themselves do not migrate because Zoho has its own workflow-based segmentation and list tools. We provide the documented criteria so the customer's admin can replicate the same prospect segments using Zoho's Saved Filters and Custom Views.