Migrate from openCRX to Zoho CRM

openCRX LegalEntity records (organisations) map to Zoho CRM Account. LegalEntity attributes including business classification, industry segment, and multi-currency settings transfer to Zoho Account fields. The openCRX segment that contains the LegalEntity is noted for Zoho territory assignment if applicable. Account is imported before any Contact records so that the Account-Contact relationship is satisfied at insert time.

openCRX Contact records (individuals) map to Zoho CRM Contact. PostalAddress and PhoneNumber sub-objects transfer to Zoho's standard address and phone fields. Contact's primary LegalEntity link becomes the Zoho Account lookup. openCRX Contact roles (e.g., Decision Maker, Technical Lead) migrate as a custom Contact field since Zoho does not have a native role attribute on the Contact-Account relationship.

openCRX Opportunities inherit from the abstract contract class and carry deal fields, ratings, and associated notes. We map openCRX Opportunity to Zoho Deal, preserving the openCRX contract status as Zoho Stage, the estimated value as Deal Amount, and the probability as a custom field since Zoho Deal stages do not carry decimal probabilities. The openCRX contract-position line items require decomposition into Zoho Deal Items or Quote line items.

openCRX Quotes inherit from the same contract hierarchy as Opportunities and Sales Orders, with Quote positions stored as contract positions. We map openCRX Quote to Zoho Quote, preserving line items, pricing rules, and currency context. Quote positions flatten into Zoho Quote Items with product, quantity, unit price, and discount fields. The parent Opportunity link is resolved by matching the openCRX contract reference to the migrated Deal.

openCRX Sales Orders follow the contract hierarchy and can be transformed from Quotes. Order positions are contract positions with pricing logic applied. We map openCRX Sales Order to Zoho Sales Order, preserving header details, order positions, pricing, and the parent Quote reference. If Zoho Inventory management is not enabled, Sales Orders migrate as read-only records with a flag indicating they require re-creation in the destination system.

openCRX Invoices are terminal contract objects in the sales process chain, inheriting from contract classes. We map Invoice headers, line positions, payment status, and currency to Zoho Invoice. Payment status from openCRX migrates to Zoho Invoice status fields. Historical invoices without open payment obligations may be migrated as read-only or skipped depending on the customer's accounting needs.

openCRX Products (including bundles and design-to-order configurations) map to Zoho Product. Multi-currency price lists and run-time pricing rules require decomposition: each openCRX price list for a given currency becomes a separate Zoho Price List entry. Complex bundles are decomposed into Zoho Product Bundles where the destination Zoho edition supports them, or into individual product components with a custom bundle identifier field.

openCRX Activities are core objects with rich attributes including time-tracking. Activity Trackers for grouping migrate as Zoho Tasks with a custom tracker identifier field. openCRX Activity subtypes require mapping: tasks with subtype CALL become Zoho Calls, scheduled meetings become Zoho Events, and general tasks migrate as Zoho Tasks. Activity timestamps and duration fields transfer to the corresponding Zoho field.

openCRX custom fields added via DataBinding PropertySet are feature definitions in the UI customising layer bound to CrxObject at runtime. We identify all active custom fields during scoping by querying the openCRX configuration schema, then create equivalent Zoho CRM custom fields per module before migration begins. Field data types are mapped: text to Zoho single-line or multi-line text, picklist to Zoho picklist, date to Zoho date, numeric to Zoho currency or numeric depending on context.

openCRX stores binary attachments linked to objects. We extract attachment metadata and file content via the data export process. Re-attachment to migrated Zoho CRM records uses the Zoho Attachments API. Note that WebDAV-based document access on Windows clients is known to be unreliable; we run export processes on Linux or macOS to avoid silent file access failures. Attachments migrate after parent records are confirmed in Zoho to ensure the correct record linkage.

openCRX users with role-based security assignments map to Zoho CRM Users. openCRX segment-scoped user roles require decomposition: each role-permission combination in openCRX is evaluated against Zoho's permission model. Users with no Zoho license assigned at migration time are created as inactive Zoho Users to preserve historical assignment context, then activated when the customer provisions the license.

openCRX Workflow Processes are segment-specific infrastructure objects that are not standalone records transferable between systems. We document every active Workflow Process definition during discovery, including triggers, conditions, and actions, and deliver this as a written workflow inventory. Zoho Workflow Rules are rebuilt by the customer's admin using the documented openCRX workflow logic as the specification.