Migrate from Splio to Zoho CRM

Splio Contacts with no purchase history and no loyalty enrollment map to Zoho CRM Lead. Splio Contacts with at least one order or an active loyalty membership map to Zoho CRM Contact attached to a Zoho Account. We compute the split using Splio's order count and loyalty enrollment status at migration time. Original Splio contact properties (email, phone, consent flags) are mapped to Zoho Contact standard fields; any Splio custom properties on the contacts scope become Zoho CRM custom fields on the Contact or Lead layout.

If Splio data includes company or store associations on contacts, these map to Zoho CRM Account. The Splio store reference on a contact becomes an Account lookup. Zoho's account hierarchy (parent account, child accounts) is used to represent multi-location retail structures if the Splio stores scope is present.

Splio Order records map to Zoho CRM Deal (Opportunity). The Splio order_id becomes a custom field on the Deal (src_order_id__c) since Zoho Deals do not have a native external ID by default. Order amount maps to Deal Amount; order_date maps to Closing Date; order status maps to Stage. We create Zoho Deals before importing order_items so that the parent lookup is satisfied at insert time.

Splio order_items (line items referencing products) map to Zoho CRM Line Items attached to the parent Deal. Each line item carries a reference to the Splio product via a custom field since Zoho Line Items link to Zoho Products. We export Splio products first, create matching Zoho Product records, and then import line items with the Product lookup resolved to the newly created Zoho Product ID.

Splio Products (standalone items referenced by order_items) map to Zoho CRM Products. The Splio product_sku, product_name, and price map to Zoho Product standard fields. Any Splio custom fields on the products scope become Zoho custom fields on the Product layout.

Splio loyalty memberships carry card_code, q_points (quantized), nq_points (non-quantized), and tier. These have no native Zoho CRM equivalent. We create custom fields on the Contact object: src_loyalty_card_code__c (single-line text), src_loyalty_tier__c (picklist), src_loyalty_points_q__c (number), src_loyalty_points_nq__c (number). We deliver a loyalty-program handoff document describing the original point structure, tier thresholds, and expiration rules so the customer's admin can configure Zoho CRM's Loyalty Management extension or a custom loyalty app post-migration.

Splio reward definitions and contact-level reward attributions are mapped to a custom field on Contact (src_rewards_earned__c as multi-line text) and a related Notes section. For structured reward data (reward name, attribution date, expiry), we use custom fields: src_reward_name__c, src_reward_date__c. We do not create a separate Zoho custom module for rewards unless the customer requests it during scoping; the migration delivers a data model recommendation for a separate Loyalty module if the reward program is central to operations.

Splio Store records (physical retail locations and e-commerce sites) map to Zoho CRM Account records with a custom field src_store_id__c carrying the original Splio store identifier. We add a picklist custom field src_location_type__c (Physical Store, E-commerce) to distinguish between retail and online locations. If the customer operates a franchise or multi-location retail model, we use Zoho's Account hierarchy (parent Account for the brand, child Accounts for each store) to represent the structure.

Splio interaction events (custom events sent via API, such as loyalty point credits, purchase events, or loyalty tier changes) are event objects without a direct Zoho CRM equivalent. We map each interaction type to a Zoho CRM Task record with Task Subject containing the event type, Description carrying the event payload, and Activity Date set to the Splio interaction timestamp. For high-volume interaction logs, we consolidate into daily summary Task records to avoid exceeding Zoho's per-module record limits and to keep the activity timeline readable for sales reps.

Splio lists drive contact segmentation and export eligibility. We preserve Splio list memberships as Zoho CRM Tags on the Contact or Lead record (via the Tagging feature available in Zoho CRM Standard and above). Blocklist entries from Splio are mapped to the Has Opted Out of Email flag on Zoho Contact and Lead to honor suppression. We deliver a list-to-tag mapping table in the migration deliverable so the customer's admin can rebuild Splio segment filters as Zoho CRM Dynamic Views or Zoho Flow triggers post-migration.

Splio Owners referenced on contacts, orders, and loyalty memberships are resolved by email match against Zoho CRM Users. We extract all distinct Splio owner_id and email pairs and match against the Zoho org User table. Any Splio Owner without a matching Zoho User is held in a reconciliation queue for the customer's admin to provision before the record import resumes, because Owner references are required on most standard Zoho objects.

Splio consent records (tracking consent, SMS consent, email consent) attached to contacts are mapped to Zoho CRM Contact custom fields src_consent_email__c, src_consent_sms__c, src_consent_tracking__c (each a picklist: Granted, Denied, Not Collected) and the standard Has Opted Out of Email flag where consent has been denied or withdrawn. Consent timestamps are stored in corresponding date fields if present in Splio.