Migrate from Factoreal to Zoho CRM

Factoreal Contacts map to Zoho CRM Leads or Contacts depending on lifecycle stage and sales readiness. We classify Contacts with a purchase history or active engagement as Zoho CRM Contacts attached to Accounts, and unqualified or early-stage records as Leads. The split rule is defined during scoping based on the customer's data distribution. Original Factoreal contact properties (source attribution, behavioral scores, tags) migrate as custom fields on both Lead and Contact for audit and reporting continuity.

Factoreal Companies map to Zoho CRM Accounts. The Company domain or website becomes the Account website field and is used as the deduplication key during import. Account is provisioned before any Contact import so that the Account-Contact lookup is satisfied at the moment of insert, preventing orphaned Contact records.

Factoreal Segments are defined by filter rules on contact attributes and behavioral events. We document each segment's rule logic and reconstruct equivalent Saved Filters in Zoho CRM. The saved filter criteria are translated from Factoreal's operator syntax (equals, contains, greater than, date range, event-based) to Zoho CRM's filter builder format. Segment membership is recomputed post-migration against the migrated Contact and Account records rather than copied as static group memberships.

Factoreal Campaigns hold subject lines, content, send history, and engagement metrics (open rate, click rate, bounce, unsubscribe). We map campaign structure to Zoho CRM Campaign records, preserving campaign name, type, status, and start/end dates. Engagement metrics migrate as custom fields on the Zoho CRM Campaign record. Active vs archived status is preserved so that reporting can filter by campaign lifecycle.

Factoreal automation workflows define trigger conditions and multi-step action sequences across email, SMS, and WhatsApp channels. These are not stored in an exportable, portable format. We capture the full workflow graph — triggers, conditions, delays, and action steps — as a written inventory document and provide a recommended Blueprint or Workflow Rule structure in Zoho CRM for the customer's admin to rebuild. This is not executable code migration; it is a rebuild guide delivered alongside the data migration.

Factoreal email templates include HTML content and dynamic merge field placeholders. We extract template HTML and convert Factoreal merge field syntax to Zoho CRM's {{$Field.Name}} format. Visual rendering differences are expected because Zoho CRM's email editor uses its own rendering engine. We preserve the template HTML as a Zoho CRM Email Template with a note flagging any placeholders that require manual reconfiguration in Zoho's template editor.

Factoreal's built-in e-commerce integration captures order records with line items, product SKUs, quantities, and transaction amounts. We map order data to Zoho CRM Sales Orders and map paid orders to Zoho Invoice records. Product SKUs are matched to Zoho CRM Product records that we create during the product import phase. Order status (pending, paid, refunded) maps to Zoho's Sales Order status field and Invoice status field.

Factoreal products with SKU, name, price, and inventory quantity map to Zoho CRM Product records. We create Product2-equivalent records in Zoho CRM during a pre-import phase so that Sales Orders and Quotes can reference them at insert time. Factoreal's product images and descriptions migrate as custom fields or attachments depending on the customer's Zoho edition.

Channel-level message logs from Factoreal export as part of contact and campaign data. We preserve send timestamps, direction (inbound/outbound), and content in Zoho CRM as Task records with a custom channel field indicating SMS or WhatsApp. The Zoho CRM Conversation module (available in certain editions) can be used for threaded message display if the customer licenses the appropriate tier.

Factoreal custom fields on contact and company records are identified during the discovery phase and mapped to equivalent custom fields in Zoho CRM. We match field types (text, number, date, picklist, multi-select, checkbox) to Zoho CRM's supported custom field types. Picklist values are migrated as picklist options. Any Factoreal custom fields that cannot be represented in Zoho CRM (due to type incompatibility) are flagged in the field mapping document with a recommended workaround.

Contacts in Factoreal carry multiple tags representing behavioral labels, source attribution, or segment membership. We export the full tag list per contact and create equivalent Tags in Zoho CRM. Zoho CRM Tags are many-to-many and support color coding. Tags are applied to Contacts and Accounts at migration time, preserving the original relationship across both systems.

Factoreal Owners referenced on Contact, Company, Deal, and Engagement records are resolved by email match against Zoho CRM Users. Any Factoreal Owner without a matching Zoho CRM User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on Deals (Zoho CRM) and Tasks is resolved at migration time using the User mapping.