Migrate from Encharge to Zoho CRM

Encharge People records map directly to Zoho CRM Contacts. Standard fields (email, first name, last name, phone, address) map to Zoho's native Contact fields by field name matching. Custom person fields in Encharge migrate as Zoho CRM custom fields on the Contact module, created with the _C suffix per Zoho convention before import. The Encharge Person ID is preserved in a custom field zg_encharge_id__c for deduplication and delta-reconciliation after cutover.

Encharge Accounts map to Zoho CRM Accounts. The company domain stored in Encharge maps to Account Website for deduplication. Account custom fields migrate as Zoho Account-level custom fields (_C). Accounts are imported before Contacts so that the Account-Contact lookup relationship is satisfied at the time of Contact insert. If an Encharge Contact has no associated Account, we create a placeholder Account record and link it.

Encharge Tags (flat string labels applied to People) map to Zoho CRM Tags. Tags migrate with their full assignment history per contact. In Zoho, Tags are applied at the module level (Contacts, Accounts, Deals) and support multi-value assignment. We export the complete tag assignment matrix from Encharge and reapply it during the Contact and Account import phase using Zoho's Tag API endpoint.

Encharge Custom Objects (Deals, Orders, Invoices, or domain-specific entities) map to Zoho CRM custom modules. We pre-create the destination custom module with the _C suffix (e.g., Orders_C) before migration, including all custom fields with type-matched Zoho field types and any lookup relationships to Contacts or Accounts. Custom relationship fields between Encharge Custom Objects are resolved at migration time using the stored reference IDs.

Encharge Segments are dynamic filter-based groups of People defined by behavioral criteria (event triggers, property conditions, date ranges). We export the full segment definition including filter rules, operators, and logic structure. Since Zoho CRM does not have an event-triggered dynamic segment equivalent, we reconstruct each segment as a Zoho Dynamic View (field-filter based) where the behavioral criteria can be approximated, or as a static Tag Group for criteria that require event-level data. Segments requiring real-time event re-evaluation are documented as a rebuild recommendation.

Encharge Activities record behavioral events (email opens, page views, clicks, custom events) with timestamps. We map these to Zoho CRM Activity records, normalizing event names to Zoho Activity field labels. Activity timestamps are preserved in the Activity Date field. Multiple Encharge event types (open, click, visit) that have no single Zoho equivalent are consolidated into a Zoho Activity record type with the event name stored in a custom Activity Type field.

Encharge Email Templates are stored as HTML with subject lines, sender names, and metadata. We export templates as HTML files preserving inline styles, images (as base64 or hosted URLs), and merge tag placeholders. Templates import into Zoho CRM's Email Templates library. Merge tags are mapped to Zoho CRM merge field syntax ($Contact.First_Name$, etc.) during the template import phase. We flag any template containing Encharge-specific liquid syntax as requiring manual adjustment.

Encharge Campaigns group emails and automation steps. Campaign names, status, and associated Contact lists migrate to Zoho CRM Campaign records. Since the campaign-Flow association does not export from Encharge, we document the campaign-to-step mapping during scoping so the customer can rebuild campaign sequences in Zoho Workflows or Blueprints. The campaign member list (Contacts enrolled in the campaign) migrates as Zoho CRM Campaign Members.

Encharge Users (team members assigned as Flow owners and sending identities) map to Zoho CRM Users. We resolve Encharge Users by email address against Zoho's User table. Any Encharge User without a matching Zoho User is placed in a reconciliation queue for the customer's admin to provision before record import begins, because OwnerId references are required for Contacts, Accounts, and Deals in Zoho.

Encharge Forms capture new People via field definitions and webhook configurations. We export the form field schema and webhook setup. Form URLs and embed codes must be updated in Zoho CRM's Web Forms or replaced with a third-party form tool post-migration. We deliver a written inventory of all active form URLs and their associated Zoho replacement form ID for the customer to update on their website.